Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Cloud

11/11/2019
05:35 PM
Connect Directly
Twitter
LinkedIn
Google+
RSS
E-Mail
50%
50%

Researchers Find New Approach to Attacking Cloud Infrastructure

Cloud APIs' accessibility over the Internet opens a new window for adversaries to gain highly privileged access to cloud assets.

Public cloud infrastructure presents security teams with a new invisible management layer, creating new security challenges that demand better understanding. Many organizations don't properly understand the cloud identity and access management layer and often fail to secure it.

Such misunderstandings usually lead to dangerous misconfigurations that can drive customer risk; for example, in the case of the recent Capital One breach. Current security practices and controls are not sufficient to mitigate the risk posed by misunderstanding of the public cloud, explain Igal Gofman, XM head of security research, and Yaron Shani, XM senior security researcher.

When Gofman and Shani began to research cloud-focused threats, they realized many popular defense mechanisms focus on specific attack vectors: for example, brute force protections against cloud services and applications like password spray tools or AWS recon tools. Post-breach defense is usually based on different user activities and machine learning algorithms.

"The missing link in this approach is that those mechanisms are usually defensive in nature and usually not predictive," the researchers explain in an interview with Dark Reading. Traditional protections primarily focus on network, application, and operating system defense, they say.

A new attack vector exists in cloud providers' application programming interfaces (API), which are accessible through the Internet and give adversaries an opportunity to take advantage and gain highly privileged access to critical assets in the cloud. The people in charge of managing cloud resources are usually members of the DevOps, development, and IT teams, who gain access to APIs using different software development kits and dedicated command line tools.

"Once those account credentials are compromised, gaining access to high-value resources is trivial," the researchers say. Even if an organization makes a private subnet not open to the Internet, they add, cloud APIs can be easily accessed from the Internet with the right API key. Cloud provider tools—for example, the command-line interface tool (CLI) — save the user's credentials inside a file, which is typically locally stored on the individual's workstation.

At this year's Black Hat Europe, Gofman and Shani plan to demonstrate an alternative new approach to attacking cloud infrastructure in a talk titled "Inside Out — The Cloud Has Never Been So Close." Their methodology involves using a graph to show permission relationships between different entities, revealing risky choke points that need to be addressed and eliminated. The outcome of this graph, they say, can be used by red and blue teams to gain deeper understanding of permission relationships in cloud environments. After explaining the connections, they'll show how attackers can abuse features to gain privileges.

Attackers don't need to be sophisticated to take advantage of public cloud APIs, they say, noting they didn't find any open-source tools that automate the entire stack of the research.

"In practice, the sophistication required to develop such tools is not high, because basically all the information is publicly available and well-documented by most cloud providers, meaning they document each security feature in great detail and it can serve both the defenders and the adversaries," Gofman and Shani say. In general, they continue, developing an offensive tool that leverages their attack research would be easier than building a defensive system around it.

In terms of protecting themselves, the first and most important steps companies should follow are best practice guides from cloud providers, the researchers say. Large and complex organizations often have trouble tracking and monitoring permissions in large cloud infrastructures, and evaluating general organizational risk factors, they explain. They suggest constantly monitoring paths attacks can take to high-value cloud resources.  

Related Content:

Check out The Edge, Dark Reading's new section for features, threat data, and in-depth perspectives. Today's top story: "What a Security Products Blacklist Means for End Users and Integrators."

Kelly Sheridan is the Staff Editor at Dark Reading, where she focuses on cybersecurity news and analysis. She is a business technology journalist who previously reported for InformationWeek, where she covered Microsoft, and Insurance & Technology, where she covered financial ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
greg.jensen
50%
50%
greg.jensen,
User Rank: Author
11/22/2019 | 12:40:49 PM
Moving beyond the API
One of the most understood areas of ITsec is the issues that a modern DevSecOps program is starting to expose. Many of today's most sophisticated business-critical applications (Finance, HR, supply chain, CRM) that are 100% cloud native, often are part of a hybrid model with back-end services that reside in the customer's data center.  This often creates the risk that a compromise of the cloud service in question sometimes has entitled access to non-cloud data repositories in the customer data center.  This is why a DevSecOps model must be designed to canvas the "hybrid cloud" with consistent policies and workflows. 
COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/10/2020
Researcher Finds New Office Macro Attacks for MacOS
Curtis Franklin Jr., Senior Editor at Dark Reading,  8/7/2020
Healthcare Industry Sees Respite From Attacks in First Half of 2020
Robert Lemos, Contributing Writer,  8/13/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: It's a technique known as breaking out of the sandbox kids.
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
The Changing Face of Threat Intelligence
The Changing Face of Threat Intelligence
This special report takes a look at how enterprises are using threat intelligence, as well as emerging best practices for integrating threat intel into security operations and incident response. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-20383
PUBLISHED: 2020-08-13
ABBYY network license server in ABBYY FineReader 15 before Release 4 (aka 15.0.112.2130) allows escalation of privileges by local users via manipulations involving files and using symbolic links.
CVE-2020-24348
PUBLISHED: 2020-08-13
njs through 0.4.3, used in NGINX, has an out-of-bounds read in njs_json_stringify_iterator in njs_json.c.
CVE-2020-24349
PUBLISHED: 2020-08-13
njs through 0.4.3, used in NGINX, allows control-flow hijack in njs_value_property in njs_value.c. NOTE: the vendor considers the issue to be "fluff" in the NGINX use case because there is no remote attack surface.
CVE-2020-7360
PUBLISHED: 2020-08-13
An Uncontrolled Search Path Element (CWE-427) vulnerability in SmartControl version 4.3.15 and versions released before April 15, 2020 may allow an authenticated user to escalate privileges by placing a specially crafted DLL file in the search path. This issue was fixed in version 1.0.7, which was r...
CVE-2020-24342
PUBLISHED: 2020-08-13
Lua through 5.4.0 allows a stack redzone cross in luaO_pushvfstring because a protection mechanism wrongly calls luaD_callnoyield twice in a row.