What evidence do auditors commonly ask for on PE-19(1) Information Leakage | National Emissions Policies and Procedures?

Physical and environmental protection policy; Procedures addressing information leakage that comply with national emissions and TEMPEST policies and procedures; System component design documentation; System configuration settings and associated documentation system security plan; Test of Information system components for compliance with national emissions and TEMPEST policies and procedures.

What is the most common gap auditors find on PE-19(1)?

Components and communications are not protected according to national emissions security policies

NIST SP 800-53 Rev 5 · PE - Physical and Environmental Protection

`PE-19(1)` Information Leakage | National Emissions Policies and Procedures

Protect system components, associated data communications, and networks in accordance with national Emissions Security policies and procedures based on the security category or classification of the information.

Source: NIST SP 800-53 Rev 5, PE-19(1). 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

Test of Information system components for compliance with national emissions and TEMPEST policies and procedures · Physical access / facilities

governing documentDocuments that govern the control

Physical and environmental protection policy · Policy repository / GRC workspace
Procedures addressing information leakage that comply with national emissions and TEMPEST policies and procedures · Policy repository / GRC workspace
System component design documentation · Policy repository / GRC workspace
System configuration settings and associated documentation 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

Components and communications are not protected according to national emissions security policies
The information's security category was not used to determine emissions security requirements

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

PE-19 Information Leakage · PE-20 Asset Monitoring and Tracking