Does SOC 2 require antivirus? What CC6.8 asks, and Macs, Linux and servers

Updated

Not by name. The criterion that covers it, CC6.8, asks for controls "to prevent or detect and act upon the introduction of unauthorized or malicious software" and names no product. Antivirus is one of five things the audit firm KirkpatrickPrice says its auditors look at under that criterion. On Windows, the vendors fetched for this page say the built-in Microsoft Defender is enough when it is on everywhere. On Macs and Linux they are less strict, but they are vendors, and your CPA firm decides for your system.

What CC6.8 asks for

KirkpatrickPrice, a firm that performs SOC 2 examinations, quotes the criterion and lists what "an auditor will assess" under it. The organization:

  1. "Restricts who can install software on assets"
  2. "Detects unauthorized changes to your software and configuration parameters"
  3. "Uses a defined change control process"
  4. "Uses antivirus and anti-malware software"
  5. "Scans information assets from outside of your organization for malware and other unauthorized software"

Joseph Kirkpatrick wrote this in February 2019 (KirkpatrickPrice). Two of his points matter for a small team. First, prevention starts with admin rights: people who may not install software should not be administrators, and if they are, "you would want some type of an alert and some type of log". Second, detection needs someone on the receiving end: "a malware, antivirus, or some other log that's generated from one of your security systems that's able to monitor that and alert the proper security officer". So the product is a fifth of the list, and an alert nobody reads covers less than it seems.

Windows, Mac, Linux and servers: what the sources say

Four pages were fetched for this guide. Only one is from an audit firm, and it does not discuss operating systems. The other three are vendors that sell compliance software or a device agent, so read the table as their experience, not as a rule.

SourceWho they areWhat it says
KirkpatrickPrice (Joseph Kirkpatrick, 22 February 2019)Audit firm that performs SOC 2 examinationsAntivirus and anti-malware software is one of five things assessed under CC6.8. No operating system detail
Strike Graph help center (Elliott Harnagel, undated)Sells a compliance platform"auditors like to see antivirus enabled for any Windows laptops, but they are less stringent for Mac and Linux machines". On Mac and Linux computers, "Antivirus is not needed". On servers, auditors "only want to see antivirus on Windows servers"
Secureframe help center (Brady Price, 5 August 2026)Sells a compliance platform"Most frameworks expect endpoint antivirus or equivalent malware protection on company devices. Built-in options often meet the baseline requirement." Names Microsoft Defender for Windows and XProtect for macOS
1Password blog (Jason Meller, 9 September 2024; first written in 2022)Sells a device agent that reports on these settingsArgues that the built-in macOS protections (XProtect, Gatekeeper, System Integrity Protection) can stand without third-party antivirus, and that the gap is reporting: macOS has no fleet-wide report, which it fills with osquery

Sources: (KirkpatrickPrice) (Strike Graph) (Secureframe) (1Password). The two help centers differ in tone: Strike Graph says antivirus is not needed on a Mac, while Secureframe says most frameworks expect antivirus "or equivalent malware protection" and points to the built-in protection as the equivalent. Both end up in the same place for a Mac team: no extra product, but a record that the built-in protection is on. No audit firm page that answers the Mac and Linux question was found for this guide.

Strike Graph adds two points worth keeping. Device management software that manages antivirus "is not a requirement for SOC 2", though it helps; whether you need an MDM at all is in does SOC 2 require MDM? And whatever you decide, "your stated control description accurately reflects how your organization implements this control". If your control says antivirus runs on all workstations and servers, the auditor tests all workstations and servers.

What your own policy already says

If you use the Policyseed generator, you have already written the rule, and it is the rule an auditor will test. Policyseed sells a kit, so read the text below as one example of how to write this down. The excerpts are rendered from the policy templates for the Northwind Cloud Inc sample intake, once with an MDM tool and once with none, so they change when a template does.

Malware protection on laptops and desktops (Endpoint and Workstation Security Policy, 4.7)

