A.8 Technological controls

A.8.12 Data leakage prevention

Not mandatory by default – decided in your SoA

What it means in plain language

New in 2022: apply measures to detect and prevent unauthorised disclosure or extraction of information.

Is it mandatory? Not automatically. You must consider this control in your Statement of Applicability (6.1.3 d). Include it if your risk assessment, laws, contracts or business needs require it; if you exclude it, write down a justification an auditor will accept.

Why this control matters

Data leakage prevention works best when controls are tuned to actual transfer paths instead of broad assumptions. The operational priority is to classify sensitive content, define detection logic, and manage exceptions so blocking, alerting, and investigation can be justified with evidence rather than treated as one-time technical setup.

Common auditor findings to check for

Potential gaps to test in your own environment, not a claim about observed audit frequency.

  • Rules are deployed for email or web traffic, but cloud shares, endpoint copy actions, and removable media transfers are not covered by the same control logic.
  • Alerts are enabled, yet no owner triages them, so false positives accumulate and real leakage indicators remain open without containment or escalation records.
  • Business exceptions are granted informally, allowing staff to bypass DLP for urgent work without expiry dates, compensating controls, or later review.

How you can implement it

Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.

  • Build the control design around data classes and transfer channels. Identify patterns such as payment card numbers, national identifiers, source code fragments, client lists, and contract files, then set detection for email, browser uploads, USB copying, printing, and sync clients. Align each rule to a business risk and document the approved response: block, quarantine, warn, or log only.
  • Assign operational roles clearly: the information security owner tunes thresholds, system administrators deploy policies, and business managers approve exceptions for legitimate use cases. Require an exception record to state the data type, destination, duration, compensating controls, and review date so temporary access does not become permanent bypass.
  • Run recurring rule reviews using sample alert queues, user complaints, and incident investigations to refine patterns that create noise or miss high-risk activity. Include new applications, collaboration tools, and remote-working pathways in the review scope, because leakage often shifts when staff move data between managed and unmanaged environments.
  • Keep an investigation trail for each significant alert, including the triggering pattern, content snippet or hash, action taken, user contacted, and decision outcome. Feed repeated false negatives or misrouted alerts into corrective action, update the Data Leakage Prevention Procedure, and coordinate with awareness training where user behavior is the root cause.

What an auditor will ask to see

  • DLP policy/rule export listing patterns, channels, actions, and business owners.
  • Alert queue review log with triage notes, false-positive tuning decisions, and escalation records.
  • Approved exception request showing scope, expiry, compensating control, and follow-up review.

Baseline documents in the kit

These free kit documents help you document or evidence A.8.12. Each one is tailored to your organization when you build your kit.

Connect this work to your ISMS

Review the dependencies with A.5.34 — Privacy and protection of personal identifiable information (PII) and A.8.15 — Logging. Keep the ownership and evidence consistent across these activities.

Required information and the kit’s 19-document core for the wider implementation context.

Use the SIG and CAIQ questionnaire accelerator to find supporting documents. A mapping is a starting point: verify your actual operating evidence before answering a buyer.

For help adapting this to your environment, explore ISO/IEC 27001 consulting, starting with a free one-hour consultation.

Get these documents tailored to your organization

109 ready-to-edit documents, including all 19 mandatory ones, tailored from a short scoping questionnaire and linked to your risk register and SoA.

Start free

Plain-language interpretation by an ISO/IEC 27001 lead implementer, not the official text of ISO/IEC 27001:2022.