United Kingdom

UK MoD JSP 936 Dependable AI in Defence Part 1: Directive (V1.1, 2024)

67 controls. 0 other frameworks in our corpus share controls with it. Here is all of it, and how much of it you are already doing.

Page built . This page is derived from the framework corpus, which changes when the corpus is extended rather than daily.

67 controls 0 frameworks share controls with it United Kingdom verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

There is no implementation kit for this framework yet. The control list and the overlap above are free and complete.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

No measured overlap with another framework in the corpus.

Every control

CodeControlAlso in
1-12Purpose, policy basis and characterisation of AI, software and security in scope0
100-101Appoint a RAISO who assures responsible AI across all projects in scope and sets the culture0
102On transfer of AI, establish accountability in the receiving organisation and have its RAISO accept the risk0
103-104Put context-appropriate roles in place; every project identifies its RAISO and medium or high risk projects inform them0
105-106Provide an Ethics Manager and independent ethics assurance for large, high-ethics-risk or production-line AI work0
107-108Consult the DAU before external communications on ethically sensitive work and legal advisers on legal aspects0
109-111Non-sovereign AI and allied interoperability0
112-114Satisfy the RAISO that shared, exported or imported AI and data meet ASR policy and respect host-nation considerations0
115-118Human/AI teaming and Human Centred Design0
119-121Apply a recognised, resourced Human Centred Design approach across the lifecycle, and HFI under JSP 912 for military capability0
122-123Identify users and their needs, involve them in development and testing including after retraining, and apply human sciences to the design0
125Analyse the allocation of functions between humans and AI across all modes and autonomy levels0
127-128Assess and plan for workforce implications from the outset and keep re-evaluating0
129-131Train users to understand behaviour, limits and calibrated trust, include edge cases, and assure collaborative learning teams case by case0
13-16Apply the directive from the outset of capability development, across the whole life cycle and all stakeholders, in proportion to maturity0
132-134Lifecycle models: DevOps, MLOps and the directive's lifecycle-agnostic stance0
135-137Plan the AI lifecycle with version-controlled plans that embed the ethical principles0
140-142State performance requirements, run a hazard analysis including data failure modes and feed new hazards to system safety0
143-148Keep requirements traceable, demonstrate learned behaviours meet high-level intent, specify the operating context and data, and state how each requirement is verified0
150Make the AI architecture traceable to requirements and protective against identified failure modes0
151-153Justify and document algorithm design choices and performance measures, and optimise for the operational context0
154-155Maintain traceability in implementation and justify and check every framework and library0
156-160Demonstrate data is relevant, complete, balanced and accurate, and keep training, test and verification data separate and representative0
161-163Assure data provenance, keep all influencing data under configuration management and validate synthetic data0
165-168Document each model's assumptions, dependencies, errors and ODD; check this before re-use; design for interpretability; classify models with their data0
17-18Tailor only through a recorded risk assessment managed under Section 30
170-173Verify and validate across the ODD and its boundaries, demonstrate safe behaviour outside it, regression test updates and evidence sufficiency0
174-177Confirm performance in the real operating context, analyse environment differences, re-demonstrate after substantive host changes and define the approved ODD0
178-181Write proportionate Security Operating Procedures, monitor environment and performance, add expert checks for risky decisions and control modification0
183-186Leadership maintains AI competence: analyse roles, train and supervise staff, and bring in external support where in-house competence falls short0
187-189Apply JSP 940 quality policy to AI with planning and assurance scaled to risk and maturity0
19-22TLB Holders and Chief Executives direct, resource and delegate to competent people0
190-194Evidence-based safety management: analyse unique AI safety risks early, include them in safety cases, meet Def Stan 00-055 and 00-056 and manage risk under JSP 892 at AI pace0
195-197Secure by Design with continuous assurance: analyse AI-specific security risks such as data poisoning and adversarial inputs from the earliest opportunity0
198-200Require externally acquired AI to meet the directive with equal confidence, and require suppliers to understand the Defence context and demonstrate competence0
201-202Require arguments for third-party software and assured, documented provenance of all training and test data0
203-204Contract for through-life access to data, algorithms and models with clear IP ownership, and assess export control restrictions on freedom of action0
205-208AI assurance as an overlay on traditional software assurance, assurance risk and the system context0
206Do not adopt AI where assurance risk is intolerable; otherwise assure in proportion to the risk of incorrect outputs0
209Assure behaviour on excursions from the ODD, including adversarial causes, with failure mode behaviour chosen and confidence matched to risk0
23-26Apply Def Stan 00-055 and 00-056, review current standards and prefer civil standards with a military delta0
28Record and agree the risk balance for choosing AI over existing technology for major and higher risk components0
29-37Robotic and autonomous systems and digital systems: definitions and the continuum of autonomy0
35-36Account for the level of autonomy and test the military delta of dual-use systems0
38-39Define the ODD of AI in digital systems and identify every in-scope digital system as AI-based0
40-41State AI use in products and official statistics and give risk owners the assurance information0
42-43Identify alternative information sources and the influence of AI advice in system risk analysis0
44-49The ASR perspectives and the five MOD AI Ethical Principles0
47-48Take legal advice from the start and communicate the controls that keep AI use lawful0
50-51Consider the ethical principles as early as practicable and signpost redress0
52-55Human-centricity: identify everyone affected and assess impact across all modes using Human Security factors0
56-58Responsibility: name responsible persons through the governance chain and articulate human involvement for every context of use0
61-65Understanding: give each stakeholder group the level of understanding it needs, within security limits and in the system-of-systems context0
67Set an open, inclusive culture for raising AI issues and ethical risk assessment0
69-71Bias and harm mitigation: analyse data, algorithms and models for unwanted bias, and monitor and mitigate harms including from intentional bias0
75Define and communicate the operating context and bound the system's behaviour0
76-78Set and demonstrate performance targets for the operating context, reconsider inherited targets, and define responses to out-of-design inputs0
79-81Analyse security threats across the development environment and supply and data chains, install guards and minimise the attack surface0
82Analyse failure modes, including inter-system emergent effects and cascading failures0
83-85Research ethics: comply with JSP 536, declare AI used in research and apply the principles at every readiness level0
86-88Run an AI ethical risk assessment at the outset and on material change, review it at senior level and rate each use case on residual risk to set the approvals route0
89-90Refer special-attention and high-ethical-risk applications to the DAU0
91Halt development or deployment safely when ethical risks become unacceptable0
92-93Manage ethical risk throughout the lifecycle and have the RAISO manage trade-offs with operational effectiveness0
95Develop and communicate evidence of ethical development and use, as transparently as security allows0
96-98Governance of AI builds on existing software governance0
99TLB Executive Boards give 2PUS an annual Statement of AI Ethical Assurance backed by auditable evidence0

Tell me when UK MoD JSP 936 Dependable AI in Defence Part 1: Directive (V1.1, 2024) files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What this page is

A control-level reference for UK MoD JSP 936 Dependable AI in Defence Part 1: Directive (V1.1, 2024), drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition