Collect Audit Logs There's a predictable early move in a lot of intrusions: once an attacker is on a machine, they clear its local logs. If the only record of what happened lives on the same computer that was compromised, you've effectively handed the person you're investigating the ability to edit the evidence. Control 8.2 solves that by getting your logs off the individual machines and into a place an attacker can't quietly reach. If 8.1 was the decision about what to record, 8.2 is the act...

Trending at Forthright.

The Financial Risk of Healthcare Non-Compliance: Why “Good Enough” Security Is No Longer Enough

CIS IG1 Control 3.1: Data Management is Not a Policy Problem

CIS IG1 Control 2.3 — Why Unauthorized Software Is a Hidden Threat Lurking on “Trusted” Devices

CIS IG1 Control 2.2 — Why Running Supported Software Is a Security Requirement, Not an IT Preference
No Results Found
The page you requested could not be found. Try refining your search, or use the navigation above to locate the post.
