Skip to main content

The Cloud Attack Chain

In an earlier posting on Public Cloud Security Detection Use Cases, we attempted to map
detections to the traditional Lockheed Martin Kill Chain. After further reflection,
we decided that cloud infrastructure threats are sufficiently different enough to warrant a
modified attack chain framework. We are releasing the Cloud Attack Chain framework today.
The Cloud Attack Chain is a simplified attack chain model that describes typical attacks on public cloud
infrastructure.  The attack chain describes how an attacker gains access to a victim’s cloud environment, how
they move laterally through the target cloud infrastructure, and what malicious actions they perform.   Our
new Whitepaper describes the four stages of the attack chain and provides detailed examples of some real-world

As a preview, the stages of the Cloud Attack Chain are:

1. Exposure: Exposure of cloud resources is at the beginning of any cloud attack. Exposure can be deliberate,
based on business trade-offs, or accidental, resulting from misconfigured resources or unpatched vulnerabilities.  
Exposures are where attackers start looking for a way in.

2. Access:  Access occurs when an attacker has figured out how to exploit an exposure and gains access to your
cloud infrastructure.

3. Lateral Movement: With access to your infrastructure, the attacker identifies targets for the attack, gaining
access to additional resources or escalating their privileges.

4. Actions: Now having access to the resources they need, the attacker performs some malicious action to fulfill
their objectives.

We invite you to learn more by downloading the paper at

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

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