From 61a2fbe75eed0edecd8203cd7465363343e9ee60 Mon Sep 17 00:00:00 2001 From: RomualdLemesle Date: Tue, 24 Feb 2026 16:46:17 +0100 Subject: [PATCH 1/5] [docs] chore(breaking-changes): add 2.2.0 breaking changes --- docs/deployment/breaking-changes.md | 16 ++++++++++++++++ .../2.2.0-opencti-security-coverage.md | 13 +++++++++++++ mkdocs.yml | 1 + 3 files changed, 30 insertions(+) create mode 100644 docs/deployment/breaking-changes/2.2.0-opencti-security-coverage.md diff --git a/docs/deployment/breaking-changes.md b/docs/deployment/breaking-changes.md index 47086ba9..34c65859 100644 --- a/docs/deployment/breaking-changes.md +++ b/docs/deployment/breaking-changes.md @@ -13,6 +13,22 @@ This table regroups all the breaking changes introduced, with the corresponding | [OpenAEV encryption of secret](#openaev-encryption) | - | 2.1.0 | | [OpenAEV renaming](#openaev-renaming) | 1.18.20 | 2.0.0 | +## OpenAEV 2.2.0 + +### Introduction + + + +#### Scenario Generation from OpenCTI Security Coverage + +Starting from OpenAEV 2.2.0, the interconnection between OCTI and OAEV is only supported with **OCTI 7.0**. + +Previous versions of OCTI are no longer compatible due to API and interconnection changes introduced in OCTI 7.0. + +Please make sure to upgrade OCTI before or at the same time as OpenAEV to avoid service disruption. + +For more details, see [this migration guide](breaking-changes/2.2.0-opencti-security-coverage.md) + ## OpenAEV 2.1.0 ### Introduction diff --git a/docs/deployment/breaking-changes/2.2.0-opencti-security-coverage.md b/docs/deployment/breaking-changes/2.2.0-opencti-security-coverage.md new file mode 100644 index 00000000..bd17eb97 --- /dev/null +++ b/docs/deployment/breaking-changes/2.2.0-opencti-security-coverage.md @@ -0,0 +1,13 @@ +# Scenario Generation from OpenCTI Security Coverage + +!!! info "" + + * **Introduced in**: `OpenAEV 2.2.0` + +## Description of changes + +Starting from **OpenAEV 2.2.0**, the interconnection between **OCTI** and **OpenAEV** is only supported with **OCTI 7.0**. + +Due to API and interconnection changes introduced in OCTI 7.0, previous versions of OCTI are no longer compatible with OpenAEV 2.2.0 and above. + +If you upgrade OpenAEV to version 2.2.0 or later while running an older version of OCTI, the interconnection will not function properly. \ No newline at end of file diff --git a/mkdocs.yml b/mkdocs.yml index 579624d7..f4fa6f80 100644 --- a/mkdocs.yml +++ b/mkdocs.yml @@ -138,6 +138,7 @@ nav: - Migration guides: - OpenAEV renaming: deployment/breaking-changes/2.0.0-openaev-renaming.md - OpenAEV encryption: deployment/breaking-changes/2.1.0-encrypting-password.md + - Scenario Generation from OpenCTI Security Coverage: deployment/breaking-changes/2.2.0-opencti-security-coverage.md - User Guide: - Getting started: usage/getting-started.md - Foundations: From d0ab77d6d2ad57ae5d898e6afb3850bca5752fca Mon Sep 17 00:00:00 2001 From: RomualdLemesle Date: Tue, 24 Feb 2026 16:58:40 +0100 Subject: [PATCH 2/5] [docs] chore(breaking-changes): add 2.2.0 breaking changes --- overrides/main.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/overrides/main.html b/overrides/main.html index cd225043..04c9c945 100644 --- a/overrides/main.html +++ b/overrides/main.html @@ -8,8 +8,8 @@ {% endblock %} {% block announce %} -Breaking Changes in OpenAEV 2.1 - +Breaking Changes in OpenAEV 2.2 + Click here to go to the migration guide. {% endblock %} \ No newline at end of file From 86dc882b6dbafdab5f23a55ee9029b0e02dd31ea Mon Sep 17 00:00:00 2001 From: RomualdLemesle Date: Tue, 24 Feb 2026 18:33:27 +0100 Subject: [PATCH 3/5] [docs] chore(breaking-changes): add 2.2.0 breaking changes --- docs/deployment/breaking-changes.md | 6 +++--- .../breaking-changes/2.2.0-opencti-security-coverage.md | 6 +++--- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/deployment/breaking-changes.md b/docs/deployment/breaking-changes.md index 34c65859..00148922 100644 --- a/docs/deployment/breaking-changes.md +++ b/docs/deployment/breaking-changes.md @@ -21,11 +21,11 @@ This table regroups all the breaking changes introduced, with the corresponding #### Scenario Generation from OpenCTI Security Coverage -Starting from OpenAEV 2.2.0, the interconnection between OCTI and OAEV is only supported with **OCTI 7.0**. +Starting from OpenAEV 2.2.0, the interconnection between OpenCTI and OpenAEV is only supported with **OpenCTI V7**. -Previous versions of OCTI are no longer compatible due to API and interconnection changes introduced in OCTI 7.0. +Previous versions of OpenCTI are no longer compatible due to API and interconnection changes introduced in OpenCTI V7. -Please make sure to upgrade OCTI before or at the same time as OpenAEV to avoid service disruption. +Please make sure to upgrade OpenCTI before or at the same time as OpenAEV to avoid service disruption. For more details, see [this migration guide](breaking-changes/2.2.0-opencti-security-coverage.md) diff --git a/docs/deployment/breaking-changes/2.2.0-opencti-security-coverage.md b/docs/deployment/breaking-changes/2.2.0-opencti-security-coverage.md index bd17eb97..023a617f 100644 --- a/docs/deployment/breaking-changes/2.2.0-opencti-security-coverage.md +++ b/docs/deployment/breaking-changes/2.2.0-opencti-security-coverage.md @@ -6,8 +6,8 @@ ## Description of changes -Starting from **OpenAEV 2.2.0**, the interconnection between **OCTI** and **OpenAEV** is only supported with **OCTI 7.0**. +Starting from **OpenAEV 2.2.0**, the interconnection between **OpenCTI** and **OpenAEV** is only supported with **OpenCTI V7**. -Due to API and interconnection changes introduced in OCTI 7.0, previous versions of OCTI are no longer compatible with OpenAEV 2.2.0 and above. +Due to API and interconnection changes introduced in OpenCTI V7, previous versions of OpenCTI are no longer compatible with OpenAEV 2.2.0 and above. -If you upgrade OpenAEV to version 2.2.0 or later while running an older version of OCTI, the interconnection will not function properly. \ No newline at end of file +If you upgrade OpenAEV to version 2.2.0 or later while running an older version of OpenCTI, the interconnection will not function properly. \ No newline at end of file From 1e2e6272912593a8ca769255c83b0ce6cfb9b594 Mon Sep 17 00:00:00 2001 From: RomualdLemesle Date: Wed, 25 Feb 2026 08:55:03 +0100 Subject: [PATCH 4/5] [docs] chore(breaking-changes): add 2.2.0 breaking changes --- docs/deployment/breaking-changes.md | 39 ++++++++++++------- .../2.2.0-opencti-security-coverage.md | 12 ++++-- 2 files changed, 35 insertions(+), 16 deletions(-) diff --git a/docs/deployment/breaking-changes.md b/docs/deployment/breaking-changes.md index 00148922..5755092b 100644 --- a/docs/deployment/breaking-changes.md +++ b/docs/deployment/breaking-changes.md @@ -6,12 +6,14 @@ Please follow the migration guides if you need to upgrade your platform. ## Breakdown per version -This table regroups all the breaking changes introduced, with the corresponding version in which the change was implemented. +This table regroups all the breaking changes introduced, with the corresponding version in which the change was +implemented. -| Change | Deprecated in | Changed in | -|:--------------------------------------|:--------------|:-----------| -| [OpenAEV encryption of secret](#openaev-encryption) | - | 2.1.0 | -| [OpenAEV renaming](#openaev-renaming) | 1.18.20 | 2.0.0 | +| Change | Deprecated in | Changed in | +|:------------------------------------------------------------|:--------------|:-----------| +| [OpenCTI / OpenAEV compatibility](#octi-oaev-compatibility) | - | 2.2.0 | +| [OpenAEV encryption of secret](#openaev-encryption) | - | 2.1.0 | +| [OpenAEV renaming](#openaev-renaming) | 1.18.20 | 2.0.0 | ## OpenAEV 2.2.0 @@ -21,11 +23,15 @@ This table regroups all the breaking changes introduced, with the corresponding #### Scenario Generation from OpenCTI Security Coverage -Starting from OpenAEV 2.2.0, the interconnection between OpenCTI and OpenAEV is only supported with **OpenCTI V7**. +Starting from OpenAEV 2.2.0, the interconnection between OpenCTI and OpenAEV requires matching major versions: -Previous versions of OpenCTI are no longer compatible due to API and interconnection changes introduced in OpenCTI V7. +- **OpenAEV 2.2.0** and above only works with **OpenCTI V7** +- **OpenCTI V7** only works with **OpenAEV 2.2.0** and above -Please make sure to upgrade OpenCTI before or at the same time as OpenAEV to avoid service disruption. +Previous versions of OpenCTI are no longer compatible with OpenAEV 2.2.0+, and conversely, OpenCTI V7 is not compatible +with earlier versions of OpenAEV. + +Please make sure to upgrade both OpenCTI and OpenAEV simultaneously to avoid service disruption. For more details, see [this migration guide](breaking-changes/2.2.0-opencti-security-coverage.md) @@ -36,7 +42,9 @@ For more details, see [this migration guide](breaking-changes/2.2.0-opencti-secu #### OpenAEV encryption -With the introduction of the OpenAEV catalog, built-in connectors now store their configuration in the database. To ensure security, secrets and passwords within these configurations must be encrypted. This requires two new mandatory properties to be configured. +With the introduction of the OpenAEV catalog, built-in connectors now store their configuration in the database. To +ensure security, secrets and passwords within these configurations must be encrypted. This requires two new mandatory +properties to be configured. For more details, see [this migration guide](breaking-changes/2.1.0-encrypting-password.md) @@ -45,14 +53,19 @@ For more details, see [this migration guide](breaking-changes/2.1.0-encrypting-p ### Deprecation + #### OpenAEV renaming -Following the evolution of scope in OpenBAS (Open Breach & Attack Simulation), it was decided to rename the project to OpenAEV (Open Adversarial Exposure Validation). +Following the evolution of scope in OpenBAS (Open Breach & Attack Simulation), it was decided to rename the project to +OpenAEV (Open Adversarial Exposure Validation). -This platform allows you to entirely create custom attack scenarios to emulate on endpoints. You can even create your own automated tabletop crisis simulation. +This platform allows you to entirely create custom attack scenarios to emulate on endpoints. You can even create your +own automated tabletop crisis simulation. -All those changes require manual modifications to upgrade from previous versions of OpenBAS, even if a lot have been automated. +All those changes require manual modifications to upgrade from previous versions of OpenBAS, even if a lot have been +automated. -Take note that the first startup can be longer, all modifications have to be applied, and it can take a bit longer than usual. +Take note that the first startup can be longer, all modifications have to be applied, and it can take a bit longer than +usual. For more details, see [this migration guide](breaking-changes/2.0.0-openaev-renaming.md) \ No newline at end of file diff --git a/docs/deployment/breaking-changes/2.2.0-opencti-security-coverage.md b/docs/deployment/breaking-changes/2.2.0-opencti-security-coverage.md index 023a617f..47062a88 100644 --- a/docs/deployment/breaking-changes/2.2.0-opencti-security-coverage.md +++ b/docs/deployment/breaking-changes/2.2.0-opencti-security-coverage.md @@ -6,8 +6,14 @@ ## Description of changes -Starting from **OpenAEV 2.2.0**, the interconnection between **OpenCTI** and **OpenAEV** is only supported with **OpenCTI V7**. +Starting from **OpenAEV 2.2.0**, the interconnection between **OpenCTI** and **OpenAEV** requires matching major +versions: -Due to API and interconnection changes introduced in OpenCTI V7, previous versions of OpenCTI are no longer compatible with OpenAEV 2.2.0 and above. +- **OpenAEV 2.2.0** and above only works with **OpenCTI V7** +- **OpenCTI V7** only works with **OpenAEV 2.2.0** and above -If you upgrade OpenAEV to version 2.2.0 or later while running an older version of OpenCTI, the interconnection will not function properly. \ No newline at end of file +Due to API and interconnection changes introduced in OpenCTI V7, previous versions of OpenCTI are no longer compatible +with OpenAEV 2.2.0+, and conversely, OpenCTI V7 is not compatible with earlier versions of OpenAEV. + +If you upgrade one platform without upgrading the other, the interconnection will not function properly. Both platforms +must be upgraded simultaneously. From 5ff4717723f576c46c9c1fd52aa4a0ea96199fb4 Mon Sep 17 00:00:00 2001 From: RomualdLemesle Date: Mon, 2 Mar 2026 09:01:53 +0100 Subject: [PATCH 5/5] [docs] chore(breaking-changes): add 2.2.0 breaking changes --- docs/deployment/breaking-changes.md | 16 +++++++++------ .../2.2.0-opencti-security-coverage.md | 20 ++++++++++++------- overrides/main.html | 2 +- 3 files changed, 24 insertions(+), 14 deletions(-) diff --git a/docs/deployment/breaking-changes.md b/docs/deployment/breaking-changes.md index 5755092b..4cae4837 100644 --- a/docs/deployment/breaking-changes.md +++ b/docs/deployment/breaking-changes.md @@ -23,15 +23,19 @@ implemented. #### Scenario Generation from OpenCTI Security Coverage -Starting from OpenAEV 2.2.0, the interconnection between OpenCTI and OpenAEV requires matching major versions: +In **OpenAEV 2.2.0**, the interconnection between OpenCTI and OpenAEV requires matching major versions: -- **OpenAEV 2.2.0** and above only works with **OpenCTI V7** -- **OpenCTI V7** only works with **OpenAEV 2.2.0** and above +- **OpenAEV 2.2.0** only works with **OpenCTI V7** +- **OpenCTI V7** only works with **OpenAEV 2.2.0** -Previous versions of OpenCTI are no longer compatible with OpenAEV 2.2.0+, and conversely, OpenCTI V7 is not compatible -with earlier versions of OpenAEV. +Due to API and interconnection changes introduced in OpenCTI V7, previous versions of OpenCTI are not compatible +with OpenAEV 2.2.0, and conversely, OpenCTI V7 is not compatible with earlier versions of OpenAEV. -Please make sure to upgrade both OpenCTI and OpenAEV simultaneously to avoid service disruption. +!!! success "Resolved in OpenAEV 2.2.1" + + Backwards compatibility with older OpenCTI versions has been restored starting from **OpenAEV 2.2.1**. This breaking change only affects **OpenAEV 2.2.0**. + +If you are upgrading to OpenAEV 2.2.0, please make sure to upgrade both OpenCTI and OpenAEV simultaneously to avoid service disruption. For more details, see [this migration guide](breaking-changes/2.2.0-opencti-security-coverage.md) diff --git a/docs/deployment/breaking-changes/2.2.0-opencti-security-coverage.md b/docs/deployment/breaking-changes/2.2.0-opencti-security-coverage.md index 47062a88..dbfdd732 100644 --- a/docs/deployment/breaking-changes/2.2.0-opencti-security-coverage.md +++ b/docs/deployment/breaking-changes/2.2.0-opencti-security-coverage.md @@ -3,17 +3,23 @@ !!! info "" * **Introduced in**: `OpenAEV 2.2.0` + * **Resolved in**: `OpenAEV 2.2.1` ## Description of changes -Starting from **OpenAEV 2.2.0**, the interconnection between **OpenCTI** and **OpenAEV** requires matching major +In **OpenAEV 2.2.0**, the interconnection between **OpenCTI** and **OpenAEV** requires matching major versions: -- **OpenAEV 2.2.0** and above only works with **OpenCTI V7** -- **OpenCTI V7** only works with **OpenAEV 2.2.0** and above +- **OpenAEV 2.2.0** only works with **OpenCTI V7** +- **OpenCTI V7** only works with **OpenAEV 2.2.0** -Due to API and interconnection changes introduced in OpenCTI V7, previous versions of OpenCTI are no longer compatible -with OpenAEV 2.2.0+, and conversely, OpenCTI V7 is not compatible with earlier versions of OpenAEV. +Due to API and interconnection changes introduced in OpenCTI V7, previous versions of OpenCTI are not compatible +with OpenAEV 2.2.0, and conversely, OpenCTI V7 is not compatible with earlier versions of OpenAEV. -If you upgrade one platform without upgrading the other, the interconnection will not function properly. Both platforms -must be upgraded simultaneously. +!!! success "Resolved in OpenAEV 2.2.1" + + Backwards compatibility with older OpenCTI versions has been restored starting from **OpenAEV 2.2.1**. This breaking change only affects **OpenAEV 2.2.0**. + +If you upgrade to OpenAEV 2.2.0 without upgrading OpenCTI, the interconnection will not function properly. Both +platforms +must be upgraded simultaneously when moving to OpenAEV 2.2.0. diff --git a/overrides/main.html b/overrides/main.html index 04c9c945..33f9a33d 100644 --- a/overrides/main.html +++ b/overrides/main.html @@ -8,7 +8,7 @@ {% endblock %} {% block announce %} -Breaking Changes in OpenAEV 2.2 +Breaking Changes in OpenAEV 2.2.0 — Resolved in 2.2.1 Click here to go to the migration guide.