Ingest AWS GuardDuty logs

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Ingest AWS GuardDuty logs

L2 Linker

Dear community,

 

I'm seeking help to ingest AWS Guardduty logs into Cortex XDR.

I did check the documentation and only found the method to ingest AWS assets, Flow log via S3 and Route53 via S3. 
I don't mind the AWS guardduty logs is not normalized, the objective is to get the logs into the Cortex XDR platform.

 

Appreciate if you could share your experience and knowledge.

Thank you. Cortex XDR AWS 

AC
1 REPLY 1

L5 Sessionator

Hi @Antony_Chan, thanks for reaching us using the Live Community.

 

As you noted, collecting AWS GuardDuty logs is not supported as an OOB feature, and if you can send them to XDR they will not be stitched to alerts and won't be processed by the analytics engine.

 

If you have Cortex XDR Pro license, you could be able to create an HTTP listener and send the logs to the tenant using a script to read the Guard Duty logs from a S3 bucket, like using Lambda to read the bucket and send the logs in JSON format to XDR. Here you can find the XDR side of the configuration requirements if you have the right license. After ingesting the logs you will need to parse them using custom parsing rules, to get the fields and store them in the dataset.

 

If this post answers your question, please mark it as the solution.

JM
  • 98 Views
  • 1 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!