Clause 2 · Full public text

Normative references

One document is normative: ISO/IEC 29100:2011, the privacy framework. Its principles supply the reason deletion matters, and the draft assumes the reader can use them. No other standard is binding through clause 2.

Citation: ISO/IEC DIS 27555, Clause 2. Held: Full public text.

What the draft asks of an organisation

The draft makes ISO/IEC 29100:2011 the single normative reference. That means the privacy framework's principles are part of the draft's requirements by reference, and a team implementing the draft is expected to know them. The two principles the introduction names are data minimisation and use, retention and disclosure limitation. Neither is optional background: deletion is presented as the control that makes retention limitation real. A dated reference pins the edition, so a later revision of the privacy framework does not silently change this draft. Everything else the draft mentions, including de-identification guidance and deletion tool literature, sits in the bibliography as informative material. The practical consequence is a short reading list with one mandatory item and a longer list of context.

What the public sample holds

Clause 2 is in the free preview in full, in both the DIS sample and the ISO Online Browsing Platform.

What this clause covers, in our reading

A single normative reference keeps the dependency surface small. The privacy framework supplies the vocabulary of principles, and the deletion draft supplies the method that turns a retention principle into dated rules. A reader who has not read the privacy framework can still use the draft, but the justification for each rule will be thin. The two named principles answer different questions. Data minimisation asks whether the record should exist at all. Use, retention and disclosure limitation asks how long it may stay and who may see it. Deletion is the mechanism that closes the second question. The dated reference also tells an auditor which edition of the privacy framework the policy was written against. If the organisation holds a later edition, the clause still points to the dated one for this draft, and the policy can note the later edition as additional context. The bibliography is where tool and de-identification reading lives, and the draft is explicit that those topics are outside its own text. That division is useful in a review: a finding about a wipe method is a tool finding, not a finding against this draft.

What to prepare

1. Record which edition of the privacy framework the organisation holds and which edition its policy cites.
2. Map the two named principles to specific policy lines that already exist.
3. Keep the bibliography separate from the normative reading list in the evidence file.
4. Note any later edition of the privacy framework as context, not as a substitute for the dated reference.

The evidence an auditor or regulator asks for

Tests to run

• Check that the policy cites the dated edition the draft names, not an undated family reference.
• Ask the policy owner to explain how retention limitation is enforced by a deletion rule.
• Confirm that tool and de-identification material is labelled informative, not normative.

What the public text does not settle

• The draft does not reproduce the privacy principles, so the reader needs the other document.
• The draft does not say what to do when a national adoption of the privacy framework differs.

Next

• Add the normative reference and its edition to the policy control sheet.
• Brief the policy owner on the two principles and where they appear.

Other clauses

• Clause 1: Scope
• Clause 3: Terms and definitions
• Clause 4: Symbols and abbreviated terms