Skip to content
Cryptography
ASD ISMISM-1766

ASD ISM 1766 Use a SHA-2 output size of at least 224 bits

What it says

When using SHA-2 for hashing, an output size of at least 224 bits is used, preferably SHA-384 or SHA-512.

Quoted as published. Everything else on this page is written by Control Stack.

In plain English

In non-classified, OFFICIAL: Sensitive and PROTECTED systems, any use of SHA-2 for hashing must have an output of at least 224 bits, with SHA-384 or SHA-512 preferred.

When SHA-2 is used for hashing, the output size must be at least 224 bits, preferably SHA-384 or SHA-512. SHA-2 is a family of hashing algorithms, which turn data into a fixed-length value called a digest. Output size is the digest's length in bits. Every standard variant meets this minimum, including the widely used SHA-256, but a digest truncated to under 224 bits does not. The ISM applies this control to non-classified, OFFICIAL: Sensitive and PROTECTED systems only. ISM-1767 and ISM-1768 set higher minimums for SECRET and TOP SECRET.

Why it matters

Shorter digests make collisions (two inputs sharing a digest) easier to find, so a forged file or signature could pass a check. A 224-bit output gives about 112 bits of security strength, ASD's target at these levels; SHA-384 or SHA-512 adds margin.

How to implement

  1. Find every place each system in scope uses SHA-2.

    Cover certificate and code signatures, TLS and VPN settings, integrity checks, password storage and in-house code. Read each variant, such as SHA-256, and any truncation, from configuration, code or vendor documentation. Other hashes, such as MD5 or SHA-1, fall under ISM-0471, which allows only approved algorithms.

  2. Fix any SHA-2 output kept below 224 bits.

    Where code keeps only part of a hash digest (an HMAC tag is not one), keep the full digest or at least 224 bits of it, and recompute shortened values already stored. A bought product that cannot change does not meet this control until replaced.

  3. Make SHA-384 or SHA-512 the default for new and changed settings.

    Set them in certificate templates, signing tools, configuration baselines and coding standards wherever the product and the systems it works with support them. SHA-224 and SHA-256 still meet this control, so a product limited to them is compliant.

  4. Confirm the variant in bought products and services.

    Read the vendor's documentation or cryptographic bill of materials, or inspect what the service presents, such as its certificate's signature algorithm. Where a product offers a choice, select SHA-384 or SHA-512.

Keep it running

Recheck hash settings when a system, certificate template or signing tool is added or changed, and when a system is reclassified to SECRET or TOP SECRET, where ISM-1767 or ISM-1768 applies instead. ASD does not plan to approve SHA-224 or SHA-256 beyond 2030.

Evidence and audit

  1. Check 1 of 2What an auditor asks for

    Ask for

    Stored SHA-2 digests, such as integrity records, sampled by the auditor from each in-scope database or file where a code search or product documentation shows they are stored.

    Look at

    The length of each value.

    Good evidence

    Every sampled digest is at least 224 bits once decoded (28 bytes, or 56 hexadecimal characters), so none has been cut below the minimum.

  2. Check 2 of 2What an auditor asks for

    Ask for

    Hash calls found by a code search across every in-house repository for in-scope systems, and vendor documentation for a sample of bought products drawn from software discovery.

    Look at

    The SHA-2 variant each call and product uses, and whether any code keeps only part of a hash digest (an HMAC tag is not one).

    Good evidence

    Every SHA-2 call and sampled product keeps at least 224 bits of output, with no digest truncated below that, confirmed from code, configuration or vendor documentation rather than assumed.

Mappings

Closest match in ISO/IEC 27001: A.8.24, Use of cryptography, which this control partially meets.

ISO 27001

ISO/IEC 27001: 1 mapping

  • A.8.24Use of cryptographyPartially meets

Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.