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.

Reactive or Proactive? Making the Case for New Kill Chains
Newest First  |  Oldest First  |  Threaded View
User Rank: Ninja
7/6/2018 | 1:21:43 PM
Lockheed Martin at BlackHat and on GitHub
Back in 2013 DR did another article on kill chain and how Lockheed Martin approached that process.  In fact, Lockheed did a presentation at Black Hat and the conclusion of that paper back in 2012 was that their "current batch of Intrusion Detection products are clearly insufficient against today's targeted modern threats." Their presentation laid out "a series of models for how to rethink the problem from the ground up. Stepping back from our need to only instrument highly actionable events is the first and most important realization that we have outlined. The event pipeline provides a framework to understand how low confidence events can and should be assimilated into an effective intrusion detection program."

Jump to 2018 and that declaration of intent to develop a better kill chain process has Lockheed leading the industry with their Cyber Kill Chain, notably "proactive" and to some extent "predictive" in character.  As cool as this all sounds, I'm afraid that the industry still needs to bring this model and idea of cyber defense down to a more digestible level.  At Black Hat Lockheed sounded like the next step in cyber defense was ready to be revealed, but for the everyday security analyst, Cyber Kill Chain may come off like yet another expensive bloatware Enterprise product.  Luckily, Lockheed Martin has shared some of its tech on GitHub with several threat analysis and prevention tools that it has open-sourced.  Better understanding of kill chains and the attack phases may come from the FOSS community in the short term, with easily accessible and free implementations to play with.

In addition to the LM GitHub code, I recommend Security Onion (SO), a GNU/Linux OS for security professionals, to play with code related to the newer kill chain models.





Navigating Security in the Cloud
Diya Jolly, Chief Product Officer, Okta,  12/4/2019
US Sets $5 Million Bounty For Russian Hacker Behind Zeus Banking Thefts
Jai Vijayan, Contributing Writer,  12/5/2019
Register for Dark Reading Newsletters
White Papers
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Our Endpoint Protection system is a little outdated... 
Current Issue
Navigating the Deluge of Security Data
In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2019-12-11
Tableau Server 10.3 through 2019.4 on Windows and Linux allows XSS via the embeddedAuthRedirect page.
PUBLISHED: 2019-12-11
Yabasic 2.86.1 has a heap-based buffer overflow in the yylex() function in flex.c via a crafted BASIC source file.
PUBLISHED: 2019-12-11
On Moxa EDS-G508E, EDS-G512E, and EDS-G516E devices (with firmware through 6.0), denial of service can occur via PROFINET DCE-RPC endpoint discovery packets.
PUBLISHED: 2019-12-11
The VisualEditor extension through 1.34 for MediaWiki allows XSS via pasted content containing an element with a data-ve-clipboard-key attribute.
PUBLISHED: 2019-12-11
MediaWiki through 1.33.1 allows attackers to bypass the Title_blacklist protection mechanism by starting with an arbitrary title, establishing a non-resolvable redirect for the associated page, and using redirect=1 in the action API when editing that page.