SOC2-CC6-ENDPOINT

Endpoint Protection (EDR/Antivirus)

preventivemedium effectivenessWeekly

What this control does

Endpoint detection and response software on all corporate laptops and workstations used to access production systems or customer data.

Implementation guidance

Deploy an EDR solution (CrowdStrike, SentinelOne, Microsoft Defender) on all corporate devices via MDM. Set policy to alert on malware detection within 1 hour. Review unprotected device alerts weekly. For BYOD, require a managed profile via MDM as a minimum.

Requirements satisfied

CC6.8

Why it matters

Unmanaged or unprotected endpoints are the primary attack vector for malware, ransomware, and data exfiltration—especially devices accessing production systems or customer data. Without EDR/antivirus, a compromised device can move laterally across your infrastructure and bypass perimeter defenses. A missing or disabled protection agent leaves your organization exposed to the most common breach scenarios auditors and regulators investigate.

Evidence to collect

  • MDM inventory report showing all corporate devices with EDR/antivirus agent version and last check-in timestamp
  • Alert rule configuration from EDR console showing malware detection alert threshold and routing to SIEM or ticketing system
  • Weekly endpoint compliance report listing non-compliant, unprotected, or overdue devices (last 4 weeks)
  • Quarantine/detection log from EDR showing sample malware alerts with response actions taken in past 30 days

Testing procedure

Request the MDM endpoint inventory filtered for devices accessing production or customer data; verify 100% have an active EDR/antivirus agent deployed. Check EDR console alert settings to confirm malware detections trigger notifications within 1 hour. Sample recent malware detection events and verify each was logged with containment action (quarantine, block, alert to SOC). Interview the compliance lead on their weekly unprotected device review process and inspect the last 4 weekly reports for completeness.

Common gotchas

Organizations often exclude developer or QA laptops from EDR policy believing they don't touch production, then fail to track which devices actually *do* access customer data—leading to coverage gaps. Another common mistake is deploying EDR but disabling real-time scanning to reduce CPU impact, leaving the agent installed but ineffective; always verify real-time scanning is enabled via group policy or MDM configuration, not just agent presence.