With an MDM tool: Every laptop and desktop runs the built-in or company-approved endpoint protection with real-time malware scanning enabled and the host firewall turned on. Alerts from endpoint protection are reviewed by the Security Owner and forwarded to Datadog where the tooling supports it. Browsers keep their built-in protection against known malicious and phishing sites turned on, and where your MDM tool supports it a DNS or web filtering profile blocks known malicious domains on every company endpoint.
With none: Every laptop and desktop runs the built-in or company-approved endpoint protection with real-time malware scanning enabled and the host firewall turned on. Alerts from endpoint protection are reviewed by the Security Owner and forwarded to Datadog where the tooling supports it. Browsers keep their built-in protection against known malicious and phishing sites turned on.

Who may install software (Endpoint and Workstation Security Policy, 4.8)

Personnel work from a standard user account. Local administrator rights are granted only where a role requires them, are recorded in the device inventory and are reviewed quarterly. Software is installed only from official vendor sources or app stores, and browser extensions with access to page content require Security Owner approval.

How the configuration is enforced (Endpoint and Workstation Security Policy, 4.3)

With an MDM tool: Every company endpoint is enrolled in your MDM tool before it is issued, and enrollment may not be removed by the user. your MDM tool enforces the configuration in Sections 4.4 to 4.8 and reports compliance to the Security Owner.
With none: Because Northwind Cloud Inc does not currently operate a mobile device management platform, every endpoint is configured against the written baseline checklist before issue, and each user attests quarterly that the configuration in Sections 4.4 to 4.8 remains in place, attaching system screenshots or reports as evidence.

Three things to notice. First, item 4.7 says "the built-in or company-approved endpoint protection", so a fleet of Macs on XProtect, or Windows laptops on Defender, is inside the written rule; no product purchase is promised. Second, it promises more than a scanner: the host firewall on, and alerts reviewed by the Security Owner, which is KirkpatrickPrice's detection point. Third, item 4.8 covers the first line of the audit firm's list, standard user accounts and recorded admin rights, which many teams forget when they think of CC6.8 as "antivirus".

Evidence to keep

  • A per-device record that protection is on. With an MDM tool, its compliance report. Without one, item 4.3 above describes the quarterly attestation with screenshots; each capture should show the device, the date and the setting (what a usable capture shows is in SOC 2 evidence screenshots).
  • The device list the record is checked against. A per-device record proves little if a laptop is missing from the list. The free asset inventory template has a device tab with the assigned user, operating system, disk encryption and MDM columns. It has no endpoint protection column yet, so record that status in its notes column.
  • The alert review. Who receives endpoint protection alerts, and a dated note of what was looked at. A malware alert on a laptop with production access is a SEV2 incident in the generated incident response plan.
  • Admin rights. The list of people with local administrator rights and the quarterly review of it, from item 4.8.

For a Type II report, the auditor looks at the whole observation period, so one dated record at the end is weaker than one per quarter. The evidence checklist lists the rest of the endpoint evidence.

Servers and containers

The generated Endpoint and Workstation Security Policy covers laptops, desktops and phones only; its scope says servers, containers and cloud workloads are covered by the Network and Infrastructure Security Policy. That policy has no item on malware protection for servers. For a team on Linux hosts and containers, that matches Strike Graph's experience that auditors ask for antivirus on Windows servers only (Strike Graph). If you run Windows servers, add a statement on their malware protection before you approve the set, because nothing in it covers them today.

No fetched source covers container images under CC6.8. What the generated set does promise is scanning:

Where vulnerabilities are found (Vulnerability and Patch Management Policy, 4.1)

