Sophos

Scanner supports Sophos Central SIEM alert logs, which contain information about security events and alerts generated across various Sophos products integrated with Sophos Central. 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 Sophos to Fluentd to S3

Sophos provides a Python tool to export SIEM alerts from Sophos Central to a destination that supports receiving syslog data.

You can run a Fluentd agent to receive syslog data and forward logs to S3.

You can follow the Sophos documentation to configure the SIEM alert export flow to a syslog destination, which in our case will be Fluentd. See the following Sophos resources:

• Sophos Central APIs: Send alert and event data to your SIEM

• Sophos-Central-SIEM-Integration on GitHub

You can follow the Fluentd documentation to configure it to receive syslog input and write output logs to your S3 bucket. Make sure to configure the output format to be JSON. See the following Fluentd articles:

• Fluentd syslog input module

• Fluentd s3 output module

Step 2: Link the S3 bucket to Scanner

If you haven't done so already, link the S3 bucket containing your Sophos 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_sophos_central_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 sophos:central, but you are free to choose any name. However, out-of-the-box detection rules will expect sophos:central.

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

8. For S3 Bucket, choose the S3 bucket containing Sophos 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 end. 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.