Control framework changelog
We maintain the default control frameworks so they stay accurate and usable. This page lists the changes to their content, what each change means for your use cases, and the Deeploy release that contains it. For changes to the Deeploy platform itself, see the changelog.
Frameworks and versions
| Framework | Current version | Based on | Last updated |
|---|
| EU AI Act | 2024/1689 | EU regulation laying down harmonised rules on artificial intelligence | February 2026 |
| ISO/IEC 42001 | 2023 | ISO/IEC 42001 AI management system standard | September 2025 |
| AIUC-1 | October 2025 | AIUC-1 standard | June 2026 |
| NIST AI RMF | 1.0 | NIST AI Risk Management Framework | January 2026 |
| Deeploy AI Control Framework | 1.0 | Developed by Deeploy | February 2026 |
How we version frameworks
- Corrections and improvements are made to the current version of a framework and listed below.
- Significant changes, for example when the underlying standard or regulation is revised, are released as a new version. A new version shows up as a new framework in your list of control frameworks, next to the existing version. It doesn't replace the existing version, and you choose when to apply it to a Workspace.
How to read the tables
The date is the release date of the Deeploy version that contains the change. The version is the version of the standard or regulation that the framework reflects, for example 2023 for ISO/IEC 42001:2023. For the Deeploy AI Control Framework, it is Deeploy's own version.
| Type | Meaning |
|---|
| New version | A framework, or a new version of a framework, was released |
| Added | Controls were added to an existing version |
| Changed | Names, descriptions or other details of existing controls were changed |
| Fixed | A mistake was corrected, such as a typo or a missing risk classification |
| Removed | Controls were removed from an existing version |
| Impact | Meaning |
|---|
| No action needed | Wording, names or other details changed. Your use cases and their progress are unaffected. |
| Applicability changed | The use cases a control applies to changed, for example because a risk classification was added. New use cases are affected right away. Existing use cases are updated the next time their risk classification or role is saved. |
| Stage changed | A control moved to a different lifecycle stage. |
| Checks changed | Checks of a control were removed. The progress of the control in your use cases can change, and documentation that was linked to a removed check is unlinked. The documentation itself is kept. |
| Control added, Control removed | A control was added to or removed from a framework. Timing is the same as for Applicability changed. |
EU AI Act
| Date | Version | Type | Change | Impact | Release |
|---|
| 19-02-2026 | 2024/1689 | New version | EU AI Act control framework released | – | 1.58 |
ISO/IEC 42001
| Date | Version | Type | Change | Impact | Release |
|---|
| 08-09-2025 | 2023 | New version | ISO/IEC 42001 control framework released | – | 1.52 |
AIUC-1
| Date | Version | Type | Change | Impact | Release |
|---|
| 22-06-2026 | October 2025 | Fixed | Controls A005, A006 and A007 now belong to the Development stage, so they show in the use case control list as intended | Stage changed | 1.62 |
| 19-02-2026 | October 2025 | Fixed | Corrected typos in the names of controls D004 and E005 | No action needed | 1.58 |
| 28-01-2026 | October 2025 | New version | AIUC-1 control framework released | – | 1.57 |
NIST AI RMF
| Date | Version | Type | Change | Impact | Release |
|---|
| 28-01-2026 | 1.0 | New version | NIST AI RMF control framework released | – | 1.57 |
Deeploy AI Control Framework
| Date | Version | Type | Change | Impact | Release |
|---|
| 19-02-2026 | 1.0 | Changed | Renamed from "Responsible AI" to "Deeploy AI Control Framework" | No action needed | 1.58 |
| 11-07-2025 | 1.0 | New version | Control framework released as "Responsible AI" | – | 1.50 |