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.

Comments
Are You Listening to Your Kill Chain?
Threaded  |  Newest First  |  Oldest First
ChristopherJames
ChristopherJames,
User Rank: Strategist
1/22/2019 | 2:02:37 AM
Just Sniff them out
Well I don't think you're going to be a very successful hacker if you aren't at least able to hide long enough to get part of your hack in place right? Of course it will take a while for the systems to detect unauthorized entry. The most important part is how long it takes before they are discovered right?
b haley
b haley,
User Rank: Author
1/23/2019 | 11:24:16 AM
Re: Just Sniff them out
Thank you for reading and engaging in this discussion. You are right that it takes time for hackers to do their work and time to detect them. That part is a race condition. Can we spot, block and remove the hacker before they accomplish their goal. There are several sides to tilt the odds in our favor. the 3 I think are most important are actionable alerts, quick remediation, and proactive defenses.

If our detection tools can identify attacks quickly, clearly, with relevant information, and with certainty; we can take action. Looking at the forensics from major breaches, we captured great intelligence and usually identified the attack many times. However, the security team didn't get the details or have confidence that it was a real problem in all the noise. That feels like a problem with clarity and certainty, not identification. Most pitches I hear are all about speed to detect. My core premise is a tool giving alerts that cannot be acted on will be ignored. It gives only a false sense of security.

We have tools to quickly isolate and remediate machines. No excuse for not having those in place.

Proactive defenses provide some space between the attack and its completion. We see attacks where it is clear the hackers know what they are after in terms of servers, applications and sometimes passwords. By the time someone sees an IDS alert, that hacker has the info they were after. An IPS that shuts off access is speeding up the time to isolation, but is still in a race and false alarms impact operations. When users complain, security tends to loosen constraints, making detection slower.

Proactive defenses, those in place before the hacker attacks, at least slow the attack. Not talking about esoteric here. Firewalls, MFA, DLP, honeybots... all put speedbumps in the path and detection points. My gold standard for actionable alert is someone logging into a honeypot. Hackers are wasting time and giving away information on where they are, what they are after and whose credentials they are using. Honeypots weakness is a hacker must find the honeypot a more attractive target than real systems. With inside knowledge or good luck, the hacker avoids those defenses.

Another proactive example is my company builds tools to limit traffic from the server side (opposite the firewall approach). If you try to access a server from too far away (outside the data center, outside the cluster, outside the company...), an alert identifies the attack source, destination and target app. At the same time, the server cannot respond to the attacker so it is effectifly cloaked. While the attacker is trying to figure why this machine they found in LDAP won't respond, the security team is taking action. That gives a proactive defense with highly actionable alarms.

 
MarkSindone
MarkSindone,
User Rank: Moderator
1/27/2019 | 10:40:04 PM
They evolve just as much
There is just so much that we can do in the prevention of attacks. Regardless of how tough we think our security measures might be, attackers might just be even more advanced than we really are. That is simply how evolvement truly works and we need to stay ahead of the attackers in order to come up with a solution.


Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
The Promise and Reality of Cloud Security
Cloud security has been part of the cybersecurity conversation for years but has been on the sidelines for most enterprises. The shift to remote work during the COVID-19 pandemic and digital transformation projects have moved cloud infrastructure front-and-center as enterprises address the associated security risks. This report - a compilation of cutting-edge Black Hat research, in-depth Omdia analysis, and comprehensive Dark Reading reporting - explores how cloud security is rapidly evolving.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-48285
PUBLISHED: 2023-01-29
loadAsync in JSZip before 3.8.0 allows Directory Traversal via a crafted ZIP archive.
CVE-2023-0564
PUBLISHED: 2023-01-29
Weak Password Requirements in GitHub repository froxlor/froxlor prior to 2.0.10.
CVE-2021-4315
PUBLISHED: 2023-01-28
A vulnerability has been found in NYUCCL psiTurk up to 3.2.0 and classified as critical. This vulnerability affects unknown code of the file psiturk/experiment.py. The manipulation of the argument mode leads to improper neutralization of special elements used in a template engine. The exploit has be...
CVE-2023-0562
PUBLISHED: 2023-01-28
A vulnerability was found in PHPGurukul Bank Locker Management System 1.0. It has been rated as critical. Affected by this issue is some unknown functionality of the file index.php of the component Login. The manipulation of the argument username leads to sql injection. The attack may be launched re...
CVE-2023-0563
PUBLISHED: 2023-01-28
A vulnerability classified as problematic has been found in PHPGurukul Bank Locker Management System 1.0. This affects an unknown part of the file add-locker-form.php of the component Assign Locker. The manipulation of the argument ahname leads to cross site scripting. It is possible to initiate the...