Trustworthy AI Characteristics: Defining what trustworthy means for clinical AI

If you have been asked for evidence of trustworthy AI characteristics, the framework outcome behind the question is NIST AI RMF GOVERN 1.2. What follows is what it says, what satisfies it, and where organizations usually come up short.

What the framework says

The characteristics of trustworthy AI are integrated into organizational policies, processes, procedures, and practices.

That is the text of NIST AI RMF GOVERN 1.2. Read it closely: it describes an outcome to achieve, not a product to buy, which is why two practices of the same size can satisfy it in different ways and both be right.

What this looks like in practice

In an assessment, NIST AI RMF GOVERN 1.2 is not one question. It resolves into several, and each one is really asking for different evidence. These are among the questions asked about it:

• Has the organization embedded the characteristics of trustworthy AI, validity and reliability, safety, security and resilience, accountability and transparency, explainability and interpretability, privacy, and fairness with harmful bias managed, into its policies, processes and procedures?
• Does the organization have a policy requiring that its generative AI systems be evaluated for dangerous capabilities, such as CBRN uplift and offensive cyber capability, and for the robustness of their safety measures, both before deployment and on an ongoing basis?
• Does the organization have a digital content transparency policy that sets out how the origin and history of generative AI training data and generated content are documented?

Ownership usually sits with the AI governance lead, though the evidence is often produced by someone else, which is where the trail breaks. A control that works but has no owner tends to stop working the month the person who quietly maintained it changes roles.

Who this applies to

NIST AI RMF is voluntary rather than binding, and that changes how it should be used. Adopting it does not create a legal obligation, and declining it is not a violation. It earns its place when a customer contract names it, when it gives structure to AI governance work you already owe under a law or a contract, or when a recognized practice is worth having on record. Treat it as a way of organizing that work, not as a second regime.

Building it, in order

The sequence below is the order that produces evidence as a by-product rather than as a separate documentation exercise:

1. Adopt an AI policy that names each trustworthiness characteristic and what it means for the organization.
2. Map each characteristic to the processes and procedures that operationalize it (design review, testing, approval, monitoring).
3. Obtain executive approval of the policy and publish it to everyone who builds, buys or uses AI.
4. Write or update a policy that names the dangerous-capability categories to evaluate (at minimum CBRN and offensive cyber) and the systems in scope.
5. Require evaluation before deployment and at a defined cadence or on material change, using internal testing and, for higher-risk systems, external evaluators, for a vendor model, the policy may rely on the provider's published evaluations once they have been reviewed.
6. Assign an owner and define the approval step that consumes the evaluation results.

Where else this maps

The questions behind NIST AI RMF GOVERN 1.2 also map to NIST AI 600-1 2.1, 2.8, 2.9 and ISO/IEC 42001 5.2, A.2.2, which are voluntary guidance and standards rather than law; following them does not by itself establish compliance with any law. That matters for scoping: the same evidence can be written once and referenced from each, rather than rewritten per framework.

Evidence an assessor asks for

For this outcome the evidence type that satisfies it is a policy. The distinction matters more than it looks: a policy states what you intend to do, a procedure states how, and a record proves it happened on a date. Auditors ask for all three, and a practice that has written the first two often has nothing for the third.

Date every document and keep the superseded versions. The framework sets no retention period, so this is our recommendation rather than a requirement: keep each version for as long as the system it describes is in use and for a period after it is retired, because a question about a past decision is answered from the version that was in force when it was made.

Where this usually goes wrong

The usual gap is a control that exists in practice and nowhere in writing. Someone does the work, reliably, and it has never been written down, so the organization cannot demonstrate it and cannot notice when it stops. The fix is not more control, it is a dated record and a named owner.

What to do about it

• Produce the evidence, not the intention. For NIST AI RMF GOVERN 1.2 that means a signed, dated policy with a named owner and a review date. If the only evidence is that someone knows how this works, you have a practice and not a record.
• Put a name on it. Your AI governance lead should be recorded as the owner. Where the work is done by someone else, say so in the document: the split between who owns it and who performs it is where the trail usually breaks. A control with no owner stops working the month the person who quietly maintained it changes roles, and nobody notices.
• Set a review cadence and keep the evidence of each review. An annual date with a dated output is a common floor; what fails an assessment is a control implemented once and never re-checked against a changed environment.
• Do not treat this as a legal obligation. It is a voluntary framework. Adopt it where a customer contract or a regulator's guidance names it, or where it gives structure to AI governance work you owe for other reasons, and say in your own documentation which of those reasons applies.

If NIST AI RMF GOVERN 1.2 is new to you, the useful first step is not a policy template. It is writing down what you already do, dating it, and naming an owner. That turns an undocumented practice into evidence, and it usually reveals the real gap.

Related outcomes

• Legal and Regulatory Requirements for AI: Classifying an AI tool before deployment
• Risk Management Processes for AI: Sizing AI risk management to the use case
• Ongoing AI Monitoring: Monitoring a model after it goes live

References

• GOVERN 1.2, in NIST AI Risk Management Framework 1.0 (NIST AI 100-1). This is a voluntary framework, not a legal requirement. The quoted statement is NIST's own, from the Core tables of NIST AI 100-1.
• Crosswalk references in this post are the mappings in our question bank, and are not verified against the published text of those standards.
• This post describes what a framework outcome asks for and what evidence documents it. It is not legal advice, and your counsel owns the conclusion. State law may impose additional obligations of its own.