Vulnerabilities / Threats

8/23/2017
10:30 AM
Connect Directly
Twitter
LinkedIn
RSS
E-Mail vvv
100%
0%

Why You Need to Study Nation-State Attacks

Want to know what attacks against businesses will look like soon? Examine nation-state attacks now.

Thinking like a cybercriminal can help predict what methods attackers are likely to develop in the future, so we can proactively build effective countermeasures, as I’ve described in the past. Similarly, nation-state attacks can help security researchers predict attacks against enterprises: methods exhibit a clear trickle-down effect, with tricks first used in nation-state attacks being seen in enterprise-facing attacks soon after.

One of the most important recent security developments is the rise of sophisticated, politically motivated attacks, such as the one carried out against Hillary Clinton's campaign chairman John Podesta during the 2016 presidential election. However, such attacks have been against a broad spectrum of victims, ranging from individual lawmakers and staffers to think tanks and nongovernmental organizations (NGOs). These attacks involved clever identity deception methods combined with techniques used to circumvent traditional content-scanning methods.

Another event is the sudden rise of ransomware attacks, whether targeting lawmakers, health care institutions, transportation, or small businesses. Whereas most ransomware attacks aim to extort money, some have recently demanded nonmonetary "payments," such as forcing a government organization to make a political statement.

What do such attacks have in common? They've become increasingly sophisticated. For example, in the Podesta attack, the attackers cleverly obfuscated some words (such as "password" and "account") by replacing some of their letters with Cyrillic letters that look the same to humans, but which thwart keyword-based filters. Another example was the post-election attacks on think tanks and NGOs, in which malware files were cleverly hidden from the view of traditional antivirus tools by sending the corrupted files in encrypted zip files. Without access to the decryption keys, the contents can't be scrutinized by traditional mail-filter technologies.

The use of advanced techniques to circumvent security tools has recently become much more common. What's interesting (and worrisome) is that not just nation-state attacks use such techniques. That's where the techniques were first used, but there has been a notable trickle-down effect, and tricks first used in nation-state attacks have been seen in attacks against enterprises a few weeks later. In a sense, this trend mimics the flow of insights gained just as technologies developed for the space program found themselves spun off as commercial products. This is why companies in the private sector need to quickly determine whether they would be vulnerable to these advanced attacks.

Take Active Measures Now
The security community should quickly roll out detection and protection measures in anticipation of trickle-down versions. For example, obfuscation attacks can be detected by automatically spotting deceptive mixtures of character sets and blocking such messages. Encrypted zip files are easily detected, but since they have important legitimate use, they can't be blocked. One possible solution is for a security system that can "wrap" them with a trusted executable as the messages are delivered. The task of the wrapper is to request a PIN or password, then use this to decrypt the wrapped file and perform a security check in real time. If the file is determined to be safe, the user is given access to the plaintext file.

From the user's perspective, nothing is different, except maybe for a short delay caused by the scanning of the decrypted files. The wrapper approach also works for other file types, such as encrypted PDFs. With this approach, one can take back the advantage of time from the attackers, since this enables on-the-fly scans of plaintext data without requiring independent software vendors to coordinate the protection of an end user, which is always difficult.

Even better, the wrapper can include information about the sender as well. Was a malicious file sent by a trusted party? If so, then the trusted party has been compromised and should be notified. The more we use contextual information, the better our defenses get. And much of this context is to be found in early attacks — so unless we study nation-state attacks and learn from them, we implicitly help enterprise attackers.

Although the sophistication of online crime has changed in the last year, and there is clear evidence of trends toward fraud becoming just another business, other things have remained very much the same. For example, email remains the principal attack vector. Similarly, identity deception is still at the core of most attacks, be they phishing, business email compromise, ransomware, or other malware attacks where the stolen identity is usually from an authority figure, well-known brand, or a trusted party. While attackers constantly try new ideas, one thing is clear: they don't mess with a winning formula.

Moving forward, the security community must pay close attention to the nature and strategy of nation-state attacks and quickly address them, because the same techniques will be repurposed to attack enterprises. In addition, we must expect that every newly found and disclosed vulnerability will be used in attacks, whether by nation-state actors or enterprise-facing attackers.

