Clause 1 · Public
Scope
The scope states what the document is for and who it is for. It gives guidance on managing the risks and navigating the threats that arise across the life cycle of a big data system, from the characteristics that make it different: volume and velocity, variety and variability, volatility and veracit
Public text. This clause is public in the draft. The statement below is ours and the clause number is the citation; the official wording is the one to check against.
What it says, in our words
The scope states what the document is for and who it is for. It gives guidance on managing the risks and navigating the threats that arise across the life cycle of a big data system, from the characteristics that make it different: volume and velocity, variety and variability, volatility and veracity, validity and value. It says the guidance applies when big data is used in the design and rollout of AI systems. It closes by saying that every organisation which develops or uses big data systems is covered, whatever its type, size or purpose.
What it means for an ISMS manager
Read the scope as an applicability test, because that is what it is. The document does not ask whether an organisation is large, regulated or in a particular sector. It asks whether the organisation develops or uses big data systems. If the answer is yes, the guidance is written for you, and the practical question becomes which of the eight characteristics your systems actually show. The second thing the scope settles is that this is not a technology-only document. It names AI systems in the same sentence as the big data life cycle, so a data platform that feeds a model is inside the guidance, and so is a model that produces data the platform then holds. Write the applicability note against the scope's own words, not against a vendor's summary.
What changed in this unit
- Clause 1: validity in scope. This draft's scope sentence lists all eight, with validity between veracity and value.
The characteristics this covers
What an auditor samples
- A one-page applicability note naming each big data system, the business owner and the date.
- The data inventory extract that shows those systems, with the data types and volumes.
- The risk assessment or method that already covers them, so the guidance can attach to it.
- The board or risk committee minute that records the decision to prepare now or wait.
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.
Cross-references in the draft
Clause 1 cross-refers to 3.1.4, 5.2, 6, 7. Public text. The scope in this draft lists eight characteristics and adds validity to the seven the first draft carried.
Where this comes from
- Public view of ISO/IEC DIS 27045.2 in the ISO Online Browsing Platform. The table of contents, foreword, introduction, clause 1, clause 2, clause 3.1, clause 3.2 and clause 5 are public. Clauses 4, 6, 7 and Annex A are not. Retrieved 21 October 2026.
- ISO record for ISO/IEC DIS 27045.2 (88970). Status, stage 40.60, close of voting, edition 1, 26 pages, CHF 67, committee, ICS codes and the abstract. Retrieved 21 October 2026.
- ISO stage feed for 88970. The feed states that the document reached stage 40.60 on 2026-08-07. Retrieved 21 October 2026.