Skip to main content

Integration with Amazon GuardDuty

What is Amazon GuardDuty?

Amazon GuardDuty is a continuous security monitoring platform that analyzes and processes VPC flow logs, AWS CloudTrail event logs and DNS logs. It uses threat intelligence feeds, such as lists of malicious IPs and domains to identify malicious activity within your AWS environment.

You can enable the GuardDuty Service through your Amazon Console. Once there, you are then presented with the GuardDuty dashboard, as shown in the example below:














Finding are rated as High, Medium or Low on the dashboard and have the following meaning:  

High findings indicates that the resource in question is compromised and is actively being used for unauthorized purposes.

Medium findings indicates suspicious activity, for example, a large amount of traffic being returned to a remote host that is hiding behind the Tor network.

Low findings indicates suspicious or malicious activity that was blocked before it compromised your resource.

Integrating CloudHunter with GuardDuty

CloudHunter integrates with Amazon GuardDuty to enable customers to comprehensively manage risk across AWS and other leading cloud services such as Microsoft Azure. CloudHunter ingests Amazon GuardDuty findings and provides a centralized view on security risks, leading to more actionable alerts and incidents, and faster, automated remediation.


Key benefits of integrating Amazon GuardDuty with Sift Security CloudHunter include:

  • Centralized & Enhanced Cloud Visibility: CloudHunter correlates GuardDuty findings with finding from other cloud security products such as Amazon Inspector, as well as raw cloud data such as CloudTrail and VPC Flow, and related logs such as host logs. Sift Security provides comprehensive visibility to all of this data including alerts, dashboards, search, and our innovative graph canvas visualization and investigative interface.
  • Enhanced Alerts: CloudHunter pulls in findings from products like Amazon GuardDuty and Inspector, and enriches those alerts by correlating them with other risks and relevant context. For example, if we see an alert related to an instance, the score of the alert is affected by its context: (a) are there any vulnerabilities? (b) is the instance in a sensitive account? (c) does the instance have excessive permission? This context combined with our clustering algorithms enables the highest fidelity, most actionable alerts to be surfaced as possible incidents which should be investigated immediately.
  • Entity Behavioral Analysis: CloudHunter identifies the riskies entities, including accounts, users, instances, and storage. These entity views are generated by combining alerts from multiple sources, anomalous activity, and business context. Analysts can easily investigate the riskiest entities by filtering all alerts associated with that entity and exploring the alerts in the graph canvas.
  • Easier, Faster Investigations: Through the correlation and enrichment above, analysts start with a small number of actionable alerts, and have all the necessary context to rapidly investigate root cause and impact. These investigations include filterable alert tables, alert details, search, and graph canvas, which allows simple investigations that do not require in depth understanding of the underlying data structure and allow for seamless pivoting across entities and IOCs.
  • Seamless, Automated Response: Sift Security offers a number of integrations out of the box, that allow users to take seamless manual action or create automated play-books. Additionally, our customers can easily add additional integrations to meet their needs.

Visit cloudhunter.io for more information on CloudHunter and how to benefit from integration with GuardDuty

Popular posts from this blog

Sift Security Tools Release for AWS Monitoring - CloudHunter

We are excited to release CloudHunter, a web service similar to AWS CloudTrail that allows customers to visually explore and investigate their AWS cloud infrastructure.  At Sift, we felt this integration would be important for 2 main reasons:
Investigating events happening in AWS directly from Amazon is painful, unless you know exactly what event you're looking for.There are not many solutions that allow customers to follow chains of events spanning across the on-premises network and AWS on a single screen. At Netflix, we spent a lot of time creating custom tools to address security concerns in our AWS infrastructure because we needed to supplement the AWS logs, and created visualizations based on that data.  The amazing suite of open source tools from Netflix are the solutions they used to resolve their own pain points.  Hosting microservices in the cloud with continuous integration and continuous deployment can be extremely efficient and robust.  However, tracking events, espec…

Sift Security and WannaCry

😢 The WannaCry ransomware attack has left security teams around the world scrambling to make sure they are protected and to assess whether they have been victimized. To protect themselves, organizations need to have visibility into which systems are vulnerable and be able to rapidly roll out patches.  To understand whether they have been targeted, they need visibility into the channels over which the ransomware is distributed.  To understand whether they have been infected, they need visibility into the endpoints.
Over the past weekend, I was bombarded with questions from current customers, potential customers, former colleagues, friends, and family.  Am I vulnerable? How do I protect myself? How do I know if I’ve been hit? What do I do if I’ve been hit? What can you do to help me?
This post focuses primarily on the last question. What can we at Sift Security do to help an organization respond to a massive ransomware attack? I break this down into four categories, visibility, analyt…

Data Exfiltration from AWS S3 Buckets

You will have no doubt heard by now about the recent Booz Allen Hamilton breach that took place on Amazon Web Services – in short, a shocking collection of 60,000 government sensitive files were left on a public S3 bucket (file storage in Amazon Web Services) for all to see. We are all probably too overwhelmed to care, given all the recent breaches we have been hearing about in the news. But with this breach it was different, it involved a trusted and appointed contractor whose job it was to follow security policies, put in place to avoid such incidents. So was this incident accidental or malicious? More, later about the tools we can use to tell the difference between the two. First, lets recap what happened.The IncidentAccording to Gizmodo, the 28GB of data that was leaked not only contained sensitive information on recent government projects, but at least a half dozen unencrypted passwords belonging to government contractors with Top Secret Clearance – meaning anyone who got their h…