With an MDM tool: Northwind Cloud Inc maintains continuous discovery across in-scope assets from at least these sources: software composition and static analysis in GitHub Actions on every pull request and on a schedule; secret scanning in GitHub; container image scanning before deployment and on a recurring schedule; the native security posture service of each platform in AWS and Vercel; endpoint patch and compliance reporting from your MDM tool; an annual independent penetration test; vendor advisories; published threat intelligence including the CISA Known Exploited Vulnerabilities catalog; and reports received through the disclosure channel.
With none: Northwind Cloud Inc maintains continuous discovery across in-scope assets from at least these sources: software composition and static analysis in GitHub Actions on every pull request and on a schedule; secret scanning in GitHub; container image scanning before deployment and on a recurring schedule; the native security posture service of each platform in AWS and Vercel; endpoint patch and compliance reporting; an annual independent penetration test; vendor advisories; published threat intelligence including the CISA Known Exploited Vulnerabilities catalog; and reports received through the disclosure channel.

That is closest to the fifth line of KirkpatrickPrice's list, scanning assets for malware and other unauthorized software. How often to scan is in SOC 2 vulnerability scanning frequency.

A short routine for a small team

  1. Decide per operating system and write it down: Defender on Windows, the built-in protection on macOS, and either nothing or a tool such as ClamAV on Linux laptops (Strike Graph mentions it as "a free and easy-to-use antivirus solution"). Make the written control match.
  2. Turn it on everywhere and keep the setting on with your MDM tool or the baseline checklist.
  3. Route the alerts to one named person and review them on a schedule.
  4. Take admin rights away from people who do not need them, and record the exceptions.
  5. Record it each quarter: the MDM report or the attestations, checked against the device list.

Frequently asked questions

Does SOC 2 require antivirus?
Not by name. The criterion, CC6.8, asks for controls "to prevent or detect and act upon the introduction of unauthorized or malicious software", as KirkpatrickPrice quotes it. Antivirus and anti-malware software is one of five things that audit firm says its auditors assess under CC6.8; the others are who may install software, detecting unauthorized changes, a change control process and scanning assets from outside. In practice most teams run malware protection on their laptops, and the built-in tools are often enough according to the vendors fetched for this page.
Is the built-in protection on a Mac enough?
Three vendor sources lean that way, and none is an audit firm. Strike Graph's help center says that on Mac computers "Antivirus is not needed". Secureframe says "macOS includes built-in protections such as XProtect" and that built-in options "often meet the baseline requirement". 1Password's Jason Meller argues at length that XProtect, Gatekeeper and System Integrity Protection can stand without a third-party product, as long as you can report their state across the fleet. The audit firm source on this page does not discuss operating systems. Ask your CPA firm before you rely on it, and keep a dated record that the built-in protections are switched on.
Is Microsoft Defender enough on Windows?
Both vendor sources that address it say yes. Strike Graph: "the native Windows Defender antivirus suffices as long as it is enabled on all employee laptops". Secureframe: "Microsoft Defender meets the antivirus requirement for Windows." The condition is the one in both quotes: it has to be on, on every laptop, and you need a record that shows it.
Do we need EDR?
No source fetched for this page says SOC 2 requires endpoint detection and response. Secureframe mentions EDR only as an option for intrusion detection, "alongside or instead of network-based tools". KirkpatrickPrice's point is about detection and alerting: you need a malware, antivirus or other security log that alerts "the proper security officer". An EDR product is one way to get that; the built-in protection with a reviewed alert is another.
Do Linux servers and containers need antivirus?
Strike Graph says auditors generally do not ask for it on Linux servers and "only want to see antivirus on Windows servers". It is the only fetched source that addresses servers, so treat it as one vendor's experience. No fetched source covers container images. The generated Vulnerability and Patch Management Policy scans container images before deployment and on a schedule, which is the control most container teams show instead.
What about phones?
None of the fetched sources discusses phones under CC6.8. The generated Endpoint and Workstation Security Policy puts the endpoint protection rule on "every laptop and desktop", not on phones; for phones it asks for a passcode, encryption and current updates. If a customer questionnaire asks about malware protection on mobile devices, answer what you actually run.

Policyseed provides governance policy templates and AI tailoring. It is not legal advice and not a compliance guarantee. Management adopts the policies; the CPA firm performs the SOC 2 examination.