ISO 27555 contents: 55 headings

The complete contents of the draft, taken from the public preview: ten clauses and 45 subclauses. The evidence level is shown for each clause, so you can see where the public sample carries the text and where it does not.

Ten clauses and 45 subclauses, in document order.
Code	Heading	Level	Clause page
1	Scope	Clause	Clause 1
2	Normative references	Clause	Clause 2
3	Terms and definitions	Clause	Clause 3
4	Symbols and abbreviated terms	Clause	Clause 4
5	Framework for deletion	Clause	Clause 5
5.1	General	Subclause	Clause 5
5.2	Constraints	Subclause	Clause 5
5.3	Clusters of PII	Subclause	Clause 5
5.4	Retention period and regular deletion period	Subclause	Clause 5
5.4.1	Retention period	Subclause	Clause 5
5.4.2	Regular deletion period	Subclause	Clause 5
5.4.3	Allocation of clusters of PII	Subclause	Clause 5
5.5	Archives and backup copies	Subclause	Clause 5
5.6	Standard deletion periods, starting points, deletion rules and deletion classes	Subclause	Clause 5
5.7	Special situations	Subclause	Clause 5
5.8	Documentation of policies and procedures	Subclause	Clause 5
6	Clusters of PII	Clause	Clause 6
6.1	General	Subclause	Clause 6
6.2	Identification	Subclause	Clause 6
6.3	Documentation	Subclause	Clause 6
7	Specification of deletion periods	Clause	Clause 7
7.1	Standard and regular deletion periods	Subclause	Clause 7
7.2	Regular deletion period specifications	Subclause	Clause 7
7.3	Standard deletion period identification	Subclause	Clause 7
7.4	Deletion period specifications for special situations	Subclause	Clause 7
7.4.1	General	Subclause	Clause 7
7.4.2	Modification of data objects	Subclause	Clause 7
7.4.3	Delayed deletion by allocation to another cluster of PII	Subclause	Clause 7
7.4.4	Suspension of the deletion	Subclause	Clause 7
7.4.5	Backup copies	Subclause	Clause 7
8	Deletion classes	Clause	Clause 8
8.1	Abstract starting points: abstract deletion rules	Subclause	Clause 8
8.2	Matrix of deletion classes	Subclause	Clause 8
8.3	Allocation of deletion classes and definition of deletion rules	Subclause	Clause 8
9	Requirements for implementation	Clause	Clause 9
9.1	General	Subclause	Clause 9
9.2	Conditions for starting points outside IT systems	Subclause	Clause 9
9.3	Requirements for implementation for organization-wide aspects	Subclause	Clause 9
9.3.1	General	Subclause	Clause 9
9.3.2	Backup	Subclause	Clause 9
9.3.3	Logs	Subclause	Clause 9
9.3.4	Transmission systems	Subclause	Clause 9
9.3.5	Repair, dismantling and disposal of systems and components	Subclause	Clause 9
9.3.6	Everyday business life	Subclause	Clause 9
9.4	Requirements for implementation for individual IT systems	Subclause	Clause 9
9.5	Deletion in regular manual processes	Subclause	Clause 9
9.6	Requirements for implementation for PII processor	Subclause	Clause 9
9.7	Control deletion in special cases	Subclause	Clause 9
9.7.1	Exception management	Subclause	Clause 9
9.7.2	Further sets of PII	Subclause	Clause 9
9.8	Handle individual requests for deletion or suspension of deletion	Subclause	Clause 9
10	Responsibilities	Clause	Clause 10
10.1	General	Subclause	Clause 10
10.2	Documentation	Subclause	Clause 10
10.3	Implementation	Subclause	Clause 10

The ten defined terms are in clause 3 and are listed on the clause 3 page. The abbreviation list is clause 4. The 2021 edition has the same clause and subclause count, except that clause 7.4.3 changes its subject.

Why the contents matter to a buyer

The contents is the one part of a draft that is public, stable and checkable. It lets a team map an existing procedure clause by clause before the full text is available, and it makes a change visible without the licensed text. When the DIS moves to an FDIS or to publication, the contents is the first place a change shows.

The paid kit expands all 55 rows into a register with a citation, an evidence level, an evidence artifact, an owner, a status and a due date. See what the kit contains.