EvidenceSheet

CC6.8 Preventing and detecting unauthorised or malicious software

Controls prevent, or detect and respond to, the introduction of unauthorised or malicious software. Points of focus: only authorised people can install applications and software; changes to software and configuration that may signal malicious code are detected; software is implemented through a management-defined change process; utility software able to bypass normal operating or security procedures is restricted to authorised people and its use monitored (added in 2022); anti-malware on servers and endpoints is configured, kept current and used to remove what it detects; and assets received from outside or returned to the organisation are scanned and cleaned before joining the network.

Source: SOC 2 (2017 Trust Services Criteria), CC6.8. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open SOC 2 (2017 Trust Services Criteria) in the compliance library.

These are criteria, not controls: you design controls that meet them, and which criteria are in scope follows the categories your report covers (Security always; Availability, Confidentiality, Processing Integrity and Privacy only if chosen). A Type 2 report tests that the controls operated across the period, so the evidence asked for is samples across that period, not one copy.

5
artefacts
2
held by a system
1
at each review
moderate
to go live
Endpoint management (MDM / EDR)
where the evidence lives
teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

  • Endpoint protection coverage report across servers and workstations · Endpoint management (MDM / EDR)
  • File integrity or configuration drift monitoring alerts · Endpoint management (MDM / EDR)

periodic reviewEvidence produced at each review

  • Malware detection and remediation records · Endpoint management (MDM / EDR)

governing documentDocuments that govern the control

  • Local administrator and software installation restrictions · Policy repository / GRC workspace
  • List of privileged utility tools, who may run them, and usage monitoring · Policy repository / GRC workspace

First move

Start with the 2 of 5 artefacts that already live in a system (Endpoint management (MDM / EDR)); keep the periodic reviews but log each one as a dated record with a named reviewer.

Common gaps auditors find

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

CC6.7 Restricting and protecting information in transmission, movement and removal · CC7.1 Detecting configuration changes and new vulnerabilities