What evidence do auditors commonly ask for on SI-4(13) System Monitoring | Analyze Traffic and Event Patterns?

System and information integrity policy; System and information integrity procedures; Procedures addressing system monitoring tools and techniques; System design documentation; System monitoring tools and techniques documentation; System configuration settings and associated documentation.

What is the most common gap auditors find on SI-4(13)?

No profiles of common traffic and event patterns have been developed

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

`SI-4(13)` System Monitoring | Analyze Traffic and Event Patterns

(a) Analyze communications traffic and event patterns for the system; (b) Develop profiles representing common traffic and event patterns; and (c) Use the traffic and event profiles in tuning system-monitoring devices.

Source: NIST SP 800-53 Rev 5, SI-4(13). 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 Organizational processes for intrusion detection and system monitoring; mechanisms supporting and/or implementing intrusion detection and system monitoring capabilities; mechanisms supporting and/or implementing the analysis of communications traffic and event patterns · SIEM / log platform

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 system monitoring tools and techniques · Policy repository / GRC workspace
System design documentation · Document repository
System monitoring tools and techniques documentation · Policy repository / GRC workspace
System configuration settings and associated documentation · Policy repository / GRC workspace
List of profiles representing common traffic patterns and/or events · Document repository
System protocols documentation · Document repository
List of acceptable thresholds for false positives and false negatives · Document repository

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

No profiles of common traffic and event patterns have been developed
Monitoring devices are not tuned using traffic and event profiles, producing excessive false positives

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-4(12) System Monitoring | Automated Organization-generated Alerts · SI-4(14) System Monitoring | Wireless Intrusion Detection