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

Contents / Clause 7.3

Clause 7.3: Skinny decryption

Text on this site

Title only, body not in the public preview

Citation

ISO/IEC 18033-7:2022, clause 7.3 (contents entry, page 10)

Key date

15 September 2027 Estimated

What the clause requires

Text not in the public preview

The published contents list entry reads ISO/IEC 18033-7:2022, clause 7.3 (contents entry, page 10). The body is not in the sample we can read, so this page states no requirement from it and does not describe it from memory.

What the public text does not state

  • The body of clause 7.3
  • The inverse round and schedule

What it means for you

The inverse direction for Skinny has its own clause, which is a useful reminder that the standard treats encryption and decryption as separate conformance surfaces. A module can support one direction only, and a product claim that says "Skinny" may mean encryption alone. The buyer s question is which directions the module offers.

The public text does not describe the inverse round, the inverse schedule or the order of operations. The record states that limitation and does not fill it. The evidence request is the same shape as the forward page: a known-answer test for the inverse, or a round trip against the published vector, plus a review note.

This page also carries a procurement point. If a supplier answers "we use Skinny" without naming the direction, the answer is incomplete for any use that needs decryption, which includes most storage and transport uses. The record treats the direction as part of the configuration, not as an implementation detail.

Evidence to keep

What an auditor or a customer is likely to ask for
ArtefactOwnerWhy it matters
Known-answer test for the inverse direction or a published-vector round tripEngineeringProves the inverse, not just self-consistency.
Statement of which directions the module offersProcurementA forward-only claim is not enough for most uses.
Purchase record for the base standard, so clause 7.3 can be readStandards ownerThe clause is not in the public preview without it.

How to verify it

Ask whether decryption is supported. If the answer is yes, ask for the inverse test. If it is no, record the limitation.

Dates

The kit plan for clause 7.3 sets the evidence review at 17 June 2027, 90 days before the estimated publication date of 15 September 2027.

Cross references

Where this comes from

Source for this page

Retrieved 2026-10-20. Our own statement, cited so you can check it.