# NIST SP 800-53 Rev. 5 AC-9(4) — Additional Logon Information - Source: https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ac-9-4-additional-logon-information - Section: [Compliance](https://support.icompaas.com/compliance) › [NIST SP 800-53 Rev. 5 Controls](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5) › AC — Access Control - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **NIST SP 800-53 Rev. 5**·Control `AC-9(4)`·medium·Component: **Access Control** ## What this control requires > Notify users upon successful logon of organization-defined additional information, such as the location (e.g., IP address) or device identifier of the last logon, to enhance security awareness. This control supports the Authentication System capability within the Access Control family. > > — NIST SP 800-53 Rev. 5, Control AC-9(4) ### In plain English Notify users upon successful logon of organization-defined additional information, such as the location (e.g., IP address) or device identifier of the last logon, to enhance security awareness. In practice, this means you can prove you access management-level controls on a defined cadence. ## Why it matters SP 800-53 is the catalogue every U.S. federal authorisation (FedRAMP, FISMA, CMMC) and most regulated industries point at. A missing control surfaces as a Plan of Action & Milestones (POA&M) item that an Authorizing Official must approve before the Authority To Operate is granted or renewed. ## What an auditor looks for A 3PAO (FedRAMP) or Independent Assessor (NIST RMF) tests against NIST SP 800-53A assessment procedures. For each control they expect a documented implementation that addresses every assessment objective (Examine, Interview, Test) and an implementation summary in the System Security Plan. Within **Access Control**, the assessor will trace your implementation back to the catalogue reference (Control AC-9(4)) and look for objective evidence on the latest two assessment cycles. ## How to implement #### Endpoint Protection **MDM.** Make MDM enrollment a hard gate for device access (Intune compliance + Conditional Access, or Jamf + Okta device trust). Unmanaged devices simply don't get a session token. **EDR.** Deploy CrowdStrike / SentinelOne / Defender for Endpoint to every server and laptop; alert on any host that stops sending telemetry for >24h. ### Operational checklist - **Access.** Document the trigger, the owner and the cadence. - **Information.** Document the trigger, the owner and the cadence. - **Security.** Document the trigger, the owner and the cadence. - **Review.** Document the trigger, the owner and the cadence. - **Successful.** Document the trigger, the owner and the cadence. - **Scope:** management, access control, information, authentication, organization, system, logon information, location. ## 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: Additional Logon Information. ## Common pitfalls - Pilot MDM rollouts that quietly exclude executives or engineers; carving out the highest-risk users is the most common audit failure. ## 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-171 Rev. 3 3.1.8** — Unsuccessful Logon Attempts](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-1-8-unsuccessful-logon-attempts) - [**CIS Controls v8 6.7** — Centralize Access Control](https://support.icompaas.com/compliance/cis-controls-v8/6-7-centralize-access-control) - [**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) - [**BSI C5:2020 IDM-08** — Confidentiality of authentication information](https://support.icompaas.com/compliance/bsi-c5-2020/idm-08-confidentiality-of-authentication-information) - [**SOC 2 (2017 TSC) CC6.4** — Physical Access Controls](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/cc6-4-physical-access-controls) ## Related controls in NIST SP 800-53 Rev. 5 - [**Control AC-11** — Device Lock](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ac-11-device-lock) - [**Control AC-14** — Permitted Actions Without Identification Or Authentication](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ac-14-permitted-actions-without-identification-or-authentication) - [**Control AC-10** — Concurrent Session Control](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ac-10-concurrent-session-control) - [**Control AC-9** — Previous Logon Notification](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ac-9-previous-logon-notification) - [**Control AC-9(1)** — Unsuccessful Logons](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ac-9-1-unsuccessful-logons) - [**Control AC-12(1)** — User-Initiated Logouts](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ac-12-1-user-initiated-logouts) ## References - [NIST Computer Security Resource Center — NIST SP 800-53 Rev. 5](https://csrc.nist.gov/Projects/risk-management/sp800-53-controls) - Catalogue identifier: `Control AC-9(4)` Topics: identity accessawareness trainingidentity managementaccess reviewprivileged accessendpoint protection ## Related compliance guidance - [NIST SP 800-53 Rev. 5: a practical implementation guide for cloud teams](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5): Start with the full NIST SP 800-53 implementation guide — scope, roadmap, evidence and how the assessment runs. - [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): If your obligation is protecting CUI in your own systems for a federal or defence contract, this derived subset — not the full catalogue — is the requirement. - [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Most commercial SaaS already hold a SOC 2 Type 2, and FedRAMP 20x Class A is designed for providers that have one.