NIST SP 800-53 Rev. 5·Control IA-6·medium·Component: Identification and Authentication

What this control requires

Obscuring feedback of authentication information during the authentication process to protect it from exploitation by unauthorized individuals. This includes displaying asterisks for passwords or limiting feedback visibility to prevent shoulder surfing, particularly on systems like desktops with large monitors, while balancing usability on small-display devices. This control supports the Authentication Interface capability within the Identification and Authentication family.
— NIST SP 800-53 Rev. 5, Control IA-6

In plain English

Obscuring feedback of authentication information during the authentication process to protect it from exploitation by unauthorized individuals. In practice, this means you can prove you policy 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 Identification and Authentication, the assessor will trace your implementation back to the catalogue reference (Control IA-6) 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.

Policy Management

Docs. Keep each policy in version-controlled Markdown alongside the code that implements it; ship a signed PDF snapshot at each annual review and link the SHA into the SoA.

Operational checklist

  • Policy. Document the trigger, the owner and the cadence.
  • Information. Document the trigger, the owner and the cadence.
  • Process. Document the trigger, the owner and the cadence.
  • Security. Document the trigger, the owner and the cadence.
  • Protection. Document the trigger, the owner and the cadence.
  • Scope: management, information, authentication information, feedback, protection, identity, capability, systems.

Evidence to collect

  • User Device Scan. MDM compliance state per user device (Intune / Jamf / Workspace ONE).
  • Policy Document. A signed and version-controlled policy / standard / procedure document.

Endpoint compliance telemetry (Intune, Jamf) proves managed coverage. Signed policy or standard documents the safeguard. Focus: Authentication Feedback.

Common pitfalls

  • Pilot MDM rollouts that quietly exclude executives or engineers; carving out the highest-risk users is the most common audit failure.
  • Policies that no engineer has read; the version in Confluence drifts from the version that's actually being enforced.

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.

Related controls in NIST SP 800-53 Rev. 5

References

Topics: governance riskendpoint securityendpoint protectionidentity managementpolicy management