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.

Endpoint

4/20/2017
02:00 PM
Ofer Amitai
Ofer Amitai
Commentary
Connect Directly
LinkedIn
RSS
E-Mail vvv
100%
0%

Kill Chain & the Internet of Things

IoT "things" such as security cameras, smart thermostats and wearables are particularly easy targets for kill chain intruders, but a layered approach to security can help thwart an attack.

The concept of a kill chain attack has been around for several years. The term originated from the military, but computer scientists at Lockheed-Martin Corporation were the first to use this term in the field of cybersecurity, describing a kill chain framework to defend computer networks in 2011. Its relevance has taken on new meaning in our current era of IoT devices and botnet attacks. IDC predicts that by 2020, 30 billion connected “things” will be a part of the digital infrastructure.

The  “kill chain” lays out the stages of a cyber-attack, starting from early reconnaissance to completion of the attack with the goal of data theft and enabling more attacks. These stages are:

1. Reconnaissance – The intruder selects its target device, researches it, and searches for vulnerabilities

2. Weaponization - Intruder uses a remote access malware weapon, such as a virus or worm, addressing a vulnerability  

3. Delivery - Intruder transmits weapon to the target device, whether through e-mail attachments, websites, USB drives, etc.

4. Exploitation - Malware weapons program code to triggers the attack. This then takes action on target network to exploit vulnerability.

5. Installation - Malware weapon installs access points for the intruder to use.

6. Command and Control – Malware then enables intruder to have "hands on the keyboard" persistent access to the target network, also enabling future attacks.

IoT devices, particularly items like security cameras, smart thermostats, wearables, and even coffee makers, are easy targets for kill chain intruders. They often have little or no security system, making step #2 of the kill chain rather easy.  For example, last year 80 Sony IP security camera models were found to have back doors, giving hackers easy access.

Don't Break the Kill Chain! Prevent it 
The best way to prevent a kill chain from infiltrating enterprise IoT security is to invest in a layered approach. There are four steps to this approach:

1. Assessment:  Start with a  network discovery process of all the existing IoT devices, including managed and partially managed devices. Understand what each type of device is, what operating system it is running on and which application and processes are installed on it.

2.  Segmentation:  IoT devices should not be in the same network segment as other devices, or within reach of the organization’s mission critical systems and data. Deploy firewalls between these segments to prevent “things”  from reaching the “crown jewels” of your network.

3. Detection:  Regularly analyze your network behavior to detect every IoT device which joins the network, and carefully examine if it behaves similarly to other typical devices. A compromised device or a fake device might look the same but behave differently.

4. Response:  Because manual alerts can take hours or even days to process, the best practice should involve some type of backup plan that will block or limit the access of a specific device within seconds.

This layered approach is designed to both prevent the likelihood of a kill chain attack, and also to break a live attack if one does occur. Once a vulnerability in the IoT device is detected and an attack is underway, breaking the final steps of the kill chain is most crucial, as it is often where the biggest gap lies in an organization’s advanced threat protection strategy. These last stages provide the best picture of who might be attacking and infecting your corporate network. They also require the least amount of time to remediate. For example, if a vulnerable security camera continues to communicate to an Internet forum, even after segmentation, it’s an easy call to block it entirely from the network. 

[Check out the two-day Dark Reading Cybersecurity Crash Course at Interop ITX, May 15 & 16, where Dark Reading editors and some of the industry's top cybersecurity experts will share the latest data security trends and best practices.]

Related Content:

 

Ofer Amitai is CEO and co-founder of Portnox, where he is responsible for day-to-day operations and setting the company's strategic direction. He has over 20 years' experience in network security, during which time he established the first IT security team in the Israeli Air ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
COVID-19: Latest Security News & Commentary
Dark Reading Staff 6/5/2020
Abandoned Apps May Pose Security Risk to Mobile Devices
Robert Lemos, Contributing Writer,  5/29/2020
How AI and Automation Can Help Bridge the Cybersecurity Talent Gap
Peter Barker, Chief Product Officer at ForgeRock,  6/1/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: What? IT said I needed virus protection!
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-9074
PUBLISHED: 2020-06-05
Huawei Smartphones HONOR 20 PRO;Honor View 20;HONOR 20 have an improper handling of exceptional condition Vulnerability. A component cannot deal with an exception correctly. Attackers can exploit this vulnerability by sending malformed message. This could compromise normal service of affected phones...
CVE-2020-9859
PUBLISHED: 2020-06-05
A memory consumption issue was addressed with improved memory handling. This issue is fixed in iOS 13.5.1 and iPadOS 13.5.1, macOS Catalina 10.15.5 Supplemental Update, tvOS 13.4.6, watchOS 6.2.6. An application may be able to execute arbitrary code with kernel privileges.
CVE-2020-11975
PUBLISHED: 2020-06-05
Apache Unomi allows conditions to use OGNL scripting which offers the possibility to call static Java classes from the JDK that could execute code with the permission level of the running Java process.
CVE-2020-12723
PUBLISHED: 2020-06-05
regcomp.c in Perl before 5.30.3 allows a buffer overflow via a crafted regular expression because of recursive S_study_chunk calls.
CVE-2020-1883
PUBLISHED: 2020-06-05
Huawei products NIP6800;Secospace USG6600;USG9500 have a memory leak vulnerability. An attacker with high privileges exploits this vulnerability by continuously performing specific operations. Successful exploitation of this vulnerability can cause service abnormal.