Zum Hauptinhalt springen
ISO/IEC 27701:2025 · Annex A, Table A.1 · Control for PII controllers

A.1.4.3 Limit processing

Updated on 5 min Reviewed by: Cenedril Editorial
ISO/IEC 27701:2025GDPR

In the CRM of a logistics company, everybody with a login sees all customer data: warehouse staff see payment defaults, sales sees the complaint history including health details from letters of complaint. Exports to sales partners are produced on demand as spreadsheets, and the oldest records date from a time nobody remembers. Collection was neatly limited. For everything that happened afterwards, there was no rule. A.1.4.3 requires processing after collection to be restricted to what is needed by default, above all for disclosure, storage period and access, and this restriction to be secured through policies and documented procedures.

The control picks up where A.1.4.2 leaves off. That control is about what comes in. This one is about how far the data travels inside and outside the organization and how long it stays.

What does the standard require?

The control makes two demands: one about governance and one about substance.

  • Governance through policies and procedures. The limitation of processing is anchored in the information security and privacy policies. For this, the standard refers to its clause 5.2 on the privacy policy. Documented procedures add how the rules are introduced and how compliance with them is maintained.
  • Three levers, narrow by default. The standard explicitly names disclosure of the data, how long it is stored and the circle of people with access. For all three, the default is the minimum that the respective purpose calls for.
  • The purpose remains the yardstick. Whether processing is adequate, relevant and necessary is always judged against the defined purposes from A.1.2.2. Without a documented purpose, the limitation can neither be set nor checked.

In practice

Extend the policy. Write the limitation into the existing privacy policy; a separate document is rarely needed. What matters more is the procedure behind it: who decides on a new processing activity, who reviews it and where is the decision recorded? Only this second half turns a principle into a rule that still applies after the next change of staff.

Grant access by role. Permissions follow the task. Warehouse staff need delivery addresses. The payment history stays with accounting. Define roles, document them in an authorization matrix and review assignments regularly; for sensitive data, a quarterly cycle works well. The technical foundations come from A.5.15 Access Control and A.8.3 Information Access Restriction.

Govern disclosure. For each processing activity, record which recipients receive data on a regular basis. Disclosures outside that list go through an approval step. On the technical side, export restrictions, approval workflows for bulk exports and data leakage prevention rules all help.

Set the storage period. Each activity gets a time limit derived from its purpose or from a legal obligation. The details are handled by A.1.4.8 Retention.

Start narrow by default. New employees receive a basic role, new reports show aggregated values, new systems hide rarely used fields. Extensions go through a request with a justification.

Typical audit evidence

For A.1.4.3, auditors typically expect:

  • Privacy policy containing the rule on limiting processing and a described approval procedure for new processing activities
  • Authorization concept and records of access reviews (→ Access Control Policy)
  • List of recipients per processing activity and approvals for individual disclosures outside that list
  • Retention periods per activity (→ Records Retention Schedule)
  • Internal audit reports that check compliance by sampling (→ Internal Audit Plan & Report)

KPI

% of processing activities verified to process only necessary PII

Verified means: for the activity, the circle of access, the recipients and the storage period are defined, matched against the purpose and implemented in the systems. The target is 100%. An honest figure only emerges if the review also looks into the systems, since a line in the record alone proves little.

Supporting KPIs:

  • Share of roles whose permissions were confirmed in the last review cycle
  • Number of approved individual disclosures per quarter
  • Share of systems in which the defined storage period is technically enforced

A.1.4.3 corresponds above all to Article 25(2) GDPR. That provision requires privacy-friendly defaults explicitly for the amount of data, the extent of processing, the storage period and accessibility. Under it, personal data must not be made accessible to an indefinite number of people without the individual’s intervention. Behind this stand the principles of Article 5(1)(b), (c) and (e) (purpose limitation, data minimization, storage limitation). Steering through policies reflects Article 24(2), which names appropriate data protection policies as part of the controller’s measures. Article 32(4) adds that people with access to the data process it only on instruction (→ GDPR General Data Protection Regulation).

A.1.4.3 connects privacy objectives with the access and deletion rules of the ISMS:

Sources

Frequently asked questions

How does A.1.4.3 differ from A.1.4.2?

A.1.4.2 limits which data enters the organization at all. A.1.4.3 takes over from there: who may see the data, where it goes and how long it stays. Lean collection is of little use if afterwards every employee can access everything.

Is an access control concept enough?

It covers access, which is one of the three points. Disclosure and storage period need rules of their own. The standard also requires the limitation to be steered through policies and documented procedures, so that it survives changes of staff.

What does "by default" mean for processing?

New systems, roles and reports start with the narrowest scope that makes sense. Anyone who wants to see more or pass data on applies for it with a justification. That way the burden of justification always lies with the extension.

No Cookies!

This wiki collects nothing, bakes nothing and leaves nothing behind. There's nothing to consent to. Privacy doesn't get better than this.