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 for more information on CloudHunter and how to benefit from integration with GuardDuty

Popular posts from this blog

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 Incident According 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

Sift Joins Netskope, the Cloud Security Leader

Four years ago, we started Sift with the mission of simplifying security operations and incident response for the public cloud. In that time, we have assembled a fantastic team, created an innovative cloud detection and response solution, and have worked with many market-leading customers. I’m delighted to share that we’ve taken yet another step forward — as announced today, Sift is now officially part of Netskope. You can read more about this on Netskope CEO Sanjay Beri’s  blog  or in the official  announcement  on the Netskope website. For our customers, investors, partners, and team, this is an exciting new chapter. Let me tell you why we’re so excited.  Since the beginning, Netskope has had an unmatched vision for the cloud security market. Having started in 2012, they initially focused on SaaS security and quickly followed that with IaaS security capabilities. Six years later, they are now more than 500 employees strong and used by a quarter of the Fortune 100. They are a l

Sift Security vs. Elastic Search and Elastic Graph

We are often asked, “What is the difference between Sift Security and Elastic Graph ?” This is a great question that typically comes from folks who are already familiar with Elasticsearch [0] and Elastic Graph [1]. The answer boils down to the following: Elastic Graph is a tool for visualizing arbitrary aggregate search results. Elasticsearch is a Restful search that distributed, and has analytics engine that solves a number of use cases such as mapping from Python to ES REST endpoints. Sift Security uses a graph database to simplify and accelerate specific security use cases. In this blog post, we describe the advantages of each of these approaches, and conclude with a discussion of when to use each. Advantages of Sift Security vs ElasticSearch and Elastic Graph Query speed Sift Security builds a property graph to represent security log events at ingestion time.  We do this work at ingestion time for one reason:  to speed up common investigative queries.  When investi