CC6.8: Malicious software

The company prevents and detects unauthorized or malicious software on endpoints and in its software supply chain, and keeps systems patched.

Category: Security (common criteria, required in every SOC 2 report) · Series: CC6 (Logical and physical access controls) · TSC 2017 (2022 points of focus)

That summary is Policyseed’s own paraphrase, written to be read next to the policy sections below. The authoritative wording is the AICPA’s Trust Services Criteria, which the CPA firm tests your controls against during the examination.

Policies that address CC6.8

The Policyseed crosswalk points CC6.8 at 3 policies. Each link opens the full sample text at the section an auditor would read. Section 4 holds the statements management commits to; section 5 holds the procedures that produce evidence.

Evidence examples for CC6.8

Artifacts a company of 5 to 200 people can realistically produce. The Audit Kit’s evidence checklist lists them per policy with an owner column so each one has a name against it before the examination.

  • Endpoint protection or EDR console report showing coverage of all managed devices
  • MDM configuration restricting software installation to approved sources
  • Dependency scanning configuration and recent results from the source control platform
  • Patch compliance report from MDM for operating system updates

Related criteria in CC6 (Logical and physical access controls)

Previous: CC6.7 Data in transit and on removable media. Next: CC7.1 Detecting vulnerabilities and configuration changes. All 38 criteria are listed on the template index.

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.