Suricata

Scanner supports Suricata EVE logs, which contain information relevant to network intrusion detection. In order for Scanner to see them, you need to configure a worfklow to push logs to an S3 bucket that Scanner is linked to.

Step 1: Set up logs to flow from Suricata to a local file

You can follow the Suricata documentation to configure it to export EVE JSON logs to a single file on local disk. See: Eve JSON Output.

This can be quite the firehose of data, so make sure to set up log file rotation to prevent your hard disk from filling up. See the Suricata documentation here: Rotate log file.

Step 2: Set up Fluentd to ship logs from local file to S3

You can follow the Fluentd documentation to configure it to read Suricata logs from local file and write the logs to your S3 bucket. Make sure to configure the output format to be JSON. See the following Fluentd documentation articles:

Step 3: Link the S3 bucket to Scanner

If you haven't done so already, link the S3 bucket containing your Suricata logs to Scanner using the Linking AWS Accounts guide.

Step 3: Set up an S3 Import Rule in Scanner

  1. Within Scanner, navigate to Settings > S3 Import Rules.

  2. Click Create Rule.

  3. For Rule name, type a name like my_team_name_suricata_logs.

  4. For Destination Index, choose the index where you want these logs to be searchable in Scanner.

  5. For Status, set to Active if you want to start indexing the data immediately.

  6. For Source Type, we recommend suricata:eve, but you are free to choose any name. However, out-of-the-box detection rules will expect suricata:eve

  7. For AWS Account, choose the account that contains the S3 bucket containing Suricata logs.

  8. For S3 Bucket, choose the S3 bucket containing Suricata logs.

  9. For S3 Key Prefix, type the prefix (i.e. directory path) of the S3 objects that Fluentd is writing.

  10. For File type, choose JsonLines with Gzip compression.

  11. For Timestamp extractors, under Column name, type timestamp. This is the field in each log event that contains the timestamp information.

  12. Click Preview rule to try it out. Check that the S3 keys you expect are appearing, and check that the log events inside are being parsed properly with the timestamp detected properly.

  13. When you're ready, click Create.

PreviousSublime SecurityNextSyslog

Last updated