# IA-03 Device Identification and Authentication

NIST SP 800-53 control. Family: IA Identification and Authentication. Function: preventative. Baselines: moderate, high. Mapping licence: CC BY-SA 4.0.

Statement: Uniquely identify and authenticate [Assignment: organization-defined devices and/or types of devices] before establishing a [Selection (one or more): local; remote; network] connection.
Guidance: Devices that require unique device-to-device identification and authentication are defined by type, device, or a combination of type and device. Organization-defined device types include devices that are not owned by the organization. Systems use shared known information (e.g., Media Access Control [MAC], Transmission Control Protocol/Internet Protocol [TCP/IP] addresses) for device identification or organizational authentication solutions (e.g., Institute of Electrical and Electronics Engineers (IEEE) 802.1x and Extensible Authentication Protocol [EAP], RADIUS server with EAP-Transport Layer Security [TLS] authentication, Kerberos) to identify and authenticate devices on local and wide area networks. Organizations determine the required strength of authentication mechanisms based on the security categories of systems and mission or business requirements. Because of the challenges of implementing device authentication on a large scale, organizations can restrict the application of the control to a limited number/type of devices based on mission or business needs.

## Enhancements (3)
- IA-03(01) Cryptographic Bidirectional Authentication
- IA-03(03) Dynamic Address Allocation
- IA-03(04) Device Attestation
Withdrawn by NIST: IA-03(02) (now in IA-03(01)).
Each enhancement's statement: /api/v1/controls/IA-03?fields=enhancements

## Patterns that use it (6)
- Critical (2): SP-006 Wireless- Private Network Pattern; SP-020 Email Transport Layer Security (TLS) Pattern
- Important (4): SP-011 Cloud Computing Pattern; SP-017 Secure Network Zone Module; SP-023 Industrial Control Systems; SP-048 Offensive AI and Deepfake Defence (draft)

## Clauses by framework (49 frameworks)
- cobit_2019: DSS05
- nist_csf_2: PR.AA-01, PR.AA-03
- cis_controls_v8: CIS 13.9
- soc2_tsc: CC6.1, CC6.1-POF3, CC6.1-POF8
- iec_62443: 3-3 SR 1.2
- mas_trm: 9
- bsi_grundschutz: ORP.4
- anssi: Hygiene.5, Hygiene.26, SecNumCloud.10.5
- osfi_b13: B-13.3.2
- finma_circular: IV.B.d(59), IV.C(62)
- gdpr: Art.32(1)(b)
- dora: Art.9(4)(c)
- rbi_csf: Annex1.4, ITGRCA.19
- hkma_tme1: TME1.8.3, TME1.10.2
- mlps_2: 8.4
- cra: CRA.I.2d
- swift_cscf: SWIFT.2.1
- cbb_tm: TM-6
- cbuae: CR-4
- nca_ecc: 5-1
- qatar_nia: AC
- sama_csf: 3.1
- uae_ia: T9
- bog_cisd: CISD-IX
- bom_ctrm: 3.3
- cbe_csf: CTO-1
- cbn_csf: Part3.2
- sa_js2: JS2-7.1
- bot_cyber: Ch2.2
- cpmi_pfmi: PFMI.P22
- eba_ict: 3.4.2
- ffiec_is: II.C.15
- hipaa_sr: §164.312(d)
- iosco_cyber: PROT-1
- cmmc_2: IA
- nrc_73_54: RG5.71-A-AC
- ieee_1686: 5.5
- ferc_cip: Order 2222
- doe_c2m2: ACCESS
- api_1164: Sec 6
- iaea_nss: Sec 5.2
- common_criteria: CC Part 2 — FIA
- fda_21_cfr_11: §11.10(h)
- fda_cyber: SA-1
- csa_ccm_v4: DCS-08
- csa_aicm: DCS-08, IAM-18
- basel_sco60: SCO60.61
- bssc: KMS-04
- sec_custody_digital: SEC-CD-02
OSA's mapping for nist_csf_2 takes NIST's published crosswalk as its base. A clause not marked as OSA's own is in that crosswalk.

## More
- This control as JSON, with guidance and ATT&CK techniques: /api/v1/controls/IA-03
- Clauses only: /api/v1/controls/IA-03?fields=mappings
- Page for people: /controls/ia-03/