Standards
The Information Security Manual.
The controls in ASD's Information Security Manual (September 2026) that a buyer asks a software supplier about, and how we meet each. An IRAP assessor judges your whole system; this is the evidence for that assessment.
| Control | What it asks | How we meet it |
|---|---|---|
| ISM-2044 | No default credentials | The first credential is created on your host at install, and works once. |
| ISM-1797 | Signed installers, patches and updates | ECDSA P-384 signatures, checked before anything is unpacked. |
| ISM-2154 | Dependencies pinned to approved versions | There are no third-party packages to pin. |
| ISM-0400 | Development, test and production kept apart | Every release is test-installed on a fresh, throwaway host first. |
| ISM-1173 | Multi-factor sign-in for privileged users | Required, and enforced by the engine itself. |
| ISM-1403 | Lockout within five failed attempts | Locked at the fifth. |
| ISM-1569 | A shared responsibility model | Published, on the procurement page. |
| ISM-2124, ISM-2125 | Service provider access restricted and logged | None exists: we cannot reach an installed system. |
| ISM-2073 | A post-quantum transition plan | Published, with a date on every step. |
Software development and delivery
Security requirements and design decisions are written before code (ISM-2033, ISM-2034). Every change is reviewed against a written gate and the review is recorded (ISM-2060, ISM-2061). Every product test suite runs before any build, and the first failure stops it (ISM-2032, ISM-2062). No third-party library is imported (ISM-2029). Releases arrive signed, and your system checks their integrity and authenticity at acceptance (ISM-1790 to ISM-1792). The compiler rebuilds itself byte for byte, the base for reproducible releases (ISM-2155). The full cryptographic bill of materials is available under NDA (ISM-2083).
Sign-in, sessions and logging
Multi-factor sign-in is available to every account (ISM-0974) and pairs something you know with something you have (ISM-1401). Session tokens are 256-bit random values held server side and stored only as hashes (ISM-2065, ISM-2066); cookies are HttpOnly and SameSite (ISM-2063). Every API that changes or reads protected data authenticates and authorises the caller (ISM-1817, ISM-1818). The software logs what you need to detect a security event and keeps secrets out of its logs (ISM-2051, ISM-2052).
AI controls
The software reports only until an administrator switches on blocking, and that switch is audited (ISM-2113). It learns only inside your install, so your data never trains anything of ours (ISM-2103). What it learns is data in an encrypted, authenticated store, never executable (ISM-2072, ISM-2086). It is not an agentic or generative AI application: it calls no tools and takes no instructions from the content it reads.
Download the ISM datasheet (PDF), with every control we were asked about. What is still to come, such as the software bill of materials and the disclosure policy, is on the assurance roadmap.