You’re probably wondering what is personally identifiable information, and whether the data your business holds counts. In short, it’s any information that can distinguish or trace a person’s identity, alone or combined with other data.
Getting this definition right is one building block of business data privacy, so treat this page as a starting point for the wider picture.
| Item | Value |
|---|---|
| Factors NIST lists for setting a PII confidentiality impact level | 6 factors |
| Basic actions NIST recommends for organizations that hold PII | 3 actions |
| Publication date of NIST SP 800-122 | April 2010 |
| Length of NIST SP 800-122 | 59 pages |
| Year of the OMB memo behind the basic PII definition | 2007 |
The figures come from NIST SP 800-122 and from NIST’s news item on the guide. Guidance gets revised, so check the sources before you rely on the figures.
What counts as personally identifiable information?
The NIST glossary defines PII as information that can be used to distinguish or trace an individual’s identity, either alone or when combined with other information that is linked or linkable to a specific individual. The glossary entry credits OMB Circular A-130 (2016) for this wording.
The idea goes back further. NIST’s news item describes a basic definition set by the Office of Management and Budget in a 2007 memo. It gives two examples: fingerprints, which are unique by themselves, and a date of birth, which can belong to many people but can be narrowed down to one person when it’s combined with other data (NIST news item).
So the useful test isn’t “does this field contain a name?” It’s “could this information be tied back to a specific person, on its own or alongside other records?”
That test matters because identifying PII comes first. NIST co-author Erika McCallister put it plainly in January 2009: “You can’t protect PII unless you can identify it.” The same announcement said thefts of PII, such as social security and credit card account numbers, were increasing dramatically, and that organizations often disagreed on what PII is (NIST news item).
Examples of PII: direct identifiers and linked information
NIST’s guide to protecting PII uses a longer definition drawn from a U.S. Government Accountability Office report. It covers any information about an individual maintained by an agency, and it splits that into identifying details and linked details (NIST glossary).
Information that can distinguish or trace an identity includes:
- name
- social security number
- date and place of birth
- mother’s maiden name
- biometric records
Other information that is linked or linkable to an individual includes:
- medical information
- educational information
- financial information
- employment information
The wording says “such as”, so these lists are examples rather than a complete catalogue. Your own records, from payroll files to customer accounts, may hold other items that pass the same test.
One caution on scope: when NIST announced the draft guide in January 2009, it said the publication is intended primarily for U.S. federal government agencies, but is meant to be useful to other organizations too (NIST news item).
Why not all PII is equal
The guide’s authors observe that “All PII is not created equal.” A telephone area code holds less specific information about an individual than a social security number, so you don’t need to protect every item the same way (NIST news item).
To tell the difference, NIST grades PII by its confidentiality impact level: low, moderate, or high. The level indicates the potential harm to the individuals and/or the organization if the PII were inappropriately accessed, used, or disclosed (NIST glossary).
SP 800-122 lists these factors for determining the level (NIST SP 800-122):
- Identifiability
- Quantity of PII
- Data field sensitivity
- Context of use
- Obligation to protect confidentiality
- Access to and location of PII
The guide works through three examples: an incident response roster, intranet activity tracking, and a fraud, waste, and abuse reporting application. Tracking staff activity, as in the second example, raises its own questions, which our guide to employee monitoring privacy laws covers.

How do you protect the PII you hold?
NIST’s news item recommends three basic actions for any organization that holds PII:
- Identify all the PII you maintain.
- Minimize the amount you collect to what is strictly necessary for your mission.
- Develop incident response plans for breaches of PII.
Beyond those basics, SP 800-122 groups its safeguards into three families (NIST SP 800-122):
- Operational safeguards: policy and procedure creation, plus awareness, training, and education.
- Privacy-specific safeguards: minimizing the use, collection, and retention of PII, conducting privacy impact assessments, de-identifying information, and anonymizing information.
- Security controls: the technical protections applied to systems that hold PII.
The impact level should shape how hard you apply them. NIST’s example is requiring appropriate training for everyone granted access to PII, with special emphasis on moderate- and high-impact PII. It also suggests restricting access to high-impact PII from mobile devices such as laptops and cellphones, because they are generally at greater risk of compromise than desktop computers at an organization’s headquarters (NIST news item).
Planning for a PII breach
SP 800-122 has a chapter on incident response for breaches involving PII. It follows these stages (NIST SP 800-122):
- Preparation
- Detection and analysis
- Containment, eradication, and recovery
- Post-incident activity
NIST says such plans would include determining when and how individuals should be notified, and whether to provide remedial services, such as credit monitoring, to affected individuals (NIST news item). Which notification duties apply to your business is a separate legal question, and our overview of data breach notification requirements is the place to start.
Frequently asked questions
Is a name on its own personally identifiable information?
Show answer
The definition in NIST SP 800-122 lists name as an example of information that can be used to distinguish or trace an individual’s identity. Whether a given name is enough in practice depends on context, which is why NIST also looks at identifiability.
Can information that isn’t unique still be PII?
Show answer
Yes. NIST’s example is a date of birth, which can belong to multiple people but can be narrowed down to one person in connection with other data.
Do medical, financial and employment records count?
Show answer
They count when they are linked or linkable to an individual. The definition names medical, educational, financial, and employment information as examples.
Does NIST’s PII guide apply to private businesses?
Show answer
As of NIST’s January 2009 announcement of the draft, the guide was intended primarily for U.S. federal government agencies, though NIST said it is meant to be useful to other organizations. Treat it as guidance you can borrow from, not as a statement of what the law requires of your company.



