PII, personally identifiable information, is any information that can identify a person. PHI, protected health information, is individually identifiable health information held by a HIPAA covered entity or business associate. PCI data is payment card data, cardholder data and sensitive authentication data, governed by the PCI Data Security Standard. PHI and cardholder data are specific, regulated subsets that usually also count as PII.
Key takeaways
- PII is a broad concept defined differently by different laws. PHI and PCI data have precise definitions.
- The rules that apply depend on the data type and on your role.
- Classify data first. Controls follow from classification.
- A SOC 2 report can cover systems holding all three, but it does not replace HIPAA or PCI DSS obligations.
Side-by-side
| PII | PHI | PCI data | |
|---|---|---|---|
| What it is | Information that identifies an individual, alone or combined | Health information linked to an individual, held by a covered entity or business associate | Cardholder data and sensitive authentication data |
| Examples | Name, email, government ID number, device identifiers | Diagnoses, treatment records, insurance details with identifiers | Primary account number, cardholder name, expiry date; CVV and PIN data |
| Governing rules | US state privacy laws, sector laws, GDPR for “personal data” | HIPAA, 45 CFR Parts 160 and 164 | PCI DSS, enforced through card brand and acquirer contracts |
| Who enforces | Regulators and attorneys general, by jurisdiction | HHS Office for Civil Rights | Card brands and acquiring banks |
| Typical assurance | Privacy assessments, SOC 2 with Privacy or Confidentiality | HIPAA assessment, SOC 2 with HIPAA mapping | PCI DSS assessment or self-assessment questionnaire |
Points people get wrong
- Health data is not always PHI. Data a consumer enters into an app with no covered entity involved is generally outside HIPAA, though state laws may apply.
- De-identified data is not PHI. HIPAA sets specific methods for de-identification.
- Sensitive authentication data must not be stored after authorization, even encrypted.
- Using a payment processor reduces PCI scope but does not remove it. You still validate through the appropriate questionnaire.
- GDPR’s “personal data” is broader than most US definitions of PII. See GDPR for US SaaS companies.
What this means for controls
- Inventory the data you hold and classify it.
- Keep regulated data in as few systems as possible.
- Apply access control, encryption, logging and retention rules per class.
- Reflect the classification in your system description so the audit scope matches. See how to scope systems for SOC 2.
How SOC 2 fits
The Confidentiality category addresses information you designate as confidential, and Privacy addresses personal information against your privacy notice. See SOC 2 Trust Services Criteria explained, SOC 2 vs HIPAA and multi-framework control mapping.
Frequently asked questions
Is an email address PII?
Usually yes, since it can identify a person.
Can one record be PII, PHI and PCI data at once?
A patient billing record with a card number contains all three, and each set of rules applies to its part.
Does Auditsuisse perform PCI DSS assessments?
PCI DSS validation is performed by Qualified Security Assessors or by self-assessment. Ask us how a SOC 2 scope should treat cardholder data.
Sources & further reading
NIST SP 800-122; 45 CFR 160.103 and 164.514; PCI DSS v4.
Related: Covered entity vs business associate, GDPR assessments, Glossary.
Work with a licensed CPA firm
Auditsuisse Assurance NA PC is a licensed US CPA firm enrolled in the AICPA Peer Review Program. See our published SOC 2 fees or book a scoping call.