What evidence do auditors commonly ask for on IA-3(4) Device Identification and Authentication | Device Attestation?

Identification and authentication policy; System security plan; Procedures addressing device identification and authentication; Procedures addressing device configuration management; System design documentation; System configuration settings and associated documentation.

What is the most common gap auditors find on IA-3(4)?

Device identification and authentication do not rely on attestation by the configuration management process

NIST SP 800-53 Rev 5 · IA - Identification and Authentication

`IA-3(4)` Device Identification and Authentication | Device Attestation

Handle device identification and authentication based on attestation by organization-defined configuration management process.

Source: NIST SP 800-53 Rev 5, IA-3(4). The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open NIST SP 800-53 Rev 5 in the compliance library.

Base controls and their enhancements. Which apply follows the baseline you are assessed against (for example FedRAMP Moderate or High, or the low, moderate and high baselines of SP 800-53B). Text in square brackets is a parameter your organisation sets.

artefacts

held by a system

at each review

moderate

to go live

Endpoint management (MDM / EDR)

where the evidence lives

teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

Procedures addressing device configuration management · Endpoint management (MDM / EDR)
Configuration management records · Identity provider / directory
Change control records · Identity provider / directory
Test of Mechanisms supporting and/or implementing device identification and authentication capabilities; mechanisms supporting and/or implementing configuration management; cryptographic mechanisms supporting device attestation · Endpoint management (MDM / EDR)

periodic reviewEvidence produced at each review

System audit records · Identity provider / directory

governing documentDocuments that govern the control

Identification and authentication policy · Policy repository / GRC workspace
System security plan · Policy repository / GRC workspace
Procedures addressing device identification and authentication · Policy repository / GRC workspace
System design documentation · Policy repository / GRC workspace
System configuration settings and associated documentation · Policy repository / GRC workspace

First move

Start with the 4 of 10 artefacts that already live in a system (Endpoint management (MDM / EDR)); keep the periodic reviews but log each one as a dated record with a named reviewer.

Common gaps auditors find

Device identification and authentication do not rely on attestation by the configuration management process
The configuration management process providing device attestation was never defined

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

IA-3(3) Device Identification and Authentication | Dynamic Address Allocation · IA-4 Identifier Management