ISO/IEC 18033-7:2022/DAmd 1 · stage 40.60 Close of voting Record read 20 October 2026 Publication estimated 15 September 2027, our estimate Official record
18033
-7
ISO 18033-7 Revision CheckerTweakable block ciphers, recorded before publication

The kit

The register you can hand to an auditor or a consultant

USD 799, one off. Six sheets, delivered as PDF, CSV and XLSX. Built from the same record as the free pages, so the citation on a row is the citation on the page. Reissued at no extra charge when the amendment publishes.

What the register records

Each row names the algorithm, the block length, the key length, the tweak length and the standard version, then the action, the owner, the evidence, the due date and the band. Those are the fields an auditor or a customer will ask for, and they are the fields the free check uses to decide the scope band.

What is in it

SheetRowsWhat it does
Obligation register46Every unit, the action, the owner, the evidence and the band. One row per thing to do.
Evidence sheet46The artefact, who owns it, why an auditor asks for it and how long to keep it.
Dated plan8From 270 days before the estimate to 30 days after publication, with a named owner and the trigger.
Supplier questions8Eight questions for a module supplier, with the answer that closes each one.
Decision record1A one-page record of the scope question, the answer, the evidence and the next review.
Reissue triggers6The stage change, the text change, the page count change, the identifier change, the date change and the annual review.

Who it is for

The ISMS manager who has to answer the question in a management review, the CISO who has to sign the decision, and the consultant who has to hand a client something better than a marked-up PDF. It is written for a reader who knows the standards language and wants the evidence, the owner and the date in one place.

Who it is not for

It is not a test lab report, a certification, a key management system or a reproduction of the standard. It does not implement a cipher and it cannot tell you whether your code is correct. It tells you what to ask, what to keep and when to act.

How the register is built

Every row cites a clause or an annex from the public record. Where the text is not in the public preview, the row says so and the action is a purchase or a supplier question rather than an assertion. The plan dates are computed from the estimated publication date, and the estimate is labelled. The register hash is on the changelog, so a later reissue can be compared with the copy you hold.

Delivery and reissue

After checkout, sign in with the address you paid with and the three files appear on this page. When the amendment publishes, the register is reissued and kit buyers are emailed. The old copy stays valid as a record of what you planned against.

Not legal advice; does not certify. If a file is faulty, we resupply or refund as the law requires.