ISO has published a new edition of its defence technical-review and audit standard. Teams should check edition references and contractual authority while monitoring a forthcoming correction.
Source published: 2026-10-09
Audience / jurisdiction: International; defence acquisition programmes, including US Department of Defense and other defence-agency projects
A new edition for defence technical reviews and audits
ISO published ISO/IEC/IEEE 24748-8:2026, Systems and software engineering — Life cycle management — Part 8: Technical reviews and audits on defence programs, on 9 October 2026. The official catalogue identifies it as edition 2 and a published International Standard, rather than a consultation draft.
The new edition replaces ISO/IEC/IEEE 24748-8:2019, whose withdrawal is recorded on the same date. This confirms a change in the published edition. It does not, by itself, establish which technical provisions have changed or whether an organisation must immediately revise its project arrangements.
For practitioners, the immediate issue is therefore edition control: knowing which version a project references and separating the newly published standard from the requirements already agreed for that project.
Sources: [1]
Who should assess the publication
The standard addresses technical reviews and audits throughout defence acquisition, including projects for the US Department of Defense and other defence agencies. Its scope includes criteria for initiating, completing and evaluating those activities, and helping buyers and suppliers agree which reviews and audits a project needs and what they should achieve.
The relevant audience includes acquisition teams, systems and software engineering leads, suppliers, and managers responsible for technical reviews and audits. This is not a general update to management-system certification auditing.
As an editorial starting point, organisations working in this scope should identify where the standard appears in their project documentation. A reference in a contract deserves a different approval route from a reference in an internally maintained guidance document.
Sources: [1]
A correction is progressing, but is not yet confirmed as published
A related Technical Corrigendum 1 entered the under-publication stage on 27 October 2026. The opened ISO catalogue entry still identifies the correction project as under development; it does not confirm a published corrigendum.
That distinction matters when communicating the update. The second edition is published, while the correction remains in the publication process. The available evidence does not establish the correction's contents or publication date.
Teams can begin assessing the new edition without assuming what the correction will say. As a practical precaution, anyone preparing revised templates or training should check the correction's status again before approving those materials.
Publication does not establish compulsory adoption
The dates serve different purposes. The 9 October date records publication of the new edition and withdrawal of its predecessor. The 27 October date records a development milestone for the corrigendum. Neither is evidence of a legal effective date or a contractual transition deadline.
The consulted catalogue records establish publication status and scope, not a government mandate or an amendment to an existing agreement. No mandatory adoption date was established from these sources.
Accordingly, the authority responsible for each acquisition or contract should determine the applicable edition before project criteria change. Catalogue withdrawal and contractual applicability should be treated as separate questions.
Practical next steps for project and audit managers
The following are editorial suggestions, not additional requirements from the standard. First, inventory contracts, technical-review plans and supplier agreements that reference the 2019 edition. Record the cited edition, document owner and person authorised to approve a change.
Next, obtain authorised access to the new edition and arrange a documented comparison with the edition currently used. That assessment should identify proposed changes to review criteria, responsibilities and supporting documents without assuming that every difference requires immediate implementation.
Finally, check the corrigendum status before approving revised materials. Keep proposed improvements separate from confirmed contractual obligations, and document the decision on which edition each affected project will use.
Sources
- ISO/IEC/IEEE 24748-8:2026 — Systems and software engineering — Life cycle management — Part 8: Technical reviews and audits on defence programs
- ISO/IEC/IEEE 24748-8:2026/Cor 1 — Technical Corrigendum 1
Your experience
Which of your current defence-project review plans cite the 2019 edition, and who has authority to approve a change of edition?
Originally published by AdviseISO, a knowledge-sharing initiative of W3 Solutionz.
