Identity Providers and Authorization Servers
LOW MODERATE HIGHRequirements NIST SOURCE
Employ identity providers and authorization servers to manage user, device, and non-person entity (NPE) identities, attributes, and access rights supporting authentication and authorization decisions in accordance with [policy] using [mechanisms].
Discussion (NIST Supplemental Guidance)
Identity providers, both internal and external to the organization, manage the user, device, and NPE authenticators and issue statements, often called identity assertions, attesting to identities of other systems or systems components. Authorization servers create and issue access tokens to identified and authenticated users and devices that can be used to gain access to system or information resources. For example, single sign-on (SSO) provides identity provider and authorization server functions. Authenticator management (to include credential management) is covered by IA-05.
Enhancements NIST SOURCE
IA-13(1) Protection of Cryptographic Keys LOW MODERATE HIGH
Cryptographic keys that protect access tokens are generated, managed, and protected from disclosure and misuse.
Discussion
Identity assertions and access tokens are typically digitally signed. The private keys used to sign these assertions and tokens are protected commensurate with the impact of the system and information resources that can be accessed.
IA-13(2) Verification of Identity Assertions and Access Tokens LOW MODERATE HIGH
The source and integrity of identity assertions and access tokens are verified before granting access to system and information resources.
Discussion
This includes verification of digital signatures protecting identity assertions and access tokens, as well as included metadata. Metadata includes information about the access request such as information unique to user, system or information resource being accessed, or the transaction itself such as time. Protected system and information resources could include connected networks, applications, and APIs.
IA-13(3) Token Management LOW MODERATE HIGH
In accordance with [policy], assertions and access tokens are:
- (a) generated;
- (b) issued;
- (c) refreshed;
- (d) revoked;
- (e) time-restricted; and
- (f) audience-restricted.
Discussion
An access token is a piece of data that represents the authorization granted to a user or NPE to access specific systems or information resources. Access tokens enable controlled access to services and resources. Properly managing the lifecycle of access tokens, including their issuance, validation, and revocation, is crucial to maintaining confidentiality of data and systems. Restricting token validity to a specific audience, e.g., an application or security domain, and restricting token validity lifetimes are important practices. Access tokens are revoked or invalidated if they are compromised, lost, or are no longer needed to mitigate the risks associated with stolen or misused tokens.
Implementation Guidance
Original engineering commentary written for this explorer — not NIST source text and not authoritative guidance.
No engineering interpretation has been authored for IA-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
No SP 800-53A assessment procedure is recorded for this item in the loaded catalog.
STIGs & CCIs
No STIG checks or CCI mappings are currently loaded for IA-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
No SP 800-53A assessment artifacts are available to derive a potential-evidence view from.