What evidence do auditors commonly ask for on SI-3(6) Malicious Code Protection | Testing and Verification?

System and information integrity policy; System and information integrity procedures; Procedures addressing malicious code protection; System design documentation; System configuration settings and associated documentation; Test cases.

What is the most common gap auditors find on SI-3(6)?

Malicious code protection is not tested with known benign code at the defined frequency

NIST SP 800-53 Rev 5 · SI - System and Information Integrity

`SI-3(6)` Malicious Code Protection | Testing and Verification

(a) Test malicious code protection mechanisms organization-defined frequency by introducing known benign code into the system; and (b) Verify that the detection of the code and the associated incident reporting occur.

Source: NIST SP 800-53 Rev 5, SI-3(6). 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 NIST SP 800-53 Rev 5 in the compliance library.

Base controls and their enhancements. Which apply follows the baseline you are assessed against (for example FedRAMP Moderate or High, or the low, moderate and high baselines of SP 800-53B). Text in square brackets is a parameter your organisation sets.

artefacts

held by a system

at each review

hard

to go live

Policy repository / GRC workspace

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

none for this control

periodic reviewEvidence produced at each review

Records providing evidence of test cases executed on malicious code protection mechanisms · Document repository
System audit records · Policy repository / GRC workspace
Test of Mechanisms supporting and/or implementing the testing and verification of malicious code protection capabilities · Document repository

governing documentDocuments that govern the control

System and information integrity policy · Policy repository / GRC workspace
System and information integrity procedures · Policy repository / GRC workspace
Procedures addressing malicious code protection · Policy repository / GRC workspace
System design documentation · Document repository
System configuration settings and associated documentation · Policy repository / GRC workspace
Test cases · Document repository
System security plan · Policy repository / GRC workspace

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

Common gaps auditors find

Malicious code protection is not tested with known benign code at the defined frequency
Tests do not verify that detection and incident reporting both occur

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

SI-3(4) Malicious Code Protection | Updates Only by Privileged Users · SI-3(8) Malicious Code Protection | Detect Unauthorized Commands