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.

News & Commentary

11/2/2017
10:30 AM
Sam McLane
Sam McLane
Commentary
Connect Directly
LinkedIn
RSS
E-Mail vvv
50%
50%

What Blue Teams Need to Know about Targeted Attacks

A malicious intruder only has to be right once. But defenders must be right 100% of the time.

Unlike in a courtroom, the defense never rests when it comes to enterprise cybersecurity. And for good reason: successful hackers are constantly devising new ways to penetrate vulnerabilities in company networks and gain access to critical data, finances, intellectual property, and all sorts of other valuable information. IT security teams can never be comfortable because a malicious intruder only has to be right once, while we on the blue team must be right 100% percent of the time.

In an increasingly wired world, cybercrime is big business and attacks are always on the rise. According to Anti-Phishing Working Group, there were more than 1.22 million phishing attacks in 2016, a 65% increase compared to the year before. What's more, damages caused by ransomware are expected to reach $5 billion by the end of 2017, a 15-fold increase over two years. If your company is unable to respond immediately to phishing, ransomware, and malware threats, business productivity and the bottom line suffers for days or weeks on end.

Unfortunately, even the most comprehensive response means little if too much time passes between a successful intrusion and its detection. With enterprises constantly under attack, all security teams seem to employ spam filters, antivirus software, security firewalls, and a host of other measures to combat potential threats. Nonetheless, attacks happen, and when they do many companies are ill-equipped to adequately respond.

There are also limits to employee awareness training that put employees on guard against the latest dangers that can cripple their devices and spread like a plague throughout the company. Should a user land on a website that "smells phishy" or suspect anything untoward on their computing device, it's important for them to proceed with caution and immediately alert others, including managers and IT personnel. But with targeted attacks increasing in frequency and sophistication, there is only so much a basic tools-and-awareness approach can do before an intruder solves a firm's perimeter and endpoint defenses, and then threatens to steal your data or infect your network.

Learn more from Sam about "Targeted Attacks: How to Recognize Them from the Defender's Point of View" on November 30 at the INsecurity Conference, sponsored by Dark Reading. Sam will describe a step-by-step process, including information correlation, effective mitigation, and future strategies. 

For security experts and engineers who defend against cyberattacks for the blue team, these threats come in many forms. Sometimes it's a server sending encrypted traffic to a known malicious website, or it could be suspicious DNS queries or user names and passwords entered "in the clear." Perhaps most commonly of all, the first signal comes in the form of odd traffic flow patterns, including those to and from foreign countries. Upon discovering such instances, organizations need to undertake an immediate investigation that can quickly determine the nature of the threat — and avoid an overly extensive hunt down a non-malicious trail of innocuous alerts and false positives that can prove quite costly in its own right.

Bottom line: even the best security engineers and experts can be helpless without the right security tools and processes at their command. It takes both human and machine intelligence working in combination to adequately defend corporate data, finances, and intellectual property.

Related Content

Sam McLane leads security engineering at Arctic Wolf, bringing over 20 years of security experience to the team. Prior to joining Arctic Wolf, Sam led product management and other sales functions for Blue Coat Systems' cloud security services business. Before Blue Coat, Sam ... View Full Bio
Comment  | 
Print  | 
More Insights
Comments
Oldest First  |  Newest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/25/2020
Hacking Yourself: Marie Moe and Pacemaker Security
Gary McGraw Ph.D., Co-founder Berryville Institute of Machine Learning,  9/21/2020
Startup Aims to Map and Track All the IT and Security Things
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
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
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15208
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, when determining the common dimension size of two tensors, TFLite uses a `DCHECK` which is no-op outside of debug compilation modes. Since the function always returns the dimension of the first tensor, malicious attackers can ...
CVE-2020-15209
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, a crafted TFLite model can force a node to have as input a tensor backed by a `nullptr` buffer. This can be achieved by changing a buffer index in the flatbuffer serialization to convert a read-only tensor to a read-write one....
CVE-2020-15210
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, if a TFLite saved model uses the same tensor as both input and output of an operator, then, depending on the operator, we can observe a segmentation fault or just memory corruption. We have patched the issue in d58c96946b and ...
CVE-2020-15211
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, saved models in the flatbuffer format use a double indexing scheme: a model has a set of subgraphs, each subgraph has a set of operators and each operator has a set of input/output tensors. The flatbuffer format uses indices f...
CVE-2020-15212
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger writes outside of bounds of heap allocated buffers by inserting negative elements in the segment ids tensor. Users having access to `segment_ids_data` can alter `output_index` and then write to outside of `outpu...