← SI-4

Analyze Traffic and Event Patterns

LOW MODERATE HIGH
1 Overlay 0 Related Controls
Graph
Export ▾

Requirements NIST SOURCE

Discussion (NIST Supplemental Guidance)

Identifying and understanding common communications traffic and event patterns help organizations provide useful information to system monitoring devices to more effectively identify suspicious or anomalous traffic and events when they occur. Such information can help reduce the number of false positives and false negatives during system monitoring.

Implementation Guidance

Engineering Interpretation

Original engineering commentary written for this explorer — not NIST source text and not authoritative guidance.

No engineering interpretation has been authored for SI-4(13) yet. This section is architected to receive it — see the Requirements and Assessment sections above for the authoritative NIST source content in the meantime.

Assessment

NIST SP 800-53A REV 5.2.0

Assessment Objectives

  1. communications traffic for the system is analyzed;
  2. event patterns for the system are analyzed;
  3. profiles representing common traffic are developed;
  4. profiles representing event patterns are developed;
  5. traffic profiles are used in tuning system-monitoring devices;
  6. event profiles are used in tuning system-monitoring devices.

Examine

[SELECT FROM: 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; list of profiles representing common traffic patterns and/or events; system protocols documentation; list of acceptable thresholds for false positives and false negatives; system security plan; other relevant documents or records].

Interview

[SELECT FROM: System/network administrators; organizational personnel with information security responsibilities; organizational personnel installing, configuring, and/or maintaining the system; organizational personnel responsible for monitoring the system; organizational personnel responsible for the intrusion detection system].

Test

[SELECT FROM: 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].

Overlays

Showing the OT/ICS overlay for the parent control SI-4 — see the SI-4(13) entries within each baseline below.

OT/ICS Overlay SP 800-82r3

NIST SP 800-82r3 Appendix F, Table 22. Blank baseline means the control/control enhancement is not selected in that initial OT baseline.

LOW

  • Base control: Included (matches standard baseline)

MODERATE

  • Base control: Included (matches standard baseline)
  • Included: (2) (4) (5)

HIGH

  • Base control: Included (matches standard baseline)
  • Included: (2) (4) (5) (10) (12) (14) (20) (22)

STIGs & CCIs

No STIG checks or CCI mappings are currently loaded for SI-4(13). This section is architected to display, per product: STIG ID, Finding ID, Severity, Title, Description, Check, Fix, CCI, and NIST control mapping — but nothing is populated here until a real DISA STIG/CCI dataset is ingested.

Learn more about STIG/CCI integration →

Evidence

Potential Evidence — Derived

Categorized from the SP 800-53A "Examine"/"Test" artifact list above by keyword — not an authoritative NIST evidence list.

Policy

  • System and information integrity policy
  • system security plan

Configuration

  • system design documentation
  • system configuration settings and associated documentation

Testing

  • 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

Other Records

  • system and information integrity procedures
  • procedures addressing system monitoring tools and techniques
  • system monitoring tools and techniques documentation
  • list of profiles representing common traffic patterns and/or events
  • system protocols documentation
  • list of acceptable thresholds for false positives and false negatives
  • other relevant documents or records