What is the most common gap auditors find on MP-3.5?

Oversight designed at a volume the reviewer cannot sustain

`MP-3.5` Processes for human oversight are defined, assessed, and documented in accordance with organizational…

Q: What evidence do auditors commonly ask for on MP-3.5 Processes for human oversight are defined, assessed, and documented in accordance with organizational…?

The documented human oversight process for the system; Assessment of whether oversight is exercisable at the pace and volume of operation; The link to the governing organisational policy on oversight; The authority the overseer holds, including whether they can stop the system.

Processes for human oversight are defined, assessed, and documented in accordance with organizational policies from GOVERN function. Oversight is designed for the specific configuration, assessed for whether it is exercisable in practice, and consistent with the governing policy rather than invented per project.

Source: NIST AI RMF 1.0, MP-3.5. 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 AI RMF 1.0 in the compliance library.

artefacts

held by a system

at each review

hard

to go live

Document repository

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

none for this control

periodic reviewEvidence produced at each review

Assessment of whether oversight is exercisable at the pace and volume of operation · Document repository

governing documentDocuments that govern the control

The documented human oversight process for the system · Document repository
The link to the governing organisational policy on oversight · Policy repository / GRC workspace
The authority the overseer holds, including whether they can stop the system · Document repository

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

Common gaps auditors find

Oversight designed at a volume the reviewer cannot sustain
Overseer able to observe but not to intervene
Process differs from the governing policy with no recorded deviation

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

MP-3.4 Processes for operator and practitioner proficiency with AI system performance and trustworthiness, and… · MP-4.1 Approaches for mapping AI technology and legal risks of its components, including the use of third-party data…