← All posts

Privacy Risk Assessment: Assessing privacy risk distinctly from security risk

August 19, 2026 · Ken Armstrong

NIST Privacy Framework ID.RA-P3 covers privacy risk assessment. In most assessments the control itself is present and the record proving it is not, which is why this outcome produces findings at organizations that are, in practice, doing the work.

What the framework says

NIST Privacy Framework ID.RA-P3 sets the expectation for privacy risk assessment. The framework describes the outcome rather than prescribing a technology, so the question is whether your implementation achieves it and whether you can show that it does.

What this looks like in practice

On the ground, NIST Privacy Framework ID.RA-P3 is not one check. It resolves into several questions, and each one is really asking for different evidence:

Has the organization assessed whether its de-identification practices adequately address the elevated re-identification risk of genetic information?
Does the organization conduct periodic privacy risk assessments to identify and prioritize risks arising from its processing of personal information?
Does the organization evaluate privacy risks arising from AI systems that process personal or other sensitive data?

Ownership usually sits with the compliance owner, 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 Privacy Framework 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 a program HIPAA describes only in outcomes, or when a recognized practice is worth having on record. Treat it as a way of organizing work you already owe, if HIPAA applies to you, 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:

Engage a qualified expert to assess whether genetic information shared for secondary purposes meets the applicable de-identification standard.
Account for the risk that genomic sequences and familial patterns may remain re-identifiable after standard identifier removal.
Apply additional controls or constraints where standard de-identification is insufficient.
Document each determination.
Conduct a periodic privacy risk assessment evaluating how personal information is collected, used, disclosed, retained, and shared.

Where this meets HIPAA

For a healthcare organization the practical reason to care is the overlap with HIPAA. In our reading this outcome covers some of the same ground as 45 CFR 164.514(a), 45 CFR 164.514(b), and 45 CFR 164.530(c). That is an editorial mapping, not an official NIST or HHS crosswalk, so read the HIPAA provision itself before relying on it; where the overlap holds, the evidence you produce can be cited against both so long as it is written once and kept in one place.

Evidence an assessor asks for

For this outcome the evidence types that satisfy it are risk assessment. 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. No federal rule sets a retention period for a voluntary framework document, so this is our recommendation rather than a requirement: keep six years, because that is what HIPAA requires of the documentation this work usually overlaps with (45 CFR 164.316(b)(2)(i) for security documentation, 164.530(j)(2) for privacy), and holding two sets of dates is how the earlier one goes missing.

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 Privacy Framework ID.RA-P3 that means a completed assessment showing the method, the findings and the 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 privacy official 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 names it or where it gives structure to something HIPAA describes only as an outcome, and say in your own documentation which of those reasons applies.

If NIST Privacy Framework ID.RA-P3 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

References

ID.RA-P3, in NIST Privacy Framework 1.0. This is a voluntary framework, not a legal requirement.
The HIPAA provisions this post names are an editorial reading of where the work overlaps, not an official NIST or HHS crosswalk.
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.