Skip to main content

Return of the Data

In the Full Fidelity Replay course, we set up the S3 Collector we will be using in this course. Previously, it was used to replay archived data unaltered into a new SIEM. Well, the new SIEM is still in evaluation. Today we are going to use the same Collector to push archived data through our sweet new Pipeline and into the SecOps SIEM.

We don’t need all archived data, though. Ed said they think the breach occurred between May 29 and June 5. Let’s keep that in mind as we configure the S3 Collector.

If you recall from the previous course (or not), we were able to configure the Collector to bypass the Data Routes, saving us some configuration work. We’ll be doing that again here.

important

Configure the s3replay collector

  1. With Manage active in Stream's top nav, select the Data submenu and click Sources
  2. Click S3 under Collectors
  3. Click s3replay
  4. Click Results Routing on the left side of the window
  5. Make sure Send to Routes is set to No
  6. Set the Pipeline to our new breachlookup
  7. Change the Destination to elastic:secopselastic
  8. Click Save

All done!

Ed can now search his newly enriched data… as soon as we run the Collector. Let’s go ahead and have the Collector grab the archived data and push it into the SecOps Elasticsearch.