ISO/IEC DIS 27007 · stage 40.60, close of voting Ballot closed 23 September 2026 Planning date 12 September 2027, an estimate Official text
27007ISO 27007 Revision CheckerISMS audit guidance, clause by clause

Free edition check

Which ISO 27007 edition applies to your next audit?

Six questions. A dated answer computed from the record on this site, in your browser. No account, no email, no request. The check tells you whether the 2020 guidance covers your next audit, which 2013 dependencies to review, and what to do before the planning date.

What it will not do

It does not audit you, score you or call you compliant. It does not predict a publication date. It places your answers against the public stage record and the clause map, and says what it cannot decide.

The result is a reading of your answers, not a certification decision.

The check
Your audit programme

The guidance concentrates on first and second party audits. Some of it is not appropriate for a certification audit.

The 2020 Annex A rows were written against the 2013 edition. The DIS aligns them to 2022.

Clause 5 is about managing a programme, not only running audits.

The 19011 revision expands remote audit guidance, and the DIS aligns to it.

A month is enough. The check uses it to place the audit before or after the planning date.

The planning date is 12 September 2027. You can choose earlier.

Nothing is sent anywhere. Reload the page and the answers are gone.

How it decides

The rules behind the result.

The check uses four facts from the record: the published edition is ISO/IEC 27007:2020; the DIS is at stage 40.60 and does not replace it; the planning date is 12 September 2027, an estimate; and the 2020 Annex A rows were written against ISO/IEC 27001:2013, while the DIS moves them to 2022.

It places your next audit before or after the planning date. If your criteria or annex rows are on the 2013 edition, it returns the dependency state even when the audit is soon. If a required answer is missing, it returns scope incomplete and names the missing answer. It never defaults an unknown to the lighter pathway.

The result is generated from the same record the pages use. The engine is deterministic and runs no model.