3 ms·
My desktop has a 20MB security log that goes back 16 days, which seems like enough. If anything, stop spamming tens to hundreds of duplicate messages when cred
by Dylan16807 4y ago
My desktop has a 20MB security log that goes back 16 days, which seems like enough. If anything, stop spamming tens to hundreds of duplicate messages when credentials are read or group membership is enumerated.
System has 8 months, application has 10 months, and setup has 26 months.
- gerdesj 4y agoYes (20Mb), but so do AD DCs which is frankly lazy on MS dev's part. If a DC is such a big deal that it requires rather more cash to buy than a "workstation" edition of Windows, then I'd like to see more attention to detail. By contrast a Linux box running systemd/journald by default will leave 10% disc space free when logging. That's enough to keep a filesystem honest! 20Mb on a DC - even one for a small site like mine will cycle quite often. I really recommend that you extend your logs to cover six months or more. It will cost you maybe a gigabyte or 10. Very little these days (my first HD was 20MB, yes: megabytes). However if you need to get some details from the past - very handy.
- msm_ 4y agoIt's absolutely not enough for APT investigation. Average attacks lengths are in months, infections sometimes span multiple years. Especially since we're talking about a backdoor (ransomware operators tend to move more quickly)
- Dylan16807 4y agoIt's not enough for that, but that bar is too high. Unless the logs are very small, you should not be keeping years of them. I still say 20MB is enough for a desktop.
- gerdesj 4y agoDepends on the desktop. Mine does quite a lot of stuff. /var/log is 8.3Gb and the journal is probably a monster. Your use case is probably different to mine - I'm a security officer for my firm.