Threat Intelligence

6/1/2016
01:45 PM
Connect Directly
Twitter
Twitter
RSS
E-Mail
50%
50%

The Double-Sided Coin Of OPSEC

Defenders must worry about their own operations security but can also learn a lot from attackers' OPSEC practices.

Most information security leaders recognize the importance of solid operations security (OPSEC) to keep the bad guys from getting an edge when formulating attacks. First developed by military minds, the idea behind OPSEC principles is simple even if the practices aren't always so cut-and-dried: keep the adversary guessing by denying them any information that might help them formulate their attacks. It's a fairly well-understood concept in the infosec world, but rarely used to flip the equation on the bad guys.

That's the premise behind a new study out today from Digital Shadows, which examined that maturity curve of OPSEC across the criminal underground and presents some opportunities that the good guys have to gain the advantage by paying attention.

"I think there’s two components for the enterprises. One, how do you think about your own OPSEC? And then, two, how do you keep an eye on what adversaries are doing to see if you can keep up with the trends, that sort of thing; tools that they’re using," explains Rick Holland, vice president of Digital Shadows and author of the report.

None of the individual criminals or criminal groups are created equally with regard to OPSEC, he says. It all depends on their motivations and financial models. For example, hacktivists might have poor OPSEC because they're whole M.O. is wrapped up around notoriety. Carders tend to have poor OPSEC because they're working on such volume, and the barrier to entry is pretty low to get into that business.

Meanwhile, more advanced operations with stealthy targeted attack campaigns invest more in OPSEC and may not advertise to the Dark Web at large about their services, choosing to do business only with those they know.

Simply observing how mature or immature an adversary is will give defenders some information about their operations. But for the most part, even those criminals with advanced OPSEC will only invest as much as they need to in keeping their tails clean.  

"An attacker who’s optimizing their OPSEC is just going to have a little bit better OPSEC than they need so that they don’t over-invest, especially on the more mature side. If you think of OPSEC as a cost of goods sold for them," he says. "They don’t want to put too much into it, and fortunately for the bad guys, the OPSEC bars can be relatively low given the lack of maturity that most of the companies they’re targeting have."

According to Holland, organizations tend to have their heads in the sand both internally and externally.

"I think organizations make a lot of decisions without understanding the risks that they face. Having some kind of OPSEC perspective in the organization is really, really important because it should drive the security program – not just the offset, but the data you’re trying to protect, the people associated with that data," he says.

Holland says many organizations don't conduct proper threat modeling and often don't understand things such as what types of adversaries are targeting them and their vertical markets, and how to use that type of intelligence to tune their security. 

Related Content:

Ericka Chickowski specializes in coverage of information technology and business innovation. She has focused on information security for the better part of a decade and regularly writes about the security industry as a contributor to Dark Reading.  View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Whoopty
50%
50%
Whoopty,
User Rank: Ninja
6/2/2016 | 7:45:29 AM
Silkroad
I think one of the best examples of poor OpSec was Ross Ulbright, the convicted admin of the Silk Road darknet marketplace. He was caught sending a tonne of fake passports to himself, logging in to the site in public locations, using personal emails for early set up requests about the site... 

You would imagine he'd be much more security concious than that, which is where half the conspiracy theories come from.
'PowerSnitch' Hacks Androids via Power Banks
Kelly Jackson Higgins, Executive Editor at Dark Reading,  12/8/2018
The Case for a Human Security Officer
Ira Winkler, CISSP, President, Secure Mentem,  12/5/2018
Windows 10 Security Questions Prove Easy for Attackers to Exploit
Kelly Sheridan, Staff Editor, Dark Reading,  12/5/2018
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
10 Best Practices That Could Reshape Your IT Security Department
This Dark Reading Tech Digest, explores ten best practices that could reshape IT security departments.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-8651
PUBLISHED: 2018-12-12
A cross site scripting vulnerability exists when Microsoft Dynamics NAV does not properly sanitize a specially crafted web request to an affected Dynamics NAV server, aka "Microsoft Dynamics NAV Cross Site Scripting Vulnerability." This affects Microsoft Dynamics NAV.
CVE-2018-8652
PUBLISHED: 2018-12-12
A Cross-site Scripting (XSS) vulnerability exists when Windows Azure Pack does not properly sanitize user-provided input, aka "Windows Azure Pack Cross Site Scripting Vulnerability." This affects Windows Azure Pack Rollup 13.1.
CVE-2018-8617
PUBLISHED: 2018-12-12
A remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka "Chakra Scripting Engine Memory Corruption Vulnerability." This affects Microsoft Edge, ChakraCore. This CVE ID is unique from CVE-2018-8583, CVE-2018-8...
CVE-2018-8618
PUBLISHED: 2018-12-12
A remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka "Chakra Scripting Engine Memory Corruption Vulnerability." This affects Microsoft Edge, ChakraCore. This CVE ID is unique from CVE-2018-8583, CVE-2018-8...
CVE-2018-8619
PUBLISHED: 2018-12-12
A remote code execution vulnerability exists when the Internet Explorer VBScript execution policy does not properly restrict VBScript under specific conditions, aka "Internet Explorer Remote Code Execution Vulnerability." This affects Internet Explorer 9, Internet Explorer 11, Internet Exp...