NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
PyPI
Python API client for OpenCTI.
Latest stable
7.261109.3
Last release 13 days ago
09 Nov 2026
Ships on a steady schedule
a new release about every 1 weeks
Most releases are documented
notes for 53 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
7 years old
473 releases · first in 2019
Drag across the ruler to compare, or tap a release to open it.
[frontend] In Observable / Indicators composed with this observable view, fix the css(#9279) by @Gwendoline-FAVRE-FELIX in https://github.com/OpenCTI-
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.4.9...6.4.10
Your coding agent can read these notes before it upgrades. Set up the MCP server →
[frontend] refacto how we get apex chart context (#9299) by @lndrtrbn in https://github.com/OpenCTI-Platform/opencti/pull/9633
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.4.8...6.4.9
[backend] keep increasing back pressure delay if queue size keeps increasing (#9358) by @JeremyCloarec in https://github.com/OpenCTI-Platform/opencti/
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.4.7...6.4.8
[frontend] display creators in Intrusion set list (#9534) by @Archidoit in https://github.com/OpenCTI-Platform/opencti/pull/9535
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.4.6...6.4.7
Update dependency react-apexcharts to v1.7.0 by @renovate in https://github.com/OpenCTI-Platform/opencti/pull/9352
Unknown in workbenchTask/Report/Grouping/Malware Analysis name are Unknown in knowledge related entitiesNetwork-Traffic name in workbench observables list (#9506) by @delemaf in https://github.com/OpenCTI-Platform/opencti/pull/9507Task/Report/Grouping/Malware Analysis in knowledge > related entities (#9497) by @delemaf in https://github.com/OpenCTI-Platform/opencti/pull/9498Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.4.5...6.4.6
[backend] fix version of path-to-regexp for CVE-2024-52798 by @labo-flg in https://github.com/OpenCTI-Platform/opencti/pull/9286
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.4.4...6.4.5
Update dependency amqplib to v0.10.5 by @renovate in https://github.com/OpenCTI-Platform/opencti/pull/9180
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.4.3...6.4.4
[backend] fix possible undefined fileMarkings (#9149) by @JeremyCloarec in https://github.com/OpenCTI-Platform/opencti/pull/9178
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.4.2...6.4.3
[backend] Domain observable with hyphen/dash is incorrectly rejected V2 (#8927) by @SarahBocognano in https://github.com/OpenCTI-Platform/opencti/pull
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.4.1...6.4.2
[frontend] Members ordering in Group edition form (#8984) by @Archidoit in https://github.com/OpenCTI-Platform/opencti/pull/9061
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.4.0...6.4.1
Vulnerability management, by developing additional integrations
Dear community, we're excited to announce the launch of OpenCTI 6.4! 🥳
This release has been mainly focused on solving the following pain points & unlocking the below use cases:
If our platform is flexible, sometimes this flexibility can be harmful when it some new users to the platforms perform some actions which can have a negative on their experience, such as remove the Enterprise Edition, changing the platform organisation, updating some built-in roles & groups.
This is the reason why we introduced the concept of Danger Zone 🚸.
**From the moment you will upgrade, certain area of the platform will be protected. This means you will not be able to edit them without having a new specific role capability. For more information regarding this feature, please go to the dedicated documentation
Quick and efficient incident response is essential for many organizations, yet managing participant assignments and case updates can often be time-consuming, slowing down response times.
To streamline incident management, we’ve introduced direct in-UI options for assigning participants and assignees, removing the need to open the modification panel. Additionally, we now support bulk operations for updating fields like creator, assignee, priority, severity, and type🖊️ directly from the list view.
These enhancements enable faster, more flexible incident management, giving teams the ability to quickly assign resources and update cases at scale.
To complement on this topic, one great feature added this release is also the ability to enroll a specific entity within the playbook 🤖: starting from 6.4, you can create a playbook with the first step being “Available for manual enrollment / trigger”. By creating this step without any filter & the rest of your workflow, you can now, when navigating to a container, “enroll this entity in a playbook” to have an automation running on this specific entity. This will unlock lots of use cases, for instance to apply specific measures to a particular entity that you need to follow.
Users frequently need to work with knowledge graphs to manipulate information within containers. However, adding entities to an established knowledge graph has been a challenge, as forces were automatically reapplied, disrupting the graph's layout and usability. So as creating a large number of relationships with a single entity led to problems of timeout.
In this release, we’ve refined the knowledge graph experience to support smoother interactions. Now, if you disable forces on your graph, it will maintain its layout when new entities are added 📈, preserving your custom configurations.
Additionally, with valuable input from the community, we’ve enhanced relationship management within reports. Users can now select all relationships linked to a node or choose to isolate either parent or child relationships 💡—simplifying bulk actions, such as removing relationships from a container.
Investigation graphs have also been reworked to improved the representation of file objects (observable).
Knowledge ingestion through CSV files offers flexibility, but handling custom formats can be challenging. Users need efficient ways to create mappers and manage conditional data.
To enhance CSV ingestion, we’ve introduced two key improvements to CSV mappers.
Firstly, we’ve added a duplication feature for CSV mappers (and feeds) 📁across both ingestion and data sharing, simplifying the mapper creation process.
Secondly, the new Conditional Mapping 🧪functionality allows users to map columns based on specific conditions—particularly useful when a single column contains multiple entity types. For instance, users can configure the mapper to recognize whether a row is an IP address or URL based on values in a separate column, streamlining entity classification.
Ingestion have also been improved with the ability to map a confidence level information on our score notion (x_opencti_score) when ingesting Indicators/Observables from a TAXII Feed.
Few releases back we have started our work towards unlocking some vulnerability management capabilities within the app.
This is why we have now introduced the Tenable Vulnerability Management connector. Thanks to this connector, you can now monitor your assets using our system entity within OpenCTI & get some corresponding vulnerabilities.
Additionally, systems now have a knowledge view 🪟 to see their related vulnerabilities & a new relationship type “system has vulnerability” 🔗 has been introduced too. Thanks to the work already done to add EPSS, KEV & connectors already built, in addition to these fields being supported in the playbooks, vulnerability management within OpenCTI becomes doable to a certain extent within the platform 🔥
Connectors are essential for data ingestion, yet diagnosing errors within connectors can be challenging and time-consuming. Clear error insights are crucial for efficient troubleshooting and to maintain data flow continuity.
To simplify error resolution, we’ve enhanced the error logging for connectors 💬. Now, within the error tab, users can view errors categorized under Critical, Warning, and All, allowing for immediate prioritization. Each error entry includes an improved, human-readable explanation along with a unique error code. This code links directly to documentation that provides specific troubleshooting steps, helping users quickly identify and address issues.
When it comes to troubleshooting, you also need to understand which are the users who have taken a given action, in order to be able to trace back & understand what did happen. Our logging have been improve thanks to the introduction of a filter on the “system” user. 👥
Outside of these use cases, we have tackled some additional various issues.
In addition to Tenable connectors addition, two new enrichment connectors have also been added:
We have also made a number of improvements to the Microsoft Sentinel, Tanium and Harfanglab connectors. The export of indicators and the import of incidents are now separated into two different connectors (stream & external-import).
On a finish note, we would like to thank you for your contributions 🙏 to our product, that helps making our product better: guillaumededrie, stefan1anuby, Bonsai8863, animedbz16, daimoyo007, cert-orangecyberdefense, polakovicp, DNRRomero, stefanbulof, annoyingapt, uTomasAnderson, bradchiapetta, brett-fitz, akhanafeer, mmolenda, initstring, Darkheir, WolfBytnner, Mathieu4141, DinkoReversingLabs, basvanschaik, curiouspython1.
Of course, a huge thank you to all for your contributions 🥇
We hope this release will please you! Feel free to drop us a note about anything. We’re always happy to get feedback about our product usage, whether it’s to hear that everything works perfectly or to get some improvement ideas to.
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.3.13...6.4.0
#### Bug Fixes: - #9136 ImportDoc connector Will not Automatically Create a Workbench When Uploading a PDF on the Data page of an Observable and Artif
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.3.13...6.3.14
#### Bug Fixes: - #9042 Organization mapping is not working with Microsoft when "." is present in path - #9026 PDF viewer is broken everywhere Full Ch
[frontend] Improve error message notification in the UI (#8923) by @richard-julien in https://github.com/OpenCTI-Platform/opencti/pull/8924
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.3.11...6.3.12
[frontend] Fix data tables interactions between selected elements and filters (#8571) by @lndrtrbn in https://github.com/OpenCTI-Platform/opencti/pull
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.3.10...6.3.11
Permissions from External Auth Server Not Mapped to OpenCTI Platform Groups When Logging in via loginFromProvider by @savannah030 in https://github.co
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.3.9...6.3.10
[frontend] UI fix scrollbar useless in custom dashboard (#8282) by @CelineSebe in https://github.com/OpenCTI-Platform/opencti/pull/8823
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.3.8...6.3.9
[frontend] Fix enrichment button (#8825) by @Kedae in https://github.com/OpenCTI-Platform/opencti/pull/8828
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.3.7...6.3.8
[frontend] Bad icons replaced in connector overview(#8225) by @CelineSebe in https://github.com/OpenCTI-Platform/opencti/pull/8669
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.3.6...6.3.7
[frontend + backend] added vulnerabilitties tab and 'has' relationship by @stefan1anuby in https://github.com/OpenCTI-Platform/opencti/pull/8458
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.3.5...6.3.6
Update docker.elastic.co/kibana/kibana Docker tag to v8.15.2 by @renovate in https://github.com/OpenCTI-Platform/opencti/pull/8543
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.3.4...6.3.5
Bump rollup from 4.21.3 to 4.22.4 in /opencti-platform/opencti-graphql by @dependabot in https://github.com/OpenCTI-Platform/opencti/pull/8461
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.3.3...6.3.4
[frontend] Fix ctrl+click on DataTable (#8394) by @Kedae in https://github.com/OpenCTI-Platform/opencti/pull/8402
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.3.1...6.3.3
Nothing published for this version
#### Bug Fixes: - #8395 In some very rare cases when a bundle is too large, sending to the queue can end up with "Blocked connection timeout expired."
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.3.0...6.3.1
manipulate data and initiating work toward vulnerability management.
Dear community, we're excited to announce the launch of OpenCTI 6.3! 🥳
This released has been focused on solving well known pains 🎯 :
Clarity & control over the ingestion process is a must. Hence the introduction of our feature Integrated feeds Ingestion 🧠. More and more of you are ingesting data via “integrated” feeds (TAXII, RSS, CSV), and we've worked to give you greater visibility over the data ingestion flow by representing these feeds in the form of a dedicated connector and by allocating dedicated RabbitMQ queues per ingestion configurations in place of common queues (see our depreciation announcements).
Thanks to this enhancement, you'll be able to identify bottlenecks more quickly and gain real-time insights into your data ingestion flow. 💡
Following up on this pain of providing more control to admins over the ingestion, we have introduced a new capability: bypass custom mandatory fields.
The problem is that your connectors providing you data do no always have a a specific field that you want your analyst to provide, which results in failing the creation of entity. ❌ As a result, thanks to this new capability, you will be able to enforce this custom mandatory attribute only for specific groups of users (your analysts), while allowing others (your connectors) to be able to create data without a specific field. 🔥
As mentioned in introduction, we focused on usability. This is why we introduced a new feature: bulk creation 🥇
Together, these features are designed to save you time and enhance your productivity, enabling you to focus on more critical tasks.
Improving app usability means better identification of the data that matters to you 💡
Every organization has unique data needs, even within different entities of the same company. To meet this, we introduce the new Custom Overview per Entity Type feature.
This allows users to customize each entity’s layout, selecting key information "blocks" to prioritize and adjust their size. It makes it easier to quickly spot and focus on critical data.
Usability also comes from having similar functionalities in similar screens across the app.
First of all, we have introduced List views for Threat Actors, Intrusion Sets, Campaigns & Malware, on the top of the existing card view 🪪. This will tremendously help the management of these entities without the need to go in data/entities to manage them.
Massive operations have also been added to all Arsenal entities (Malware, Channels, Tools, Vulnerability), Narratives and Attack Patterns! In this way, the consistency of operations across the application is greatly enhanced.
Last but not least, you will notice one last update that has been heavily worked in order to improve our application usability: New data tables 🎉
When upgrading to our new version, you’ll notice that data table look different: we have upgraded them. As a result, you’ll notice that:
As some of you may be aware, we would like to make easier the vulnerability management process in OpenCTI.
The first step to achieve this goal was to extend our Vulnerability model to support EPSS and CISA KEV attributes. Support of these two information were highly requested by the community🔥. Regarding EPSS, an enrichment connector to fill the data has been created too, see below.
Having these fields was not enough, we also added the ability to use them (like other vulnerability fields) in playbook components to help you build your own vulnerability decision tree 🪄.
While files and workbenches are essential, they can contribute to performance issues over time, since documents are piling up in the platform. ❌
Retention Rules for Files and Workbenches: We’ve added configurable retention rules, which are not set by default but can be easily customized. For example, you can implement a one-year policy to automatically delete any file or workbench created over a year ago. This helps prevent outdated data from accumulating and improves overall platform performance. 💯
Administrators have also been heard with an additional feature, or rather a UX improvement. To ease management of dashboard we have also introduce a new tab in the dashboard menu, to be able to view only the public dashboards as list without needing to enter in each dashboard to view the corresponding dashboards.
In terms of integrations, lots of effort has been put to deliver new connectors & improvements of existing connectors.
We already announced it on slack, but during this release, we delivered a new Splunk app 🔥, aiming to:
With the OpenCTI Add-on for Splunk, you can leverage comprehensive threat information, improving your ability to detect and respond to security incidents more effectively. More info can be found on : https://splunkbase.splunk.com/app/7485.
To provide more support to our community, we completely refactored the Qradar connector to become an official Filigran support connector. This means that we will be able to provide support on this connector if a bug arise. The refactor has also fixed some known bugs, which are listed in the below list of issues.
Being open source also means ensuring that everybody has the capacity to contribute to our codebase. However, in the past, our readmes & guidelines to contribute in our connector repository were not up to date. We’ve made some effort to update it so that all the documentation is up to date, allowing everybody to bring their own contribution more easily 💪!
As mentioned earlier, we have worked towards helping analysts to perform vulnerability management with OpenCTI. To cater this need, we built an enrichment connector to provide values for EPSS 🤘This connector integrates with the organisation “FIRST” API, aiming to retrieve EPSS values about a specific vulnerability. This enrichment connector is of course playbook compatible 🚀
Some connectors have also been reworked (namely Sekoia, Crowdstrike, Mandiant, AlienVault, Recorded Future, CISA KEV) to support our new scheduling and auto-pausing feature that will pause your connector when its queue gets full. You’ll see in these connectors new variables "duration_period" & "queue_threshold" that you need to define to enable these features. More details can be found in the respective connector pages.
We also improved the Mandiant connector by providing an option to import aliases of malwares & improve campaigns import. Campaigns import improvement provide more details regarding TTPs (labels, relation with intrusion sets, start & stop time & addition of description). In essence, we’ve made sure that we import as much data as we can.
To list them all, here are all the new connectors delivered in the milestone: Jira, Infloblox, Cisco SMA, Group IB, Cofense. The detailed list of connectors & improvement is available here: ****https://github.com/OpenCTI-Platform/connectors/releases?page=1
On a finish note, we would like to thank you for your contributions 🙏 to our product, that helps making our product better: shmztk, Bonsai8863, Fhwang0926, ParamConstructor, VerboseCat, WolfByttner, brett-fitz, mmolenda, Mathieu4141, annoyingapt, DNRRomero, DinkoReversingLabs, pietrocapece, sari3l, bradchiappetta, debelyoo, uTomasAnderson, leitosama, XGREENi3, sudesh0sudesh, cert-orangecyberdefense, cmandich, obideuce, sda06407, Obdam, piolug93, daemitus, polakovicp, julienloizelet, khalidelborai, Renizmy, curiouspython1!
Of course, a huge thank you to all for your contributions 🥇
We hope this release will please you! Feel free to drop us a note about anything. We’re always happy to get feedback about our product usage, whether it’s to hear that everything works perfectly or to get some improvement ideas to.
Depreciation announcements
The RabbitMQ “push_sync”, “listen_sync”, “listen_playbook” and “push_playbook” queues are no longer used by our product and will be considered deprecated once empty. These queues will be permanently removed in version 6.6.
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.2.18...6.3.0
#### Bug Fixes: - #8512 [livestream] update and removal are not done anymore on destination Full Changelog: https://github.com/OpenCTI-Platform/openct
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.2.18...6.2.19
#### Bug Fixes: - #8129 User overview light theme hidden entities tiles - #8116 [CSV Mapper] When having error, "Create" button is disabled - #7964 Bu
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.2.17...6.2.18
#### Bug Fixes: - #8205 app.base_path configuration is not working anymore (default empty works fine) - #8011 When a user is administrator of an organ
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.2.16...6.2.17
#### Bug Fixes: - #8182 Order of kill chain phases are lost after dataset is updated - #8150 [Retention policy] Entities are not deleted - #8013 Error
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.2.15...6.2.16
[backend] Fix migration timestamp (#6509) by @lndrtrbn in https://github.com/OpenCTI-Platform/opencti/pull/8112
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.2.14...6.2.15
[backend] Trial for improving import page by @Kedae in https://github.com/OpenCTI-Platform/opencti/pull/8031
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.2.13...6.2.14
[backend/frontend] Fix Kill all session button in the user overview (#7837) by @CelineSebe in https://github.com/OpenCTI-Platform/opencti/pull/7959
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.2.12...6.2.13
[frontend/backend] Add EPSS Support for Vulnerability Entity (#3568) by @ValentinBouzinFiligran in https://github.com/OpenCTI-Platform/opencti/pull/78…
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.2.11...6.2.12
[frontend] Cleaning up unused props by @CelineSebe in https://github.com/OpenCTI-Platform/opencti/pull/7912
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.2.10...6.2.11
Update dependency react-cookie to v7.2.0 by @renovate in https://github.com/OpenCTI-Platform/opencti/pull/7877
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.2.9...6.2.10
[backend] fix impossible deletion of some entities by @JeremyCloarec in https://github.com/OpenCTI-Platform/opencti/pull/7808
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.2.8...6.2.9
[frontend] Narratives Lines views refacto (#6741) by @Gwendoline-FAVRE-FELIX in https://github.com/OpenCTI-Platform/opencti/pull/7608
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.2.7...6.2.8
[frontend] Apply bulk creation on other entities than Channels (#4352) by @lndrtrbn in https://github.com/OpenCTI-Platform/opencti/pull/7711
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.2.6...6.2.7
[frontend/backend] Support of "KEV" field for vulnerability entity (#7390) by @ValentinBouzinFiligran in https://github.com/OpenCTI-Platform/opencti/p…
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.2.5...6.2.6
[backend] Domain name values should be case insensitive (#7311) by @SarahBocognano in https://github.com/OpenCTI-Platform/opencti/pull/7677
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.2.4...6.2.5
[frontend] Modifies autocomplete which causes form visual validation discrepancy by @ParamConstructor in https://github.com/OpenCTI-Platform/opencti/p
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.2.3...6.2.4
[backend] import from date not mandatory in Rss ingester (#7451) by @Archidoit in https://github.com/OpenCTI-Platform/opencti/pull/7592
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.2.2...6.2.3
[frontend] Incorrect space in the data / import section view between breadcrumb and content (#7529) by @SarahBocognano in https://github.com/OpenCTI-P
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.2.1...6.2.2
Update opentelemetry-js monorepo by @renovate in https://github.com/OpenCTI-Platform/opencti/pull/7466
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.2.0...6.2.1
Dear community, we're excited to announce the launch of OpenCTI 6.2! 🥳This update focuses on three main use cases: improving the platform usability to
Dear community, we're excited to announce the launch of OpenCTI 6.2! 🥳This update focuses on three main use cases: improving the platform usability to reduce analyst fatigue, aiding administrators in managing the application, and enhancing customization to cater to your needs.
In Cyber Threat Intelligence, there are a lot of ways to display and analyse characteristics of a threat, phase of attacks, and so on. Among them, the Diamond Model is a well known and useful analytic framework, but one that can be hard to harness and produce. OpenCTI 6.2 introduces an automatically generated Diamond Model for each Threats in the platform and each Incidents! 💎 This new view, accessible in the Knowledge tab of the entity, is based on all the knowle7dge accumulated around it. No manual work is required here and you can focus your precious time on analyzing the subject through the Diamond Model analytical framework! 🧠
Extracting structured knowledge from documents is a tedious and time-consuming task. Therefore, we've moved the content mapping to the content section for logical consistency and have improved the UX to be clearer and simpler to use. It is now available for all containers. 🤩 We've also added an auto-saving of the content, eliminating the need to manually save your work. 💾 Note that this auto-saving is not implemented for files you modify here, at the moment. To further ease the process of mapping each entity within text content, we've introduced automatic mapping! This feature will recognize entities that already exist on your platform. Currently, there is no magic. Mapping suggestion are based on the current capability of the ImportDocument connector (used also when you generate an Analyst Workbench from the import of a file) and there is still noise created. This is our first step towards an AI-assisted (NLP) automatic mapping that will ensure smarter extraction and less noise! 🪄
In OpenCTI 6.2, we've also made it possible to automate the creation of Analyst Workbenches for External Reference coming from a specific source. For example, it can be used to automatically create an Analyst Workbench for Reports coming from an RSS feed, automating the ingestion process while ensuring data correctness. The RSS feed triggers the external ref connector, which triggers the import document, resulting in workbenches created for each new incoming report. 💯
For our Entreprise Edition users, we have also enhanced “Ask AI” functionality: it can now leverage files uploaded from External References! 💡
Talking about ingestion, we've enhanced the CSV feed ingestion with a feature that uses the default value set in your CSV mapper to populate the marking. This simplifies data classification control and ensures that only users with sufficient marking can access data imported from CSV feeds.
On the administrative side, the Role-Based Access Control (RBAC) capabilities have been reworked to allow administrators to manage access in a more granular way. This long awaited feature will help administrators to better control who has access to what. Each menus of the Settings are now linked to a specific Capability and now an administrator can grant management of labels to a user without granting them the ability to change the interface. 🔒 We've also introduced a new "Access security activity" capability that allows to see logs related to security related events. Without this capability, a user can only view events related to modification and access of Knowledge entities.
Some sources provide Reports containing Observables for characterizing potentially malicious events. Based on that, analyst can decide these technical elements are characteristic of an attack and want to send them for further security actions (detection for example). Best practice is to send Indicators, not Observables. With OpenCTI 6.2, it is now possible to easily add Indicators related to the contained Observables when you promote these Observables via massive operations’ toolbar! 🔥
Sharing has also been improved! Now, you can also decide whether relationships created from inference rules should be shared in the TAXII collection when creating a new one. Additionally, 6.2 introduces the ability to use Organization sharing through massive operations directly! Now, you can simply select all entities you want to share with a specific Organization and click on 'share' ! 🥰
In terms of integration, administrators can now clear the queue of a connector if it gets stuck, enhancing performance management.
The Crowdstrike Feed connector has been improved to use FalconPy library when importing Threats, Reports, and also YARA and SNORT rules! Community members brought also a lot of value with the development of connectors for Red Flag Domains (external-import), ShadowServer foundation (external-import) and ReversingLabs (internal-enrichment). The Zerofox connector has also been improved! Thanks a lot! ♥️
We're eager for your feedback on these enhancements!
⚠️ Breaking changes
Since OpenCTI version 6.2 there is an upgrade of
passport-samllibrary that implies that for platform using SAML provider:
- Document signatures are now required by default. Setting
wantAuthenResponseSigned=falsedisables this feature and restores the prior, less secure behavior- Require all assertions be signed; new option
wantAssertionsSignedcan be set to false to enabled the older, less secure behavior.It means that if it’s not already done, you should generate certificates and configure the SAML identity provider in a secure way. Or else in OpenCTI configuration parameters
want_authn_response_signedand/orwant_assertions_signedcan be set to false:
PROVIDERS__SAML__CONFIG__WANT_AUTHN_RESPONSE_SIGNED=falsePROVIDERS__SAML__CONFIG__WANT_ASSERTIONS_SIGNED=falsePlease read the passport-saml detailed changelog for more details.
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.1.13...6.2.0
#### Bug Fixes: - #7486 MIME type in uploaded artifacts is not correct and lead to multiple errors - #7484 In some old instances, we have representati
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.1.12...6.1.13
[frontend] e2e tests on dashbaords - chunk 2 (#6704) by @lndrtrbn in https://github.com/OpenCTI-Platform/opencti/pull/7135
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.1.11...6.1.12
[frontend] Fix file indexing accessing to external file (#6943) by @Kedae in https://github.com/OpenCTI-Platform/opencti/pull/7254
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.1.10...6.1.11
#### Bug Fixes: - #7263 Force disable introspection can prevent correct platform usage Full Changelog: https://github.com/OpenCTI-Platform/opencti/com
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.1.9...6.1.10
> ⚠️ This release introduced an issue which sets the platform in a non viable state, please use 6.1.10 ⚠️
⚠️ This release introduced an issue which sets the platform in a non viable state, please use 6.1.10 ⚠️
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.1.8...6.1.9
[backend] Add keyPrefix for sentinel redis mode by @Kedae in https://github.com/OpenCTI-Platform/opencti/pull/7203
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.1.7...6.1.8
Update docker.elastic.co/elasticsearch/elasticsearch Docker tag to v8.13.4 by @renovate in https://github.com/OpenCTI-Platform/opencti/pull/7177
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.1.6...6.1.7
Update redis Docker tag to v7.2.5 by @renovate in https://github.com/OpenCTI-Platform/opencti/pull/7159
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.1.5...6.1.6
Update dependency @playwright/test to v1.44.1 by @renovate in https://github.com/OpenCTI-Platform/opencti/pull/7071
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.1.4...6.1.5
[backend] remove concurrency in reportDeleteWithElements (#7015) by @JeremyCloarec in https://github.com/OpenCTI-Platform/opencti/pull/7021
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.1.3...6.1.4
[frontend] remove unnecessary abstract types in entity type filter list (#6976) by @Archidoit in https://github.com/OpenCTI-Platform/opencti/pull/6987
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.1.2...6.1.3
[frontend] Fix all filters usage by @Kedae in https://github.com/OpenCTI-Platform/opencti/pull/6971
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.1.1...6.1.2
[frontend] fix several click needed to go to entity (#6804) by @marieflorescontact in https://github.com/OpenCTI-Platform/opencti/pull/6936
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.1.0...6.1.1
…connectors on entities like Intrusion Sets and Vulnerabilities differently. You can also give more control to users over certain entities like Reports…
Dear community, we're delighted to announce the release of OpenCTI 6.1.0 :partying_face:! This milestone materializes our Extended Threat Management suite by integrating OpenCTI with our new Breach and Attack Simulation open-source platform OpenBAS :fire: !! And that’s not all! 6.1 incorporates also a lot of long awaited features:rocket:!
First of all, let's discuss the OpenBAS integration :handshake:. OpenBAS is a platform where you can define series of events (technical or not) to be simulated towards endpoints or players. These simulations help you evaluate your security posture. Evaluating security posture makes more sense when tested against real and relevant threats. Here comes your OpenCTI and all of its carefully triaged, qualified, and crafted CTI! Directly from the Overview of Reports, Cases, and even Threats, you can generate a Breach and Attack simulation, evaluate your security posture, and have results integrated into your threat context. At a glance, you'll know if you are at risk! :exploding_head: We are very excited to bring this to the community and can't wait to receive your feedback on it!
OpenCTI 6.1.0 also brings Public Dashboards :loudspeaker:! Now, you can create snapshots of your custom Dashboards and share them via a permalink, with people who don't have access to your OpenCTI platform. But these snapshots aren't static—they dynamically update as data in OpenCTI changes over time! Because data confidentiality always matters :shushing_face:, users and platform administrators can control which data is shared through Public Dashboards using a maximum marking definition setting.
Now, regarding confidentiality, we've enhanced how marking definitions are handled for files associated with Knowledge entities. You can specify the maximum marking for generating exported file contents and apply markings directly to the files themselves :shield:.
With this milestone, we're thrilled to introduce a long-awaited feature: rollback on deletion! Who hasn't felt the frustration of accidentally deleting the APT28 Intrusion Set from the platform :scream:? I certainly have :wink: ! Mistakes are inevitable, and until now, some deletion actions were not easily reversible. But those days are behind us! Users now have the ability to rollback deletions for up to 7 days, by default. When you delete a Knowledge entity or relation, it's sent to a Trash collector where it can be restored from! So, the next time you accidentally delete APT28 or Cobalt Strike and their countless relationships, fear not—they'll be waiting for you in the trash, ready to be restored :relieved:.
Speaking of rollback, you may have also noticed that a 6.0 minor release introduced rollback functionality for investigations' graphs. Give it a try! Version 6.0 introduced the Max Confidence level feature for users and groups, offering a powerful tool for enhancing Knowledge quality within your platform. If you haven't already, check out the dedicated blog post for more details. OpenCTI 6.1 takes it a step further :rocket:! Now, you can define max confidence level overrides per entity types! This means you can tailor the impact of connectors on entities like Intrusion Sets and Vulnerabilities differently. You can also give more control to users over certain entities like Reports while limiting control over others like Locations and Sectors, for example. Give it a try and let us know what you think about it!
We've dedicated some time to enhance our Assignee system for Cases. Now, when users are assigned to Cases (whether as Assignee or Participant), they'll receive automatic notifications about the assignment and any subsequent changes made to the Case. Additionally, you now have the option to define in your Profile how you prefer to be notified by default for these assignments :briefcase:.
To enhance our ability to address any bugs you encounter on your OpenCTI platform, we're implementing a Support Package generation system. Administrators can now generate an archive containing relevant log files from all nodes, aiding in more precise diagnostics of any situation. Additionally, users now have the capability to copy and paste the stack trace directly when an error occurs in the front-end :hammer_and_wrench:.
On the Integration side, we updated Malpedia and Recorded Future connector to make them Playbook compatible. We also created a Crowdstrike Falcon EDR connector to send IoC from OpenCTI to Falcon. Community members brought also a lot of value over the last minor releases, with the development of connectors for NIST NVD CPE, RST Noise Control, MITRE ATLAS matrix, Malcore and Socprime. Thanks a lot! :hearts:
OpenCTI 6.1 also introduces our telemetry framework. These metrics collection is now mandatory for us to improve platform performances, as current usage implies significantly larger data volumes than before. It is also essential for us to enhance internal workflows and adapt them to community usage patterns. All collected data are anonymous and statistical. You can find detailed information on the collected data and associated usage in the telemetry documentation.
Finally, for those within our community operating in highly confidential environments, we've made a significant improvement to our Python framework to natively support air-gapped architecture. Our CTO, Julien Richard, has authored a dedicated blogpost to assist you with this. Be sure to check it out for detailed guidance :brain:.
:warning: Breaking changes
It is not possible anymore to ingest Objects with a name containing less than 3 characters (space character at the beginning or the end of the string are not included in the count)
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.0.10...6.1.0
One column per quarter.