Re:How to properly manage SSH keys for server access
by nurettin on Sunday September 27, 2020 @01:36AM
(#24604454)
Shipping software logs is just useless bureaucracy. Don't confuse it with shipping firewall/ssh/rdp logs which is an absolute must for telling how/when you were pwned. Hacker will just disable app/db logs, update their user as admin, dump the db and proceed with the cryptofuckery.
Re:How to properly manage SSH keys for server access
by throwawayinfo on Sunday September 27, 2020 @11:03AM
(#24607137)
Eh? In my experience logs are some of the most valuable data produced by software. Debugging, experiments, software quality, auth trails, analytics, customer support, privacy, security, audit/compliance and abuse are all seriously useful applications for logs. Throwing them away is like dumping gold.
Re:How to properly manage SSH keys for server access
by nurettin on Friday October 02, 2020 @03:18PM
(#24666075)
Yes, nobody said throw away application logs. That's dumb.
Re:How to properly manage SSH keys for server access
by jdxcode on Saturday September 26, 2020 @09:03PM
(#24603383)
I imagine basically any form of compliance would require centralizing logs in some form
Re:How to properly manage SSH keys for server access
by f0rfun on Saturday September 26, 2020 @11:12PM
(#24603925)
and for audit. Audit/Compliance is one of the worst yet valid reasons to introduce complexity, redundancy and all sorts of costs into projects. It's also why some people earn a living out of it purely.
Proper Information Security policy is one very good reason. If a box is compromised, you don't want the logs being tampered with.
You ship the logs to a central, dedicated server so that a clear audit trail can be established.