Skip to content
This repository was archived by the owner on Jun 30, 2026. It is now read-only.
Merged
Show file tree
Hide file tree
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions docs/deployment/breaking-changes.md
Original file line number Diff line number Diff line change
Expand Up @@ -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

<a id="octi-oaev-compatibility"></a>

#### 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
Expand Down
Original file line number Diff line number Diff line change
@@ -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**.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually it's starting from OCTI 7.0 you need OpenAEV 2.2.0
but with an OCTI < 7.0 you can use openaev 2.2.0 or even the 2.1.9

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, I made the changes

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • don't use OCTI acronym in documention or product itself -> OpenCTI
  • there is no OpenCTI 7.0 :) you can just say OpenCTI v7

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Another point: I hear in discussions that we would like to restore backwards compatibility (new OAEV with old OCTI). I would use a wording that specifically addresses the breakage with OAEV 2.2.0, so removing mentions that suggest a continuity of the breakage in further OAEV versions.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done


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.
1 change: 1 addition & 0 deletions mkdocs.yml
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down
4 changes: 2 additions & 2 deletions overrides/main.html
Original file line number Diff line number Diff line change
Expand Up @@ -8,8 +8,8 @@
{% endblock %}

{% block announce %}
Breaking Changes in OpenAEV 2.1
<a href="{{ '/2.1.X/deployment/breaking-changes/2.1.0-encrypting-password/' }}">
Breaking Changes in OpenAEV 2.2
<a href="{{ '/2.1.X/deployment/breaking-changes/2.2.0-opencti-security-coverage/' }}">
<strong>Click here to go to the migration guide.</strong>
</a>
{% endblock %}