AWS GuardDuty
Scanner supports AWS GuardDuty log events, which describe security findings generated by AWS. In order for Scanner to see these logs, you can configure GuardDuty to publish findings to S3.
Step 1: Configure GuardDuty to export to S3
You can follow the AWS documentation to configure GuardDuty to export findings to S3. See: Exporting findings.
Step 2: Link the S3 bucket to Scanner
If you haven't done so already, link the S3 bucket containing your CloudTrail logs to Scanner using the Linking AWS Accounts guide.
Step 3: Set up an S3 Import Rule in Scanner
Within Scanner, navigate to Settings > S3 Import Rules.
Click Create Rule.
For Rule name, type a name like
my_team_name_aws_guard_duty_logs.For Destination Index, choose the index where you want these logs to be searchable in Scanner.
For Status, set to Active if you want to start indexing the data immediately.
For Source Type, we recommend
aws:guard_duty, but you are free to choose any name. However, out-of-the-box detection rules will expectaws:guard_duty.For AWS Account, choose the account that contains the S3 bucket containing CloudTrail logs.
For S3 Bucket, choose the S3 bucket containing CloudTrail logs.
For S3 Key Prefix, type the prefix (i.e. directory path) where the CloudTrail trail is writing logs. This is usually just
AWSLogs/. We will use Additional Regex to refine the selection further.Click + Additional Regex, and type:
.*/GuardDuty/.*\.jsonl\.gzThis will ensure that we only index files gzipped JSON files in the directory
/GuardDuty/, and skip any files in other directories.
For File type, choose JsonLines with Gzip compression.
For Timestamp extractors, under Column name, type
CreatedAt. This is the field in each log event that contains the timestamp information.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.
When you're ready, click Create.
Last updated