Overview

Text not public. The public view of the draft withholds this unit. The page states its position, what it asks the reader to prepare and the evidence an auditor samples. It does not state the clause text.

What it says, in our words

The public view of the draft does not carry the text of clause 4. The table of contents places an Overview between the terms and the introduction to big data, and the document's own structure suggests what an overview does in this family of standards: it sets out the shape of the guidance, the relationship between the characteristics, the threats and the controls, and the place of the risk process that follows. This page does not state what the clause says.

What it means for an ISMS manager

Plan for an overview that connects the parts, because that is what the position in the contents requires. When the published text arrives, read clause 4 first and use it to check the order in which your own method handles the material. If the overview introduces a distinction the later clauses rely on, for example how a characteristic differs from a threat, that distinction belongs in your glossary and in the briefing you give control owners. Until then, do not quote the clause and do not build a training slide around it. An overview is the part of a guidance document most likely to be paraphrased badly by a consultancy, and the reader who has the official text will notice. Keep the placeholder in your reading plan and record the date you will fill it.

What an auditor samples

• The reading plan for the published edition, with clause 4 assigned to a named reviewer.
• The glossary entry or briefing note that will be updated from it.
• The review date in the ISMS calendar.

Evidence lines are the artefacts an auditor or a reviewer asks to see. They are named here so the work can be planned; they are not a certificate and they do not replace the official text.