What it means
Privacy asks whether personal information should have been collected, who may use it, how long it may be kept, and what the person can expect. Confidentiality asks a narrower question: who is allowed to read a record that already exists. A file can pass that test and still be used for a purpose the person was never offered.
Security work protects confidentiality, integrity, availability, and the ability to recover. Privacy work asks whether the processing itself fits. NIST SP 800-53 Revision 5 is a catalog of security and privacy controls, useful as shared vocabulary. The catalog does not decide that a statute applies, and this guide does not ask you to implement every control. Sector rules stay in separate explainers. Nothing here is legal advice or a compliance determination.
The idea at a glance / Data
An access check does not approve a new purpose.
Keep a successful staffing read separate from an unfinished decision to reuse the same personal data.
Fictional Chronos Hub HR keeps R101 for staffing: driver D101’s home address and clearance flag. Kael Cho has the configured staffing role; an outside reader does not. Sloane Sterling receives P101 asking to reuse the roster for neighborhood flyers. All people, records and values are synthetic.
READ THE PICTURE
Compare access and purpose
Kael can read R101 for staffing while an outside reader is refused. Those results do not approve a flyer use. Sloane holds P101; no vendor copy is created.
Keep in mindThe access checks cover R101 only. They do not establish a complete privacy program, encryption, lawful collection, consent, an allowed new purpose or a retention limit. Sloane’s new-use and legal review remain open; no vendor copy or compliance conclusion is shown.
Read the complete example
- Compare access and purpose. Kael can read R101 for staffing while an outside reader is refused. Those results do not approve a flyer use. Sloane holds P101; no vendor copy is created. The local fixture returns HTTP 200 with a copy of the unchanged synthetic row to Kael and a bodyless 403 to the unassigned reader. R101 stays retained. Separately, P101 proposes neighborhood flyers, a purpose outside the stated staffing use. Sloane Sterling holds that request pending privacy/legal review; technical read permission does not supply the missing purpose decision. No new-use authorization or vendor delivery occurs. Retention is not configured. These selected request results demonstrate one access boundary, not protection against every possible disclosure. The source and purpose record remain separate, and the exercise reaches no conclusion about applicable law or actual harm.
The access checks cover R101 only. They do not establish a complete privacy program, encryption, lawful collection, consent, an allowed new purpose or a retention limit. Sloane’s new-use and legal review remain open; no vendor copy or compliance conclusion is shown.
Diagram references: NIST Privacy Framework 1.0: processing risk and minimized logs · NIST SP 800-53 Rev. 5: processing purposes and security attributes
AN ILLUSTRATIVE SCENARIO
A staffing read and a held new-use request
In fictional Meridian HR, Vera’s configured staffing read returns R101 while an unassigned reader receives 403. Sloane then receives P101 asking to reuse the same home-address and clearance roster for recruiting flyers. She holds that proposal pending privacy/legal review, and no vendor copy is created. The original remains; the access check has not supplied a new-purpose decision or retention limit.
Put it to work
- Write the purpose that justified collection, the people covered, and the fields that purpose needs. Keep that sentence separate from the control that stops strangers reading the file.
- Limit access to roles that serve the purpose, and keep an audit trail of exports without copying extra sensitive fields into every log line.
- When a long security retention clock and a shorter purpose limit disagree, write the conflict and ask counsel or the privacy officer. Do not close it with a framework map.
How to check your work
For one synthetic export, name one control that serves both security and privacy, one place those goals conflict, and the counsel or privacy officer you would ask. If the note says the file is compliant, rewrite that line as an open question.
Connect the ideas
- Confidentiality
The property that information is available only to people or systems authorized to see it.
- Encryption
Transforming data so only holders of the appropriate key can read it, protecting confidentiality in transit or at rest.
- Audit trail
An append-oriented history of security-relevant actions that can be shown to a later reviewer.
- Data minimization
Collecting, using, and keeping only the personal information a stated purpose needs, and no longer than that purpose requires.