News for hackers. Stuff that matters.
Re:Practical Linux Hardening Guide by Someone1234 on Thursday January 24, 2019 @05:17PM (#18993600)
Well said.

"Log noise" is a legitimate security concern all by itself. It is actually disappointing how rarely it is discussed, and how in this world of "AI everywhere" there's no great smart AI log analysers to reduce the signal:noise.

Moving the SSH port might "only" reduce noise, but that's a legitimate security goal in its own right.

Re:Practical Linux Hardening Guide by seanwilson on Friday January 25, 2019 @09:10AM (#18997944)
> "Log noise" is a legitimate security concern all by itself. It is actually disappointing how rarely it is discussed, and how in this world of "AI everywhere" there's no great smart AI log analysers to reduce the signal:noise.

That's because after many people learn about not using "security through obscurity" they apply the rule without thinking as if obscurity never has any benefit for anything.

Re:Practical Linux Hardening Guide by thaumaturgy on Thursday January 24, 2019 @06:36PM (#18994150)
That's because people can't agree on what is or isn't valuable.

For instance, if I (or my software anyway) see a bunch of sshd login attempts from some IP, and then that IP decides to try imap ... yeah, that's getting insta-blocked.

And that's hard to do if you decide to just ignore the sshd attempts.

Re:Practical Linux Hardening Guide by hawski on Friday January 25, 2019 @03:57AM (#18996550)
Could additional honey pot on 22 help? Run sshd on non-standard port and honey pot on 22. Then automatically ban all the hosts that would connect to it. There could be a concern for a mistake, so then ban for limited time at first or something.