Study guide
8.3 Defense in Depth: Identity, Access Management, and Authentication
Certified Information Privacy Technologist CIPT
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: CIPT Exam Overview and Study Plan
1.1 CIPT Exam Facts, Blueprint, and Study Plan
2 Chapter 2: The Privacy Technologist's Legal and Procedural Role
2.1 Privacy Function Roles: DPO, Data Owner, Steward, Custodian, Legal, and Security 2.2 Translating Legal and Regulatory Requirements into Technical Controls 2.3 Notices, Policies, and Oversight of Privacy Operations, Audits, and Third Parties
3 Chapter 3: Technical Responsibilities: Risk Concepts and Incident Response
3.1 Risk Concepts: Threat, Vulnerability, Attack, Exploit, and Privacy Risk 3.2 Technical Support for Privacy Incident and Breach Response
4 Chapter 4: Privacy Risk Models, Frameworks, and Threat Models
4.1 Privacy Risk Models and Frameworks: Contextual Integrity, Calo, Solove, FIPPs, OECD, NIST, and FAIR 4.2 Privacy Threat Models: LINDDUN and MITRE PANOPTIC
5 Chapter 5: Data Ethics and Automated Decision-Making
5.1 Legal Versus Ethical Processing and the Social Impact of Privacy-Affecting Designs 5.2 Identifying and Minimizing Bias in Automated Decision-Making
6 Chapter 6: Minimizing Privacy Risk During Data Collection
6.1 Notice, Consent Management, and Choice Architecture 6.2 Managing Privacy Risk in Automatic Collection and Telemetry 6.3 Extracting Personal Data from Publicly Available Sources 6.4 Data Retention, Destruction, and Cryptographic Erasure 6.5 Data Minimization Techniques 6.6 Implementing Data Processing Segregation
7 Chapter 7: Minimizing Privacy Risk During Data Use: Aggregation, PETs, and Secondary Use
7.1 Minimizing Privacy Risk from Aggregation and Inference 7.2 De-identification, Pseudonymization, and Tokenization 7.3 Microdata Protection: k-Anonymity, l-Diversity, and t-Closeness 7.4 Advanced PETs: Differential Privacy, Secure Multi-Party Computation, and Homomorphic Encryption 7.5 Secondary Use, Function Creep, and Purpose Limitation Controls
8 Chapter 8: Minimizing Privacy Risk During Dissemination
8.1 Disclosure and Accessibility Controls: APIs, Egress, and Clean Rooms 8.2 Countering Distortion, Exposure, Breach of Confidentiality, Blackmail, and Appropriation 8.3 Defense in Depth: Identity, Access Management, and Authentication
9 Chapter 9: Intrusion, Decisional Interference, and Dark Patterns
9.1 Minimizing Intrusion and Decisional Interference: Behavioral Advertising, Profiling, Cyberbullying, and Social Engineering 9.2 Dark Patterns and Deceptive Design
10 Chapter 10: Privacy Risks Related to Software Security
10.1 Detecting and Fixing Software Privacy Vulnerabilities 10.2 Intrusion Detection and Prevention, and Privacy in Change Management 10.3 Service Providers, Third-Party SDKs, and Supply Chain Risk
11 Chapter 11: Tracking and Surveillance Technologies
11.1 Privacy Risks and Impacts of E-Commerce 11.2 Audio and Video Surveillance, Wearables, and IoT 11.3 Privacy Issues Around Biometrics: Facial, Voice, Fingerprint, and DNA Data 11.4 Privacy Risks and Impacts of Location Tracking 11.5 Internet Monitoring and Web Tracking: Cookies, Fingerprinting, and GPC
12 Chapter 12: Workplace Technologies: AI, Communications, and Monitoring
12.1 Identifying and Minimizing Privacy Risks in AI, Machine Learning, and Deep Learning 12.2 Privacy Risks of Communications Technologies: Video Calls, Messaging, Mobile Devices, Social Media, and Gaming 12.3 Workplace Monitoring and BYOD Privacy
13 Chapter 13: Monitoring and Managing Privacy Risk
13.1 Privacy Audits, IT Control Reviews, KRIs, and KPIs 13.2 Completing Privacy and Data Protection Impact Assessments
14 Chapter 14: Implementing Privacy by Design
14.1 Cavoukian's Seven Foundational Principles of Privacy by Design 14.2 Privacy Goals, Objectives, and Translating High-Level Specifications into Low-Level Specifications 14.3 Hoepman's Privacy Design Strategies: Data-Oriented Strategies 14.4 Hoepman's Privacy Design Strategies: Process-Oriented Strategies
15 Chapter 15: Evaluating Privacy Risks in User Experiences
15.1 Privacy in User Experience: UX Concepts and Usability Testing 15.2 Value Sensitive Design
16 Chapter 16: Privacy Engineering Objectives, Architecture, and the Development Life Cycle
16.1 NIST Privacy Engineering Objectives: Predictability, Manageability, and Disassociability 16.2 Enterprise Architecture, Data Flow Mapping, Lineage, and Cross-Border Transfers 16.3 Managing Privacy Risk in the Software Development Life Cycle 16.4 Applying LINDDUN Threat Modeling in Engineering
17 Chapter 17: Managing and Monitoring Privacy Controls
17.1 Data Inventories, Records of Processing Activities, and Asset Discovery 17.2 Privacy Code Review and Runtime Behavior Monitoring
8.3 Defense in Depth: Identity, Access Management, and Authentication
Key Takeaways Explain This Topic AI
Defense in depth layers identity, authentication, authorization, network, data, detection, and recovery controls so a single failure does not expose personal data.
Least privilege is implemented with RBAC or ABAC, just-in-time elevation, privileged access management, separation of duties, and periodic access reviews.
SMS codes and typed one-time passwords can be intercepted or phished; FIDO2 security keys and passkeys are phishing-resistant because they are bound to the real site's domain.
NIST SP 800-63-4 (July 2025) requires AAL2 providers to offer a phishing-resistant option and AAL3 to use phishing-resistant, hardware-protected non-exportable keys.
Segmentation, short-lived scoped credentials, and per-tenant or per-user keys limit the blast radius of a compromise.
Last updated: October 2026
8.3 Defense in Depth: Identity, Access Management, and Authentication
Quick Summary: Defense in depth layers independent controls so that one failure does not expose personal data. The BoK highlights identity and access management (IAM) and authentication mechanisms as the core layers for protecting personal data during dissemination. Strong designs give every person and service the least access it needs, verify identity with phishing-resistant methods, segment networks and keys so a breach stays small, and log access so misuse is detected.
No single control is perfect. Passwords leak, employees make mistakes, and software has bugs. Defense in depth assumes each layer can fail and asks what the next layer does when it does.
The Layers Around Personal Data
Layer Example Controls What It Stops
Identity Single sign-on, unique accounts, workload identities for services Shared accounts that make actions untraceable
Authentication Multifactor authentication, passkeys, certificate-based service authentication Stolen or guessed passwords
Authorization Role-based (RBAC) and attribute-based (ABAC) access, least privilege, purpose checks Over-broad access by legitimate users
- Network Segmentation, private endpoints, egress allowlists, zero trust Lateral movement after a compromise
- Data Encryption with separate keys, tokenization, masking Readable data after a store is copied
- Detection Access logs, anomaly alerts, data loss prevention Undetected misuse or exfiltration
- Recovery Key rotation, credential revocation, incident runbooks Prolonged exposure after an incident
- Identity and Access Management (IAM)
Least privilege means each identity gets only the permissions its task requires, for only as long as needed. Practical techniques:
Role-based access control (RBAC) groups permissions by job function. It is simple but coarse: a "data scientist" role may allow queries that are fine for fraud work and inappropriate for marketing.
Attribute-based access control (ABAC) evaluates attributes of the user, resource, action, and context (including declared purpose), which supports purpose limitation (Section 7.5).
Just-in-time (JIT) access grants elevated rights for a short window after approval, instead of permanent administrator accounts.
Privileged access management (PAM) vaults administrator credentials, records sessions, and requires approval for sensitive actions.
Separation of duties prevents one person from both requesting and approving access, or from both exporting data and deleting the audit log.
Access reviews (recertification) periodically confirm that each person still needs each permission, and joiner-mover-leaver processes remove access when people change roles or leave.
Break-glass access for emergencies records who opened sensitive records and why, and triggers review.
Service accounts and APIs need the same discipline: short-lived tokens, narrowly scoped OAuth scopes, workload identities instead of embedded keys, and mutual TLS between services.
Authentication Mechanisms
Authentication factors fall into three categories: something you know (password, PIN), something you have (security key, phone, smart card), and something you are (fingerprint, face). Multifactor authentication (MFA) combines at least two categories.
Not all MFA is equal. One-time codes sent by SMS can be intercepted through SIM swapping, and codes typed into a fake login page can be relayed in real time by phishing proxies. Phishing-resistant authenticators, such as FIDO2/WebAuthn security keys and passkeys , bind the login to the real website's domain, so a look-alike site cannot reuse them.
NIST's SP 800-63-4 Digital Identity Guidelines , finalized in July 2025 and replacing SP 800-63-3, set three Authenticator Assurance Levels (AALs) :
- Level Requirement (summary)
- AAL1 Single-factor or multifactor authentication
AAL2 Multifactor authentication, and providers must offer a phishing-resistant option; synced passkeys can qualify
- AAL3 Phishing-resistant authentication with a hardware-protected, non-exportable key
- Privacy Considerations in Authentication
Authentication systems themselves collect personal data, so privacy technologists check them too:
Biometrics: prefer on-device matching (the template never leaves the phone's secure hardware) over central biometric databases (Section 11.3).
Risk-based authentication uses signals such as device, location, and behavior; collect only what the risk model needs, disclose it, and keep it briefly.
Identity proofing often demands identity documents; retain the verification result rather than copies of documents where rules allow.
Account recovery is frequently the weakest link; recovery by security questions or SMS can undo strong MFA.
Federation (OpenID Connect, SAML) can limit what each relying party learns, for example by releasing only needed claims or pairwise identifiers that differ per service.
Reducing Incident Blast Radius
In systems engineering, the blast radius represents the maximum scope of compromise if a specific component, credential, or microservice is breached. Monolithic architectures possess an unconstrained blast radius: compromising a single web application server grants access to global database credentials, exposing all historical records across all users and tenants.
Privacy-preserving architectures minimize blast radius through defense-in-depth controls: +-------------------------------------------------------------------------+
- | BLAST RADIUS CONTAINMENT |
- | |
- | [Compromised Web App] |
- | | |
- | v (Blocked by Micro-segmentation & ZTNA) |
- | x - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - |
- | | Direct Database Access BLOCKED | |
- | x - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - |
- | | |
- | v (Must request short-lived, scoped token via OAuth 2.0) |
- | [Token Issuance Broker] |
- | | |
- | v (Returns ephemeral token scoped to single tenant / record) |
- | [Isolated Microservice with Row-Level Security] |
- | | |
- | v (Accesses encrypted partition with tenant-specific KMS key) |
- | [Target Data Partition] (Max breach: 1 tenant, 1 transaction) |
- +-------------------------------------------------------------------------+
Micro-Segmentation and Zero Trust Network Architecture (ZTNA) : Services communicate exclusively over mutual TLS (mTLS) with cryptographically attested identities (e.g., SPIFFE/SPIRE). Analytical clusters cannot establish physical or logical TCP connections to the PII identity vault.
Ephemeral Scoped Access : Services do not maintain long-lived static database credentials with broad table permissions. Operations utilize short-lived security tokens (e.g., AWS STS, Vault dynamic secrets) scoped strictly to the current tenant and transaction context.
Decoupled Key Hierarchies : By using distinct cryptographic keys per tenant or per user in Key Management Services (KMS), the compromise of a single key reveals only an isolated slice of ciphertext, rather than decrypting the global database.