# NIST SP 800-171 Rev. 3 3.3.1 — Event Logging - Source: https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-3-1-event-logging - Section: [Compliance](https://support.icompaas.com/compliance) › [NIST SP 800-171 Rev. 3 Requirements](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3) › Audit and Accountability — §3.3 - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **NIST SP 800-171 Rev. 3**·Requirement `3.3.1`·high·Component: **Audit and Accountability** ## What this control requires > This control specifies the types of events to be logged within the system, ensuring that all security-relevant events, such as password changes, failed logins, and privileged function execution, are captured. It also requires regular reviews and updates of the event types selected for logging to ensure that they remain relevant to the system's security requirements. This control supports the Event Logging Configuration capability within the Audit and Accountability (3.3) family. > > — NIST SP 800-171 Rev. 3, Requirement 3.3.1 ### In plain English This control specifies the types of events to be logged within the system, ensuring that all security-relevant events, such as password changes, failed logins, and privileged function execution, are captured. In practice, this means you can prove you access management-level controls on a defined cadence. ## Why it matters DoD contractors and their subcontractors must implement all 100 SP 800-171 requirements to keep CUI handling contracts. Gaps are scored against the SPRS scoring methodology; below a 110-point starting score, each unmet requirement deducts points and a below-threshold score can disqualify a bid. This control is rated **high**. Auditors expect a named owner, a remediation SLA, and a tooling artefact that evidences continuous operation. ## What an auditor looks for A C3PAO conducting a CMMC Level 2 assessment uses NIST SP 800-171A objectives. They expect a System Security Plan (SSP), Plan of Action & Milestones (POA&M) for any gaps, and objective evidence (configurations, ticket records, training records) for every requirement. Within **Audit and Accountability**, the assessor will trace your implementation back to the catalogue reference (Requirement 3.3.1) and look for objective evidence on the latest two assessment cycles. ## How to implement #### Logging Monitoring **AWS.** Org-trail CloudTrail to a central log archive account, GuardDuty in every region, and Security Hub for cross-source correlation. **Azure.** Pipe every diagnostic setting into a central Log Analytics workspace; onboard Microsoft Sentinel for SIEM/SOAR. **GCP.** Aggregate audit logs in a dedicated logging project with sink to BigQuery; enable Security Command Center Premium and route findings to Chronicle SIEM. ### Operational checklist - **Access.** Document the trigger, the owner and the cadence. - **Event.** Document the trigger, the owner and the cadence. - **Configuration.** Document the trigger, the owner and the cadence. - **System.** Document the trigger, the owner and the cadence. - **Password.** Document the trigger, the owner and the cadence. - **Scope:** management, configuration, password changes, security. ## Evidence to collect - **Identity Scan.** IAM / IdP exports — Entra ID, Okta, IAM Identity Center, Workspace directory — showing accounts, roles, MFA state and last sign-in. Identity analytics (Okta, SailPoint, Access Analyzer) demonstrates least-privilege. Focus: Event Logging. ## Common pitfalls - Per-account logging that nobody stitches together at the org level — incidents that cross accounts go undetected for days. ## How it maps to other frameworks Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit. - [**NIST SP 800-53 Rev. 5 AU-10(2)** — Validate Binding Of Information Producer Identity](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/au-10-2-validate-binding-of-information-producer-identity) - [**ISO/IEC 27001:2022 A.5.2** — Information security roles and responsibilities](https://support.icompaas.com/compliance/iso-27001-2022/a-5-2-information-security-roles-and-responsibilities) - [**SOC 2 (2017 TSC) CC6.2** — Access Provisioning](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/cc6-2-access-provisioning) - [**BSI C5:2020 OIS-04** — Segregation of Duties](https://support.icompaas.com/compliance/bsi-c5-2020/ois-04-segregation-of-duties) - [**CIS Controls v8 14.9** — Conduct Role-Specific Security Awareness and Skills Training](https://support.icompaas.com/compliance/cis-controls-v8/14-9-conduct-role-specific-security-awareness-and-skills-training) ## Related controls in NIST SP 800-171 Rev. 3 - [**Requirement 3.13.14** — Technology-specific.](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-13-14-technology-specific) - [**Requirement 3.1.7** — Least Privilege - Privileged Functions](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-1-7-least-privilege-privileged-functions) - [**Requirement 3.3.8** — Protection of Audit Information](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-3-8-protection-of-audit-information) - [**Requirement 3.9.1** — Personnel Screening](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-9-1-personnel-screening) - [**Requirement 3.1.6** — Least Privilege - Privileged Accounts](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-1-6-least-privilege-privileged-accounts) - [**Requirement 3.1.8** — Unsuccessful Logon Attempts](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-1-8-unsuccessful-logon-attempts) ## References - [NIST Computer Security Resource Center — NIST SP 800-171 Rev. 3](https://csrc.nist.gov/pubs/sp/800/171/r3/final) - Catalogue identifier: `Requirement 3.3.1` Topics: identity accesslogging monitoringprivileged accessidentity managementaccess review ## Related compliance guidance - [NIST SP 800-171 and CMMC: a practical guide to protecting CUI in the cloud](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3): Start with the full NIST SP 800-171 implementation guide — scope, roadmap, evidence and how the assessment runs. - [NIST SP 800-53 Rev. 5: a practical implementation guide for cloud teams](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5): The catalogue 800-171 is tailored from, and the basis of the FedRAMP Moderate baseline your cloud providers must meet for CUI. - [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): If commercial customers ask for a certificate as well, most 800-171 controls can be evidenced once and mapped to Annex A.