DAPLE (C1) flashcards

36 cards. Read the term and the definition here. The deck at the top of this page is optional.

Lawful basis

A GDPR Article 6 condition making processing permissible: consent, contract, legal obligation, vital interests, public task, or legitimate interests. Every processing activity needs at least one documented basis.

Special category data

Personal data needing an extra Article 9 condition: racial or ethnic origin, political opinions, religion, trade-union membership, genetic and biometric identification data, health, sex life, sexual orientation.

Joint controllers

Two or more parties that jointly determine purposes and means of processing. Article 26 requires a transparent arrangement allocating responsibilities, but each party remains liable toward data subjects.

Data Protection Impact Assessment

A structured assessment required where processing likely creates high risk, such as systematic monitoring or large-scale special-category processing. It documents necessity, proportionality, risks and mitigations before processing starts.

Accountability principle

The obligation to demonstrate compliance, not merely achieve it. Evidence includes records of processing, policies, DPIAs, training records, and audit results retained and available to a supervisory authority.

Records of Processing Activities

An Article 30 register listing each processing activity with purposes, data and subject categories, recipients, third-country transfers, retention periods, and security measures. It is the backbone of governance evidence.

Storage limitation

A principle requiring personal data to be kept no longer than necessary for its purpose. Operationally it means a defined retention trigger plus a documented, executed disposal method.

Privacy champion network

Business-unit representatives who embed privacy requirements into local processes, triage questions to the central privacy team, and surface new processing activities before they go live.

Data classification tiers

A scheme such as Public, Internal, Confidential, Restricted that assigns handling rules - encryption, access approval, retention, disposal - based on sensitivity and harm if disclosed.

Data flow mapping

A record of how personal data moves between systems, teams, processors and jurisdictions, including collection points and recipients. It exposes cross-border hops and shadow transfers missed by system inventories.

Unstructured data blind spot

Documents, email, images and chat hold personal data outside database schema, so discovery tooling and user reporting are needed to include them in inventory and retention enforcement.

Data inventory metadata

Per-asset attributes such as owner, hosting location, classification, lawful basis, retention rule, access group and transfer mechanism. These attributes make the inventory usable for DPIAs and rights requests.

Defence in depth

Layering independent controls across perimeter, network, host, application and data so a single failure does not expose personal data. Each layer should map to a specific identified threat.

Zero trust architecture

A model that removes implicit trust from network location. Every request is authenticated, authorised and encrypted per session, with least privilege and continuous verification of context.

Break-glass account

An emergency privileged account used when normal access fails. It requires documented approval, time-boxed use, full session logging, and post-use credential rotation and review.

Data masking in test environments

Replacing or obscuring production personal data before use in non-production systems, so developers and testers work with realistic but non-identifying values. Tokenisation and synthetic data are alternatives.

Authenticated encryption

Encryption that provides both confidentiality and integrity, such as AES-GCM, or CBC combined with a separate MAC. It detects tampering that unauthenticated modes would silently accept.

Envelope encryption

A pattern where a data key encrypts the data and a root key held in an HSM or KMS encrypts the data key. Rotating the root key avoids re-encrypting bulk data.

Password key derivation function

A deliberately slow, salted algorithm such as Argon2, scrypt, bcrypt or PBKDF2 used to store passwords. Salting defeats precomputed tables; slowness raises offline cracking cost.

Crypto-agility

Designing systems so algorithms, key lengths and providers can be replaced without redesigning the application. It enables migration from deprecated ciphers and preparation for post-quantum algorithms.

Attribute-based access control

Authorisation decisions computed from attributes of user, resource, action and context, such as department, data classification and time. It supports fine-grained, policy-driven decisions better than static roles.

Just-in-time privilege elevation

Granting administrative rights only for a defined window after approval, then revoking automatically. It reduces standing privilege and creates an auditable record of who held elevated access and when.

Access recertification

A periodic review in which managers or resource owners confirm each user's entitlements remain necessary. Unconfirmed or orphaned access is revoked, producing evidence for audit.

FIDO2 phishing-resistant authentication

A standard using public-key credentials bound to the originating website, typically via hardware keys or platform authenticators. It resists credential phishing because no shared secret is transmitted.

Awareness moment for breach clock

The point at which an organisation has a reasonable degree of certainty that a security incident occurred and personal data may be affected. The 72-hour notification period starts here.

Chain of custody

A documented, unbroken record of who handled digital evidence, when, and what was done. It includes hashes at collection and supports admissibility in legal or regulatory proceedings.

Phased breach notification

Submitting an initial notification within the deadline with known facts, then supplementing as the investigation progresses. It satisfies the timing rule without waiting for complete scope.

Processor breach notification duty

A processor must inform the controller without undue delay after becoming aware of a personal data breach. The controller, not the processor, decides on authority and data-subject notification.

Transfer impact assessment

An analysis of the destination country's laws and practices, particularly public-authority access, and whether supplementary technical or organisational measures make the transfer effectively equivalent to domestic protection.

Standard Contractual Clauses

Pre-approved contractual terms used to legitimise transfers to countries without an adequacy decision. They impose obligations on importer and exporter and require a supporting transfer assessment.

Sub-processor authorisation

The rule that a processor may engage another processor only with prior or general written authorisation from the controller, with notice and objection rights and equivalent obligations flowed down.

Vendor exit and deletion

Contractual provisions covering return of data in a usable format, confirmed deletion, transition assistance, and escrow for critical services when the relationship ends.

Differential privacy

A technique adding calibrated noise to query results so an individual's presence in a dataset cannot be reliably inferred. The epsilon parameter trades accuracy against privacy protection.

Data protection by default

A requirement that default settings collect and expose only the personal data necessary for the chosen purpose, without the user having to change configuration to reduce exposure.

Pseudonymisation

Replacing identifiers with codes so data cannot be attributed to a person without additional separately held information. The data remains personal data and within scope of the law.

Federated learning privacy risk

Training models locally keeps raw data distributed, but shared model updates can leak information through memorisation or gradient inversion, so noise, aggregation limits and secure aggregation are needed.