Finally, society must recognize that threats are constantly evolving — in reaction to new-found adversarial opportunities as well as existing security technologies — and traditional technologies are unlikely to address them. In other words, if you think a spam filter is the answer to your problems, you are mistaken.

Learn from the industry’s most knowledgeable CISOs and IT security experts in a setting that is conducive to interaction and conversation. Click for more info and to register.

Related Content:

Markus Jakobsson, Chief Scientist for Agari, has spent more than 20 years as a security researcher, scientist, and entrepreneur, studying phishing, crimeware, and mobile security at leading organizations. In his role at Agari, he leads the company's security research with a ... View Full Bio
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
MarkusJakobsson
50%
50%
MarkusJakobsson,
User Rank: Apprentice
8/26/2017 | 12:10:57 PM
Re: $0phiStic4ti0n
It is true that, by itself, a homograph attack would not be so sophisticated. But here it was part of a bigger picture. The attack also used other deceptive techniques, such as:

* Spoof the email from a source (accounts.googlemail.com) that *looked like* the source from which real notifications would be sent ([email protected]) ...
* ... where this domain was not used by Google, and Google did not have a DMARC policy in place that caused rejection traffic appearing to come from subdomains not in use.

Of course, the attackers could have done "better" -- after all, the email was delivered in the spam folder of the intended victims. They could, for example, have used the "Spam phishinhg" techniques described by Hossein Siadati at the recent Decepticon conference, to overcome this drawback.

Maybe the attackers fouled up. Maybe they did not realize. Or maybe it just did not matter much to them: their yield was sufficient for them to be satisfied.

Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
8/26/2017 | 10:12:43 AM
$0phiStic4ti0n
I agree with the overall points, but...

"replacing some of their letters with Cyrillic letters that look the same to humans, but which thwart keyword-based filters"

...this can hardly be described, in my mind, as "sophisticated." It's no more sophisticated than people thinking their being secure by replacing the letter "o" in their passwords with numeral 0.
1.9 Billion Data Records Exposed in First Half of 2017
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/20/2017
Get Serious about IoT Security
Derek Manky, Global Security Strategist, Fortinet,  9/20/2017
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
Security Vulnerabilities: The Next Wave
Just when you thought it was safe, researchers have unveiled a new round of IT security flaws. Is your enterprise ready?
Flash Poll
[Strategic Security Report] How Enterprises Are Attacking the IT Security Problem
[Strategic Security Report] How Enterprises Are Attacking the IT Security Problem
Enterprises are spending more of their IT budgets on cybersecurity technology. How do your organization's security plans and strategies compare to what others are doing? Here's an in-depth look.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2017-0290
Published: 2017-05-09
NScript in mpengine in Microsoft Malware Protection Engine with Engine Version before 1.1.13704.0, as used in Windows Defender and other products, allows remote attackers to execute arbitrary code or cause a denial of service (type confusion and application crash) via crafted JavaScript code within ...

CVE-2016-10369
Published: 2017-05-08
unixsocket.c in lxterminal through 0.3.0 insecurely uses /tmp for a socket file, allowing a local user to cause a denial of service (preventing terminal launch), or possibly have other impact (bypassing terminal access control).

CVE-2016-8202
Published: 2017-05-08
A privilege escalation vulnerability in Brocade Fibre Channel SAN products running Brocade Fabric OS (FOS) releases earlier than v7.4.1d and v8.0.1b could allow an authenticated attacker to elevate the privileges of user accounts accessing the system via command line interface. With affected version...

CVE-2016-8209
Published: 2017-05-08
Improper checks for unusual or exceptional conditions in Brocade NetIron 05.8.00 and later releases up to and including 06.1.00, when the Management Module is continuously scanned on port 22, may allow attackers to cause a denial of service (crash and reload) of the management module.

CVE-2017-0890
Published: 2017-05-08
Nextcloud Server before 11.0.3 is vulnerable to an inadequate escaping leading to a XSS vulnerability in the search module. To be exploitable a user has to write or paste malicious content into the search dialogue.