What evidence do auditors commonly ask for on SI-14 Non-persistence?

System and information integrity policy; System and information integrity procedures; Procedures addressing non-persistence for system components; System design documentation; System configuration settings and associated documentation; System audit records.

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

The defined components and services are persistent rather than initiated in a known state and terminated

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

`SI-14` Non-persistence

Implement non-persistent organization-defined system components and services that are initiated in a known state and terminated Selection (one or more): upon end of session of use; periodically at [organization-defined frequency].

Source: NIST SP 800-53 Rev 5, SI-14. 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

Test of Automated mechanisms supporting and/or implementing the initiation and termination of non-persistent components · HR system / LMS

periodic reviewEvidence produced at each review

System audit records · Policy repository / GRC workspace

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 non-persistence for system components · Policy repository / GRC workspace
System design documentation · Document repository
System configuration settings and associated documentation · Policy repository / GRC workspace
System security plan · Policy repository / GRC workspace

First move

Mostly documents and reviews. Pull the 1 system-held artefact from your HR system / LMS on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.

Common gaps auditors find

The defined components and services are persistent rather than initiated in a known state and terminated
Non-persistent components are not terminated at session end or the defined frequency

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-13(5) Predictable Failure Prevention | Failover Capability · SI-14(1) Non-persistence | Refresh from Trusted Sources