{"data":{"id":"IA-03","name":"Device Identification and Authentication","family":"IA","family_name":"Identification and Authentication","withdrawn":false,"description":"Uniquely identify and authenticate [Assignment: organization-defined devices and/or types of devices] before establishing a [Selection (one or more): local; remote; network] connection.","supplemental_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":[{"id":"IA-03(01)","name":"Cryptographic Bidirectional Authentication","statement":"Authenticate [Assignment: organization-defined devices and/or types of devices] before establishing [Selection (one or more): local; remote; network] connection using bidirectional authentication that is cryptographically based.","baselines":[]},{"id":"IA-03(02)","name":"Cryptographic Bidirectional Network Authentication","withdrawn":true,"incorporated_into":["IA-03(01)"]},{"id":"IA-03(03)","name":"Dynamic Address Allocation","statement":"a. Where addresses are allocated dynamically, standardize dynamic address allocation lease information and the lease duration assigned to devices in accordance with [Assignment: organization-defined lease information and lease duration]; and\nb. Audit lease information when assigned to a device.","baselines":[]},{"id":"IA-03(04)","name":"Device Attestation","statement":"Handle device identification and authentication based on attestation by [Assignment: organization-defined configuration management process].","baselines":[]}],"baseline_low":false,"baseline_moderate":true,"baseline_high":true,"nist_800_53":{"rev5":{"id":"IA-03","name":"Device Identification and Authentication","description":"Uniquely identify and authenticate [Assignment: organization-defined devices and/or types of devices] before establishing a [Selection (one or more): local; remote; network] connection.","discussion":"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.","related_controls":["AC-17","AC-18","AC-19","AU-06","CA-03","CA-09","IA-04","IA-05","IA-09","IA-11","IA-13","SI-04"],"baseline_low":false,"baseline_moderate":true,"baseline_high":true,"baseline_privacy":false,"new_in_rev5":false,"changes_from_rev4":""}},"compliance_mappings":{"iso_27001_2022":[],"iso_27002_2022":[],"cobit_2019":["DSS05"],"pci_dss_v4":[],"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"],"finos_ccc":[],"iso_42001_2023":[],"iec_62443":["3-3 SR 1.2"],"asd_e8":[],"nis2":[],"apra_cps_234":[],"mas_trm":["9"],"pra_op_resilience":[],"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)"],"bio2":[],"rbi_csf":["Annex1.4","ITGRCA.19"],"fisc":[],"lgpd_bcb":[],"hkma_tme1":["TME1.8.3","TME1.10.2"],"mlps_2":["8.4"],"dnb_good_practice":[],"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"],"nerc_cip":[],"nrc_73_54":["RG5.71-A-AC"],"tsa_psd":[],"ieee_1686":["5.5"],"ferc_cip":["Order 2222"],"doe_c2m2":["ACCESS"],"api_1164":["Sec 6"],"awia":[],"iaea_nss":["Sec 5.2"],"pci_pts":[],"fips_140":[],"cbest":[],"tiber_eu":[],"pci_hsm":[],"common_criteria":["CC Part 2 — FIA"],"isae_3402":[],"fca_sysc_13":[],"fda_21_cfr_11":["§11.10(h)"],"fda_cyber":["SA-1"],"hitrust_csf":[],"iso_27799":[],"lloyds_ms":[],"naic_ds":[],"nhs_dspt":[],"pra_ss1_23":[],"solvency_ii":[],"owasp_masvs_v2":[],"csa_ccm_v4":["DCS-08"],"csa_aicm":["DCS-08","IAM-18"],"ccss_v9":[],"mica":[],"basel_sco60":["SCO60.61"],"bssc":["KMS-04"],"sec_custody_digital":["SEC-CD-02"],"dpdpa":[]},"attack_techniques":[{"id":"T1530","name":"Data from Cloud Storage","tactics":["collection"],"mapping_type":"mitigates","mapping_rationale":"Device identification and authentication ensures that only authorised and verified devices can access cloud storage resources, preventing adversaries using unregistered or rogue devices from retrieving sensitive data stored in cloud environments."},{"id":"T1537","name":"Transfer Data to Cloud Account","tactics":["exfiltration"],"mapping_type":"mitigates","mapping_rationale":"Requiring device authentication before granting cloud connectivity prevents adversaries from transferring data to external cloud accounts from unidentified devices, as only organisationally registered endpoints can establish the necessary sessions."},{"id":"T1552","name":"Unsecured Credentials","tactics":["credential-access"],"mapping_type":"mitigates","mapping_rationale":"Device-level authentication prevents unregistered systems from accessing credential stores and configuration repositories, limiting adversary ability to harvest unsecured credentials from devices that have not been authenticated to the network."},{"id":"T1602","name":"Data from Configuration Repository","tactics":["collection"],"mapping_type":"mitigates","mapping_rationale":"Authenticating devices before allowing network access ensures that only verified infrastructure components can query configuration repositories, preventing adversaries on rogue devices from dumping network device configurations via management protocols."},{"id":"T1621","name":"Multi-Factor Authentication Request Generation","tactics":["credential-access"],"mapping_type":"mitigates","mapping_rationale":"Device identification and authentication provides an additional verification layer that complements MFA, making it harder for adversaries to generate fraudulent MFA push notifications from unrecognised devices even if they possess valid user credentials."},{"id":"T1552.005","name":"Cloud Instance Metadata API","tactics":["credential-access"],"mapping_type":"mitigates","mapping_rationale":"Device authentication controls restrict access to cloud instance metadata APIs to authenticated and authorised compute instances, preventing adversaries on rogue or compromised external devices from querying metadata endpoints for temporary credentials."},{"id":"T1602.001","name":"SNMP (MIB Dump)","tactics":["collection"],"mapping_type":"mitigates","mapping_rationale":"Device identification requirements ensure that only authenticated network management stations can issue SNMP queries, preventing adversaries on unregistered devices from performing MIB dumps to collect sensitive configuration data."},{"id":"T1602.002","name":"Network Device Configuration Dump","tactics":["collection"],"mapping_type":"mitigates","mapping_rationale":"Requiring device authentication before granting management plane access prevents unidentified systems from executing configuration dumps on network devices, blocking adversary collection of routing tables, ACLs, and credential material."}],"metadata":{"last_reviewed":"2026-10-03","review_notes":"2026-10-03: nist_csf_2 PR.AA-01 added from NIST's CSF 2.0 to SP 800-53 Rev 5.2.0 crosswalk (OLIR entry 186), which OSA's mapping now takes as its base. 2026-10-03: baselines LMH to -MH, from NIST SP 800-53B Release 5.2.0.","mapping_status":"complete"},"function":"preventative","used_by_patterns":["SP-006","SP-011","SP-017","SP-020","SP-023","SP-048"]}}