3 ms·
There is so much to comment on and digest in this report, but the lifecycle of an attack diagram[1] on page 31 (figure 164) is something every software develope
by strict9 8y ago
There is so much to comment on and digest in this report, but the lifecycle of an attack diagram[1] on page 31 (figure 164) is something every software developer should burn in to memory.
It is easy to fall in the trap of seeing the most miniscule of vulnerabilities and dismissing it as "no one could ever possibly utilize that as a vector, it's not critical."
But that miniscule vulnerability becomes a single link in a ladder to everything in the system. Every seemingly-small vulnerability matters, like this painfully shows.
[1] referenced here: https://blog.hellobloom.io/how-hard-was-the-equifax-hack-a3bae36f9e6f https://blog.hellobloom.io/how-hard-was-the-equifax-hack-a3b...
- jacquesm 8y agoThat's something you keep seeing as a pattern in many hacks. It is rarely just one mistake, usually a chain of small ones, each of which doesn't look all that bad by itself.
- freehunter 8y agoThat's why technologies like SIEMs exist. No number of humans could look at logs across all the various systems and spot anomalies within them, but a SIEM can. But only if it's turned on, ingesting data, running a useful ruleset, and crucially: only if someone is watching the output.