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

3/22/2018
01:00 PM
Connect Directly
Twitter
LinkedIn
Google+
RSS
E-Mail
50%
50%

Hunting Cybercriminals with AWS Honey Tokens

Researchers at Black Hat Asia demonstrated how they used AWS honey tokens to detect security breaches at scale.

BLACK HAT ASIA - Singapore - Security analysts here today demonstrated how to detect security breaches by using Amazon Web Services (AWS) keys as honey tokens to lure cybercriminals.

A honey form is any form of credential or resource that you can use for monitoring and logging on, but doesn't exist anywhere in practical terms, explained Daniel Grzelak, head of security at Atlassian. It can be anything: an email address that doesn't belong to anyone and is generally available, a DNS name no one should ever resolve, a URL that nobody ever visits.

In their presentation, Grzelak and Dan Bourke, senior security analyst at Atlassian, showed how AWS keys can be configured as honey tokens at scale. These tokens can be placed anywhere across your environment or the supply chain and when threat actors find them, they'll try to use them. As a result, you'll know when and where a security breach occurs.

These keys are valuable to attackers and interesting for a few reasons, Grzelak said. Hackers who find AWS keys know they could use them to control someone's infrastructure. "Whenever some account gets compromised, one of the first things attackers do is look for another credential that lets them get into something more," he continued.

AWS provides complex, full-featured policy access management infrastructure, and keys to this infrastructure are placed everywhere. They're frequently found in GitHub repositories but also in .txt files, on the desktop, etc.

An AWS access key is like a scratch-off lottery ticket. If the attacker wins, they gain control over someone's infrastructure. If they lose, the key is simply an information disclosure vector that gives them more chances to win. However, they have to test it first.

"If an attacker finds an access key, there's no other way to find if it's useful other than to use the access key," Grzelak said. "One important property is, while access keys might be the keys to the kingdom, they don't have to be."

These keys could potentially grant hackers a lot of power or grant them nothing. They could also help businesses detect breaches in their networks. The logging capability in AWS means denial actions are logged and businesses can use them. If AWS keys are configured as honey tokens, a security team can know when, exactly, someone tried to use a specific token to log in.

If you want to generate a single access token, you can do so on Thinkst and put the token on your desktop. However, Grzelak and Bourke wanted to create tokens at scale to determine the implications if a business could place thousands of honey tokens across an enterprise.

Project Spacecrab

To generate this many tokens, the researchers built Project Spacecrab, which let users create, annotate, and alert on AWS keys, which don't provide access to anything, at mass scale. All keys get the deny-all policy so if anyone tried to use them, their actions are loaded into an S3 bucket.

Since AWS has a per-account user limit of 5,000 users and each can have two tokens, there is a limit of 10,000 tokens per account. However, as the researchers pointed out, that would be plenty to cover microservices for cloud services, or the number of desktops in an enterprise.

A few interesting lessons came from this experiment. The first: AWS closely monitors public Github repositories and will open support cases when public keys are put into a public GitHub repository. The second: Posting hundreds of keys to the Internet violates the AWS terms of use.

Project Spacecrab also showed that when someone posts their credentials to a public repository on GitHub, there's an 83% chance someone will use them. The average time to exploit after posting is almost exactly 30 minutes, the researchers pointed out.

Pastebin, in contrast, has a completely different exploitation profile. Only 9% of tokens posted on Pastebin were exploited, compared with more than 80% on GitHub.

Related Content:

Interop ITX 2018

Join Dark Reading LIVE for two cybersecurity summits at Interop ITX. Learn from the industry’s most knowledgeable IT security experts. Check out the security track here.

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
Ritu_G
50%
50%
Ritu_G,
User Rank: Moderator
8/19/2018 | 11:41:35 PM
hi
We have to tackle this problem regardless of what it takes. We have to come up with means and measures to ensure we take them down one way or another. It might be costly, it could get tough but we still need to get it done right. Whatever methods we might think of, we need to try them out to see if we finally can get this whole cyber crimes under control.
COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/3/2020
Pen Testers Who Got Arrested Doing Their Jobs Tell All
Kelly Jackson Higgins, Executive Editor at Dark Reading,  8/5/2020
Exploiting Google Cloud Platform With Ease
Dark Reading Staff 8/6/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
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-2020-15138
PUBLISHED: 2020-08-07
Prism is vulnerable to Cross-Site Scripting. The easing preview of the Previewers plugin has an XSS vulnerability that allows attackers to execute arbitrary code in Safari and Internet Explorer. This impacts all Safari and Internet Explorer users of Prism >=v1.1.0 that use the _Previewers_ plugin...
CVE-2020-9490
PUBLISHED: 2020-08-07
Apache HTTP Server versions 2.4.20 to 2.4.43. A specially crafted value for the 'Cache-Digest' header in a HTTP/2 request would result in a crash when the server actually tries to HTTP/2 PUSH a resource afterwards. Configuring the HTTP/2 feature via "H2Push off" will mitigate this vulnerab...
CVE-2020-11852
PUBLISHED: 2020-08-07
DKIM key management page vulnerability on Micro Focus Secure Messaging Gateway (SMG). Affecting all SMG Appliance running releases prior to July 2020. The vulnerability could allow a logged in user with rights to generate DKIM key information to inject system commands into the call to the DKIM syste...
CVE-2020-11984
PUBLISHED: 2020-08-07
Apache HTTP server 2.4.32 to 2.4.44 mod_proxy_uwsgi info disclosure and possible RCE
CVE-2020-11985
PUBLISHED: 2020-08-07
IP address spoofing when proxying using mod_remoteip and mod_rewrite For configurations using proxying with mod_remoteip and certain mod_rewrite rules, an attacker could spoof their IP address for logging and PHP scripts. Note this issue was fixed in Apache HTTP Server 2.4.24 but was retrospectively...