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?
Newest First  |  Oldest First  |  Threaded View
MarkSindone
50%
50%
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.
b haley
50%
50%
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.

 
ChristopherJames
0%
100%
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?


News
Inside the Ransomware Campaigns Targeting Exchange Servers
Kelly Sheridan, Staff Editor, Dark Reading,  4/2/2021
Commentary
Beyond MITRE ATT&CK: The Case for a New Cyber Kill Chain
Rik Turner, Principal Analyst, Infrastructure Solutions, Omdia,  3/30/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-29430
PUBLISHED: 2021-04-15
Sydent is a reference Matrix identity server. Sydent does not limit the size of requests it receives from HTTP clients. A malicious user could send an HTTP request with a very large body, leading to memory exhaustion and denial of service. Sydent also does not limit response size for requests it mak...
CVE-2021-29431
PUBLISHED: 2021-04-15
Sydent is a reference Matrix identity server. Sydent can be induced to send HTTP GET requests to internal systems, due to lack of parameter validation or IP address blacklisting. It is not possible to exfiltrate data or control request headers, but it might be possible to use the attack to perform a...
CVE-2021-29432
PUBLISHED: 2021-04-15
Sydent is a reference matrix identity server. A malicious user could abuse Sydent to send out arbitrary emails from the Sydent email address. This could be used to construct plausible phishing emails, for example. This issue has been fixed in 4469d1d.
CVE-2021-29447
PUBLISHED: 2021-04-15
Wordpress is an open source CMS. A user with the ability to upload files (like an Author) can exploit an XML parsing issue in the Media Library leading to XXE attacks. This requires WordPress installation to be using PHP 8. Access to internal files is possible in a successful XXE attack. This has be...
CVE-2021-30245
PUBLISHED: 2021-04-15
The project received a report that all versions of Apache OpenOffice through 4.1.8 can open non-http(s) hyperlinks. The problem has existed since about 2006 and the issue is also in 4.1.9. If the link is specifically crafted this could lead to untrusted code execution. It is always best practice to ...