# NIST SP 800-53 Rev. 5 IA-8(3) — Use Of Ficam-Approved Products - Source: https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ia-8-3-use-of-ficam-approved-products - 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) › IA — Identification and Authentication - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **NIST SP 800-53 Rev. 5**·Control `IA-8(3)`·medium·Component: **Identification and Authentication** ## What this control requires > Employing only Federal Identity, Credential, and Access Management (FICAM)-approved information system components in organization-defined systems to accept third-party credentials. This applies to public-facing systems, ensuring components meet FICAM's technical, security, privacy, and organizational maturity requirements for trusted authentication. This control supports the FICAM-Approved Authentication Solution capability within the Identification and Authentication family. > > — NIST SP 800-53 Rev. 5, Control IA-8(3) ### In plain English Employing only Federal Identity, Credential, and Access Management (FICAM)-approved information system components in organization-defined systems to accept third-party credentials. 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 **Identification and Authentication**, the assessor will trace your implementation back to the catalogue reference (Control IA-8(3)) and look for objective evidence on the latest two assessment cycles. ## How to implement 1. Write a short policy stating intent, scope and named owner. 2. Encode it as a platform guardrail — SCP, Azure Policy initiative, Organisation Policy, or repository policy. 3. Wire a monitoring signal that catches drift (CSPM rule, SIEM rule, scheduled query, Workspace alert) and ticket it. 4. Review on a documented cadence and capture the review in the risk register or compliance tracker. ### 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. - **Authentication.** Document the trigger, the owner and the cadence. - **Scope:** management, information, privacy, authentication, organization, system, only, identity. ## 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. - **Vendor Risk Management.** `vendor_risk_management` evidence Identity analytics (Okta, SailPoint, Access Analyzer) demonstrates least-privilege. Third-party risk management evidence (assessments, contracts, due diligence) shows supplier oversight. Focus: Use Of Ficam-Approved Products. ## 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. - [**CIS Controls v8 6.6** — Establish and Maintain an Inventory of Authentication and Authorization Systems](https://support.icompaas.com/compliance/cis-controls-v8/6-6-establish-and-maintain-an-inventory-of-authentication-and-authorization-systems) - [**ISO/IEC 27001:2022 A.5.15** — Access control](https://support.icompaas.com/compliance/iso-27001-2022/a-5-15-access-control) - [**NIST SP 800-171 Rev. 3 3.15.2** — System Security Plan](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-15-2-system-security-plan) ## Related controls in NIST SP 800-53 Rev. 5 - [**Control IA-8(2)** — Acceptance Of External Authenticators](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ia-8-2-acceptance-of-external-authenticators) - [**Control IA-5(6)** — Protection Of Authenticators](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ia-5-6-protection-of-authenticators) - [**Control IA-5(12)** — Biometric Authentication Performance](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ia-5-12-biometric-authentication-performance) - [**Control IA-5(13)** — Expiration Of Cached Authenticators](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ia-5-13-expiration-of-cached-authenticators) - [**Control IA-4(1)** — Prohibit Account Identifiers As Public Identifiers](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ia-4-1-prohibit-account-identifiers-as-public-identifiers) - [**Control IA-8** — Identification And Authentication (Non-Organizational Users)](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ia-8-identification-and-authentication-non-organizational-users) ## 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 IA-8(3)` Topics: identity accessvendor riskidentity managementvendor managementaccess reviewprivileged access ## 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.