Re:Brute.Fail Watch brute force attacks in real time
by wkat4242 on Saturday June 03, 2023 @05:46AM
(#36175162)
That's still not really security but just a nuisance mitigation IMO :)
[ Parent
| on HN ]
Re:Brute.Fail Watch brute force attacks in real time
by Gordonjcp on Saturday June 03, 2023 @05:51AM
(#36175189)
It's both, really. If you're not getting scanned, you've reduced an attack surface, and that can only be good.
Re:Brute.Fail Watch brute force attacks in real time
by wkat4242 on Saturday June 03, 2023 @08:19AM
(#36176029)
Well, I view it as hiding an attack surface. It's still there, just harder to find.
But I know I'm a bit of an absolutist on security.
Re:Brute.Fail Watch brute force attacks in real time
by Gordonjcp on Saturday June 03, 2023 @06:12PM
(#36181020)
You put a lock on your bike.
But you also put it in the shed, and lock the shed.
Re:Brute.Fail Watch brute force attacks in real time
by jlund-molfese on Saturday June 03, 2023 @09:23AM
(#36176472)
Nuisance mitigations are part of security too! Fewer irrelevant notifications makes it more likely you’ll notice when something really is a problem.
It’s like how an adversary might launch a DDoS attack at the same time as they exploit a SQL injection vulnerability to exfiltrate credit card information. Filling up logs and alerts overwhelms the blue team and makes it harder to notice the quieter, but more dangerous attack.
Re:Brute.Fail Watch brute force attacks in real time
by oh_sigh on Saturday June 03, 2023 @10:24AM
(#36176941)
Security through obscurity actually is security, and is perfectly valid to use with a defense in depth strategy. The problem is when obscurity is the only defense.
Re:Brute.Fail Watch brute force attacks in real time
by bigkm on Saturday June 03, 2023 @12:54PM
(#36178244)
I agree, these attacks are looking for systems that have pretty default security, and by running on a different port you avoid all this automated chaos because you're non default now. Like scam emails with typos, a way to filter out the naïve people.