What evidence do auditors commonly ask for on SI-2 Flaw Remediation?

Patch process covering acquired and embedded components; Tracking of fixes pending with suppliers; Compensating controls where no fix is available; Escalation route to suppliers.

What is the most common gap auditors find on SI-2?

flaws in supplier products tracked nowhere because the fix is not ours

NIST SP 800-161 Rev 1 (supply chain) · C-SCRM Family: System and Information Integrity

`SI-2` Flaw Remediation

Remediates flaws in acquired components, where the fix depends on a supplier the organization does not control.

Source: NIST SP 800-161 Rev 1 (supply chain), SI-2. 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-161 Rev 1 (supply chain) in the compliance library.

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

none for this control

governing documentDocuments that govern the control

Patch process covering acquired and embedded components · Policy repository / GRC workspace
Tracking of fixes pending with suppliers · Policy repository / GRC workspace
Compensating controls where no fix is available · Policy repository / GRC workspace
Escalation route to suppliers · 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

flaws in supplier products tracked nowhere because the fix is not ours
no compensating control while waiting for a supplier fix

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-1 Policy and Procedures · SI-3 Malicious Code Protection