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.
Update dependency source-map to v0.7.6 by @renovate[bot] in https://github.com/OpenCTI-Platform/opencti/pull/12768
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.8.5...6.8.6
Your coding agent can read these notes before it upgrades. Set up the MCP server →
[frontend] enhance catalog UI (#12652) by @esrevi in https://github.com/OpenCTI-Platform/opencti/pull/12686
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.8.4...6.8.5
[backend] add initial score on vulnerabilities updates function (#12544) by @ValentinBouzinFiligran in https://github.com/OpenCTI-Platform/opencti/pul…
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.8.3...6.8.4
[frontend] connector instance name (#12572) by @esrevi in https://github.com/OpenCTI-Platform/opencti/pull/12608
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.8.2...6.8.3
[frontend] Fix default dashboard access warning (#11556) by @MTorbay-Filigran in https://github.com/OpenCTI-Platform/opencti/pull/12554
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.8.1...6.8.2
[backend] add entity type verification by @aHenryJard in https://github.com/OpenCTI-Platform/opencti/pull/12502
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.8.0...6.8.1
The vulnerability and software models have been enhanced with additional attributes, specifically “first seen active” for Vulnerability and “product”…
Dear community, we're excited to announce the launch of OpenCTI 6.8.0! 🥳
This release focuses on solving key pain points and unlocking new use cases:
🌟 Priority Intelligence Requirements (PIR) (EE)
We are thrilled to introduce the first implementation of PIR (Priority Intelligence Requirement), a powerful feature that enables users to concentrate only on the threats that matter most to them. This enhancement is designed to help users navigate and prioritize among the vast data within the platform more effectively.
With PIR, users can define the specific criteria such as their organization's industry, locations they operate in, or any sectors and regions they wish to monitor. By setting these criteria, the platform will automatically flag relevant threats with an associated relevance score and highlight priority reports to review. This initial version focuses on helping you identify threats relevant to your organization. Future releases will enable you to operationalize PIR-identified threats in your daily workflows. We welcome your feedback on how to make this most valuable for you.
⚙️ Connector Catalog and Manager (EE)
We are excited to introduce the connector catalog and manager, a feature designed to streamline the deployment and configuration of connectors directly from the user interface.
To achieve this, we've added a connector catalog in the platform's ingestion section, listing connectors currently available for deployment through the interface. This catalog initially features a first selection of "Verified" connectors, with plans to expand the collection over time. From this catalog, users have now the possibility to view details, deploy, and configure these connectors directly within the interface.
We've also enhanced the connector view with new management capabilities. Users can now easily start and stop “managed connectors” and access their logs directly, significantly improving troubleshooting efficiency.
For on-premise deployments, this feature requires adding a new component called "xtm-composer" to the OpenCTI technology stack. This component connects your OpenCTI platform to major container orchestration systems and handles the deployment and lifecycle management of your connectors. More info on: https://github.com/FiligranHQ/xtm-composer
🤖 Chatbot/AI assistant (EE)
You have a CTI question? Ask Ariane!
We are launching the first iteration of Ariane, our brand new Agentic AI assistant, an interface that will change the way users interact with Cyber Threat Intelligence! Ariane is designed to understand complex questions related to the CTI and will leverage all the structured knowledge stored in your platform and also all the OpenCTI documentation.
With this initial release, users will have the ability to ask questions to their OpenCTI platform in natural language! Thanks to Ariane, you don’t need to know the arcane of STIX and OpenCTI to get answers anymore! It greatly lower the barrier of entry for new user and also reduce the time to create reports from structured CTI. Future iterations will further enhance its capability to deliver even deeper insights and will allow to take action on retrieve Intel, like creating a Objects or using features of the platform.
Mind that it is a Preview feature. Usage is limited at the moment. Try it and, if you want more, just reach out to us and we’ll work together on the next step!
If you’re curious on what’s happening under the hood, this feature leverages a dedicated set of tools bundled in an MCP server, publicly available here https://github.com/FiligranHQ/xtm-mcp. The main challenge to tackle was being able to translate a natural language question into a query in graphQL, the technology running the OpenCTI database. Because this is not something easy, we decided to share this capabilities through the standard Model Context Protocol, so that the largest number of OpenCTI users can keep on their AI journey.
💡 Import AI document (EE)
This release features significant improvements to our entity extraction service, accessible through our AI Import Document connector. The service now recognizes a broader range of entities (Organization, Sector, Channel, Tool, Individual, Region). Beyond this expanded recognition capability, the service can now identify and establish relationships (Uses, Targets, Located-at, Exploits, Originates-from) between detected entities.
👤 User management (CE and EE)
The user management part has been enhanced with three new capabilities that improve administrative efficiency:
🛡️ Data Quality & Security Enhancements (CE and EE)
As part of our ongoing commitment to data excellence and security, we're pleased to introduce several enhancements designed to strengthen data quality, improve reliability, and reinforce the protection of your information across our platform.
🎨 UI & UX improvements (CE)
We are aware that the UI & UX of the platform can sometimes be difficult to grasp. We are working towards improving this part.
🔄 Some other improvements have also been provided:
:opencti: XTM HUB: One click deploy (CE)
During the 6.8, XTM hub has released the ability to enroll your platform onto XTM hub. From an added value perspective from OpenCTI, this means that you can also use the newly deployed feature “One Click Deploy”, to easily deploy Dashboard & CSV feeds directly from the Hub.
Directly browse, from your OpenCTI platform the service you need on XTM Hub and within one click, get it into your OpenCTI platform!
🔗 Connectors & Integrations (CE)
Regarding connectors and integrations, this milestone brought several new connectors.
[backend] Simplify version get (#12287) by @richard-julien in https://github.com/OpenCTI-Platform/opencti/pull/12365
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.7.19...6.7.20
[backend/frontend] refactor: use new query parameter namings by @Kroustille in https://github.com/OpenCTI-Platform/opencti/pull/12244
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.7.18...6.7.19
[frontend] New shared Organisations drawer (#11246) by @delemaf in https://github.com/OpenCTI-Platform/opencti/pull/11653
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.7.17...6.7.18
[frontend] Fix issue with dissemination list EE icon (#12148) by @SarahBocognano in https://github.com/OpenCTI-Platform/opencti/pull/12184
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.7.16...6.7.17
Update dependency filigran-icon to v0.18.1 by @renovate[bot] in https://github.com/OpenCTI-Platform/opencti/pull/11691
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.7.15...6.7.16
[backend] fix provisioning numbers (#11668) by @JeremyCloarec in https://github.com/OpenCTI-Platform/opencti/pull/11981
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.7.14...6.7.15
[frontend] fix delete stix ref relationship (#11631) by @delemaf in https://github.com/OpenCTI-Platform/opencti/pull/12086
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.7.13...6.7.14
[frontend] feat: use hub platform token during 1 click deploy by @Kroustille in https://github.com/OpenCTI-Platform/opencti/pull/12020
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.7.12...6.7.13
[frontend] fix several hover layout in Techniques by @CelineSebe in https://github.com/OpenCTI-Platform/opencti/pull/11960
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.7.11...6.7.12
[frontend] chip in list default style (#11830) by @Archidoit in https://github.com/OpenCTI-Platform/opencti/pull/11959
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.7.10...6.7.11
backendVulnerabilities: support "_" & "-" in CVSS values by @maelv-filigran in https://github.com/OpenCTI-Platform/opencti/pull/11799
/Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.7.9...6.7.10
[frontend] add attributes in widget column selection for Vulnerabilities and Organizations (#11546) by @Archidoit in https://github.com/OpenCTI-Platfo…
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.7.8...6.7.9
[frontend] fix missing name for target based-on relationships (#11600) by @marieflorescontact in https://github.com/OpenCTI-Platform/opencti/pull/1165
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.7.7...6.7.8
[frontend] prevent backdrop interaction when filter popover is open (#11594) by @maelv-filigran in https://github.com/OpenCTI-Platform/opencti/pull/11
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.7.6...6.7.7
Introduce fields product on software and first_seen_active on vulnerability by @SamuelHassine in https://github.com/OpenCTI-Platform/opencti/pull/1170…
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.7.5...6.7.6
[frontend] Fix workspace duplication dialog closing unexpectedly on internal clicks (#11010) by @maelv-filigran in https://github.com/OpenCTI-Platform
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.7.4...6.7.5
[frontend/backend] fintel template variable name checker should allow - and _ (#11392) by @Archidoit in https://github.com/OpenCTI-Platform/opencti/pu
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.7.3...6.7.4
[backend] Add check in identifier for potential deduplication by @SarahBocognano in https://github.com/OpenCTI-Platform/opencti/pull/11555
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.7.2...6.7.3
[backend] Fix missing neighbours when adding to container (#11478) by @marieflorescontact in https://github.com/OpenCTI-Platform/opencti/pull/11500
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.7.1...6.7.2
[backend] Compute totals to have less counter updates on changes (#11251) by @aHenryJard in https://github.com/OpenCTI-Platform/opencti/pull/11161
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.7.0...6.7.1
Vulnerability Management & Data model
Dear community, we're excited to announce the launch of OpenCTI 6.7.0! 🥳
This release focuses on solving key pain points and unlocking new use cases:
🔔 Notifications Spamming (CE)
Notifications have been improved to avoid spamming users. Starting from 6.7, all platforms will have a buffer enabled by default for all notifications coming from OpenCTI.
Practically, if a single edit matching a live trigger is made on an entity, notification for this single change will remain real time. However, if multiple edits matching a live trigger are made on a single entity which would result in multiple notifications, only a single one will be send (To be clear, you will receive one notification per trigger). By default, the timer is set to 60 seconds.
This behavior will affect all notifications type (email, in-app, webhook) and will be enabled by default for all platforms (behavior set at affecting platform level, therefore affecting all users of the platform).
You can both disable this feature or change the timer duration, through configuration parameters PUBLISHER_MANAGER__ENABLE_BUFFERING and PUBLISHER_MANAGER__BUFFERING_SECONDS. See documentation
💾 Saved Filters & Dynamic filtering (CE)
We are also enhancing our filtering capabilities with the introduction of Saved Filters. Users can create filters tailored to their specific needs and save them for future use. These filters can be quickly accessed, removing the need to re-enter search criteria for frequent queries. Furthermore, users have the flexibility to update their saved filters as their analysis requirements change.
Dynamic filtering is also a new addition to our release: the concept of dynamic filtering is the same than the pre-queries in dashboards. It aims to identify a subset of entities/relations matching your dynamic filtering & then apply the rest of the filter on the data found through this dynamic filtering. On relationship screen, two filters Dynamic From & Dynamic To allow you to filter on each side of the relation, to get more precise results. At entity level, In regards of (dynamic) will let you be more specific in your “in regards of filters”, by applying additional filters (and not only filtering on the specific entity). Therefore, you will be able to perform queries such as “list all victims of malwares having the type ransomware”.
🖥️ UI & UX Improvements (CE)
We are aware that the UI & UX of the platform can sometimes be difficult to grasp. We are working towards improving this part. This is why we have made several changes to enhance accessibility and overall user experience. The change include:
We have also revamped the "Data/Import" view to better organize resources. Now, all uploaded files, workbenches, and drafts are centralized in one place for enhanced accessibility and simplified organization. As a result, the "Draft" menu has been relocated to this view.
🛡️Security Posture & MITRE ATTACK Sub Techniques (CE)
Gaining insight into your cyber defense coverage in relation to the techniques used by threats is essential for identifying detection gaps and improving your security posture. To support this goal, we have introduced a new entity "Security Platform" which allows you to manually map the techniques your detection tools are intended to cover (should-cover relationship) and compare them with actual threat techniques. To facilitate this process, the MITRE ATT&CK Matrix view has been enhanced, enabling easy comparison between the techniques theoretically covered by your security tools and those used by threats. By leveraging this feature, organizations can achieve improved alignment of their security strategies with real-world threats, facilitating proactive defense measures and strategic improvements over time.
In addition to this new capability, we have enhanced the "MITRE ATT&CK Matrix" view by adding support for sub-techniques. It is now easy to see the number of sub-techniques used by a threat via a badge. Additionally, you can expand a parent technique to display its associated sub-techniques, providing greater visibility into the details of the tactics employed by threats.
🎨 Fintel PDF Export Branding Customization (EE)
To ensure that report exports reflect your corporate identity, we have introduced new customization options for Fintel PDF exports, providing a more personalized and tailored presentation. Beginning with version 6.7.0, you can configure a Fintel design by uploading your company logo and choosing custom colors to be applied throughout your Fintel PDF reports. This update guarantees that your exported documents are in line with your organization's branding, maintaining a consistent visual identity.
🔐 Reset Password (CE)
We are excited to introduce the new Reset Password feature in this release. This enhancement addresses a key requirement from our user community for better password management and improved security. Users can now initiate a password reset process directly from the login page. Upon request, a secure code will be sent to the registered email address, allowing users to set a new password.
🚀 JSON Mapper/Feed (CE)
In addition to our CSV Feed/Mapper capability, we are pleased to announce the new JSON Feed/Mapper feature, which enables seamless ingestion of JSON-formatted files and feeds. With this enhancement, you can effortlessly import, parse, and map both simple and complex JSON data structures, offering greater flexibility for integrating diverse cyber threat intelligence sources.
We’ve also improved the scheduling of our built-in Feed ingesters. You can now configure a specific fetching interval for each ingester (JSON, RSS, CSV). This enhancement allows you to better comply with external data source constraints and optimize your data ingestion processes.
📓 Apply Case Templates via Playbooks (EE)
Across all 6.X.X releases, we have always tried to improve our case management capabilities based on various feedback we received from the community. In this regard, we are glad to announce that, from 6.7, within playbooks, when wrapping elements into a Case container, you can now also apply a case template directly from the playbook. This should help you improve your case management, by enabling more automation, based for instance on the cases types filters in playbooks introduced last release.
🧰 Vulnerability Management & Data model (CE)
Our vulnerability model now includes comprehensive data and metrics for CVSSV2 and CVSSV4, alongside the full attributes for CVSS V3, enhancing our assessment capabilities. We have also introduced a native capability to parse CVSS vector strings, which automatically populates respective metrics directly within our platform. This feature enhances efficiency by allowing users to input a vector string and instantly see the corresponding metrics filled in.
Finally, we've also introduced a "remediates" relationship to link software versions to specific vulnerabilities they fix, providing clearer remediation pathways. These updates deliver more detailed and actionable insights, helping users manage vulnerabilities more effectively.
In 6.7, we also extended our data model:
🔧 Background tasks processed by workers (CE)
We have enhanced our background task management system to improve performance and prevent platform lock-ups during extensive background tasks. The task execution logic has been moved to asynchronous workers, allowing for better distribution of processing across different workers. Tasks are now provisioned into worker queues and executed by these workers. The tasks view has been updated to reflect these changes, allowing you to monitor the provisioning step followed by the execution step.
🔗 Connectors & Integrations
Regarding connectors and integrations, this milestone brought several new connectors and integrations.
We would like to extend our sincere thanks to our partners and community for their valuable contributions to our connector ecosystem. Thanks to your efforts, new connectors such as Dogesec CTI Butler, Dogesec Vulmatch, Dogesec Stixify, Dogesec Obstracts and a new connector for MalwareBazaar have been added. Additionally, several existing connectors including Sekoia, Intel471, Group-IB, IBM XTI, GreyNoize Feed, MISP Feed, TheHive, and VirusTotal enrichment have been significantly improved. Your collaborations are instrumental in driving our platform forward and providing even greater possibilities to all our users. Thank you all!
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.6.18...6.7.0
Update quay.io/keycloak/keycloak Docker tag to v26.2.5 by @renovate in https://github.com/OpenCTI-Platform/opencti/pull/11289
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.6.17...6.6.18
This release deactivate the migration introduced with OpenCTI 6.6.16, cleaning up activity logs in the database. Please see the 6.6.16 release note fo
This release deactivate the migration introduced with OpenCTI 6.6.16, cleaning up activity logs in the database. Please see the 6.6.16 release note for more details.
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.6.16...6.6.17
Release 6.6.16 includes a migration script that cleans up the database following resolution of #10777. Purpose of the migration is to add missing grou
Release 6.6.16 includes a migration script that cleans up the database following resolution of #10777. Purpose of the migration is to add missing group information on activity logs that were incorrectly generated, and make possible searching and filtering activity logs consistently with respect to the group criteria. The impacted activity logs are those generated by the platform between 6.6.0 and 6.6.16. On large platforms with millions of impacted activity records, this migration can take several hours.
We disabled this migration in OpenCTI 6.6.17.
For those who do not need to repair the activity logs and prefer skipping this heavy migration, you can update your platform from 6.6.15 (or a prior release) to 6.6.17 directly. For those who wants to repair their database this way, you might want to update your platform to 6.6.16 and then to the latest version.
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.6.15...6.6.16
[frontend] Add Italian language support (#10434) by @rpfontana in https://github.com/OpenCTI-Platform/opencti/pull/11000
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.6.14...6.6.15
[CI] Feature branch on staging by @efaure in https://github.com/OpenCTI-Platform/opencti/pull/11108
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.6.13...6.6.14
[frontend] Stix core object history lines (#10965) by @Archidoit in https://github.com/OpenCTI-Platform/opencti/pull/11042
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.6.12...6.6.13
[frontend] Add a description to countries (#10087) by @SarahBocognano in https://github.com/OpenCTI-Platform/opencti/pull/10959
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.6.11...6.6.12
[frontend] Fix validation errors on changes in creation forms by @CelineSebe in https://github.com/OpenCTI-Platform/opencti/pull/10728
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.6.10...6.6.11
[frontend] Fix Search in Add locations of Threat Actor Individuals (#10794) by @Archidoit in https://github.com/OpenCTI-Platform/opencti/pull/10887
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.6.9...6.6.10
Update redis Docker tag to v7.4.3 by @renovate in https://github.com/OpenCTI-Platform/opencti/pull/10844
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.6.8...6.6.9
[backend] fix cron playbook node filter saving (#9646) by @JeremyCloarec in https://github.com/OpenCTI-Platform/opencti/pull/10810
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.6.7...6.6.8
[backend] remove status update if status is not in entity statuses configuration (#9071) by @JeremyCloarec in https://github.com/OpenCTI-Platform/open
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.6.6...6.6.7
[frontend/backend] enable adding relationships as representation entity targets (#9395) by @JeremyCloarec in https://github.com/OpenCTI-Platform/openc
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.6.5...6.6.6
[frontend] Avoid URI filters repercussion in Knowledge screens (#8511) by @Archidoit in https://github.com/OpenCTI-Platform/opencti/pull/9066
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.6.4...6.6.5
[frontend] Fix init zoom on graphs (#10580) by @lndrtrbn in https://github.com/OpenCTI-Platform/opencti/pull/10595
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.6.3...6.6.4
[frontend] Fix bulk search result panel (#10518) by @SouadHadjiat in https://github.com/OpenCTI-Platform/opencti/pull/10532
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.6.2...6.6.3
[frontend] Trying to get vite running faster (#9869) by @aHenryJard in https://github.com/OpenCTI-Platform/opencti/pull/9799
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.6.1...6.6.2
#### Bug Fixes: - #10094 Incomplete search for Observable User Account entities Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.6.0...6.6.1
Given that the DRAFT feature has been released, Workbench will be deprecated within approximatively 6 months from this release. As a result, we strong…
Dear community, we're excited to announce the launch of OpenCTI 6.6.0! 🥳
This release focuses on solving key pain points and unlocking new use cases:
OpenCTI offers lots of functionalities & various ways to see and collect information. However, sometimes, especially for new users, understand where and how to find the information can be a struggle.
We hope that 6.6 will relieve you from this pain, thanks to the introduction of our new AI functionality: the Natural Language Query powered by Arianne AI 💫. This Entreprise Edition feature allows you, from the top search bar, to ask questions to the platform! Your question will be translated into a set of filters and the corresponding results will be displayed as usual, letting you narrow down your search if needed 🔍.
This capability will fully rely on our filters and solely provide results about entities ⚠️ : as a result, any questions that would lead to filters that do not exists or a combination of filter not available in the app won’t provide you the expected results. In addition, the scope of the questions are restricted to entities. For more information regarding this functionality, please go to the dedicated documentation page https://docs.opencti.io/latest/usage/ask-ai/#assistance-for-finding-specific-entities-natural-language-query.
We are eager to hear your feedback for this functionality which is a first step towards making Arianne AI a real assistant in your daily life on OpenCTI.
Finding intelligence first requires ingesting it into the platform. We have worked hard to be able to revamp our import workflow and introduce two major features: a full rework of the import from files workflow ↖️ and the Draft feature 🎨.
First regarding the import workflow: you are now able to import multiple files at once 💡, and create a single draft out of it. As a result, this should make you win quite some time while gathering all information in a single place for validation purpose.
The second feature that comes along the import is the Draft 🎨. Draft workspaces aims to replace workbenches on the long run.
Basically, Drafts will provide the same capabilities than a workbench: the ability to view what has been extracted from the file & validate it before import. But that is not all: all the functionalities available in the application will also be available within a Draft workspace! For this first release, you will be able to enrich in Draft, apply bulk operation (mass create, edit…)💥. Switching your platform to a Draft “mode” will allow you to still browse your data, manipulate it, without impacting the main database.
You will also be able to convert your existing workbenches to Drafts.
As a result, the new import workflow coupled with the Draft functionality will enable you to better control your ingestion from files, ensuring that only high quality data is ingested for real in your OpenCTI instance.
We are keen to get feedback on this functionality that has required quite some work, therefore, feel free to try out & let us know what you think. More information on: https://docs.opencti.io/latest/usage/draftWorkspaces
We have spent some time to improve features around Case Management. We have introduced two new filters: the “@Me” filter 🤝 & the ability to filter on relative date range ⏱️. This way, you will be able to create query like “show me all cases created within the last week” ⏱️. This should improve your operational efficiency.
OpenCTI’s complex and multi-layered ACL allows organizations to implement their own data segregation, each teams having their scope of responsibility, with need-to-know based sharing. This kind of process have impact on collaboration efficiency, and it is not rare that a teamA works on a correlated case handled by teamB without knowing it. Now in OpenCTI, with the Request Access feature (EE) 🧐 teamA is able to request access to the corelated case and thus, with respect to need-to-know basis, collaborate further with teams working already on it. Basically, in the context of a platform configured to segregate data per Organizations, if an entity, having a marking accessible to user exists in the platform, but not shared to the user’s organization, upon manual creation of entity, the user will have the ability to request access to this entity. It will result in a creation of an RFI that only a specific group of user pertaining to the correct organization could approve or reject, providing full control over data to users of the platform. Try it out!
We have also improved the playbooks to be able to filter on any container sub type 🎊 (incident response type, report type, request for information type…). Therefore, you will be able to automate with more granularity the automation of your cases. All together, these filtering capabilities should help you improve the operational efficiency of your teams working on cases.
Filtering has not only be improved in the context of containers, but globally within the application. All entities having a knowledge view can now benefit from a new view, the All view 🔥, which gathers all entities and all relations without any filters at all. This is a known pain point that has been raised since a while, since you were not able to easily see all linked entity with the one you’re looking at. This view will be used to also improve the current diamond model view 💎, since the various views of the diamond model will now redirect to a view All, with some predefined filters matching your view!
Some of your cases, container or even investigations can be huge and difficult to handle by our current front-end graph engine. This is one of the reason we have heavily reworked our graphs within the platform 📈, to ensure we are able to load large graphs. To do so, we have introduced a pagination when loading your graph, avoiding your platform to crash when you attempt to load a large graph. On the top of this, we have also clarified the select & search behavior to find more easily the information you are looking for. Dedicated documentation is available here : https://docs.opencti.io/latest/usage/pivoting/?h=pivoting. This technical rework opens the path to further improvements in our graph with objective to help users perform in-graph intelligence analysis and correlation.
A few other improvements have also been provided:
Regarding connectors and integrations, this milestone brought several new connectors and integrations like:
Last but not least, we are excited to introduce our new AI-powered import-document 💫 connector. This connector allows Enterprise Edition organizations to feed information from document to OpenCTI, with more extraction capabilities than regular Import Document connector. Go to the readme of the connector to understand how to use it and its scope: https://github.com/OpenCTI-Platform/connectors/tree/master/internal-import-file/import-document-ai
⚠️ Deprecation notes:
Given that the DRAFT feature has been released, Workbench will be deprecated within approximatively 6 months from this release. As a result, we strongly encourage you to have a look at the draft functionality, to try it out, and already highlight us any issue or feature existing in workbench that you do not find in Drafts.
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.5.11...6.6.0
chore(deps): update dependency vite to v5.4.15 [security] by @renovate in https://github.com/OpenCTI-Platform/opencti/pull/10390
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.5.10...6.5.11
[frontend] large spacing on vulnerability details (#10118) by @ValentinBouzinFiligran in https://github.com/OpenCTI-Platform/opencti/pull/10262
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.5.9...6.5.10
[frontend] add marking icon in definiton column (#10074) by @marieflorescontact in https://github.com/OpenCTI-Platform/opencti/pull/10144
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.5.8...6.5.9
*No changelog for this release.*
No changelog for this release.
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.5.7...6.5.8
[frontend] feat: Hide XTM Hub CTA button if platform_xtmhub_url variable is empty by @jbanety in https://github.com/OpenCTI-Platform/opencti/pull/1022
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.5.6...6.5.7
[frontend] vulnerability detail grid updated (#10118) by @ValentinBouzinFiligran in https://github.com/OpenCTI-Platform/opencti/pull/10158
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.5.5...6.5.6
[frontend] Bad margin/padding on some pages with an information section (#10053) by @SarahBocognano in https://github.com/OpenCTI-Platform/opencti/pul
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.5.4...6.5.5
[frontend] Only accessible markings visible in filters (#10006) by @Archidoit in https://github.com/OpenCTI-Platform/opencti/pull/10010
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.5.3...6.5.4
[backend/frontend] Fix generation scenario from threat and victime entities (#9987) by @savacano28 in https://github.com/OpenCTI-Platform/opencti/pull
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.5.2...6.5.3
Update dependency dompurify to v3.2.4 by @renovate in https://github.com/OpenCTI-Platform/opencti/pull/9850
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.5.1...6.5.2
[frontend] add 'search' filter operator translation (#9772) by @Archidoit in https://github.com/OpenCTI-Platform/opencti/pull/9802
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.5.0...6.5.1
…simulations from OpenCTI. This includes a deprecation, detailed below.
Dear community, we're excited to announce the launch of OpenCTI 6.5.0! 🥳
This release focuses on solving key pain points and unlocking new use cases:
ℹ️ Enterprise Edition Activation Changes
[!NOTE] As you know, in June 2023 we introduced an “Enterprise Edition” of the platform. As we explained at the time, this was in no way a reneging on our commitment to open source software, which has been part of our DNA since the very first day of our adventure. We are convinced that we have honored this promise perfectly, continuing to invest heavily in the features of the community version and innovating for all our communities.
Access to the Enterprise Edition, subject to a special license and annual subscription, has remained for almost two years based on the good faith of the platform's users, with acceptance of the license requiring a simple checkbox in the platform settings.
To promote transparency and fair use of our products, OpenCTI 6.5.0 introduces a license key system to control activation of the Enterprise Edition. All Filigran customers and non-governmental charity organizations using EE in accordance with the terms of the license have already received their license key(s).
As a consequence, upgrading a platform with EE activated and without a valid license key will result in the full de-activation of all EE features. Of course, for organizations wishing to access the associated features for testing and development purposes, trial license keys can be generated automatically and independently from our website. Please, don't hesitate to reach out to us if you have any question or concern about this new license key system.
Analysts spend significant time working on incidents and reports to identify threats and create knowledge that improves their organization's security posture.
However, transforming this information into standardized, easily disseminated finished intelligence documents often proves challenging.
This is why we introduced the ability to create your own finished intelligence template 📜 (Enterprise Edition). From the container's customization page, you can now define templates that use variables of your container and the entities and relations present in your container. These predefined templates will reuse the intelligence contained in your container. Your analysts can simply generate finished intelligence from these templates to initialize documents pre-populated with relevant data. This significantly reduces the time needed to produce any kind of reports.
Better yet, these templates can be imported and exported 💡, allowing you to reuse them across different platforms!
In addition, we've added the capability to manage dissemination lists & leverage them to send PDF documents via email (Enterprise Edition) 📨. Once administrators define email distribution lists, analysts can use them to send Finished Intelligence documents directly to their dissemination circles. This gives non-OpenCTI users easy access to analyst-produced documents.
In certain circumstances, intelligence access needs to be more restricted—for instance, during critical incidents or when handling sensitive threat reports. To address this, we've added the ability to restrict access to a container with our authorized member mechanism 🔒(Enterprise Edition). Even with shared containers, enabling access restriction limits visibility to specifically authorized users, groups, or organizations. These authorized members receive only the access rights you grant them (view, edit, manage), helping you maintain data confidentiality.
To ensure restricted data remains manageable if an entity manager leaves your organization, administrators can access a restriction management panel 🔓 to remove restrictions on entities when needed.
Minimizing false positives is essential for improving the accuracy and effectiveness of threat detection. To support this, we've introduced exclusion lists ⛔ in OpenCTI. This feature lets you create exclusion lists to prevent specific IOCs, such as internal IPs or trusted domains, from being ingested into the platform. By preventing the ingestion of these non-malicious IOCs, you ensure they are not propagated to your external detection solutions (ex: SIEM), reducing noise and enhancing detection accuracy.
AI should enhance analysts' daily work, which is why we've revamped our AI module ✨ (Enterprise Edition). Now available across all platform entities, it supports analysts in their daily tasks. From any entity, such as a threat, analysts can quickly view latest activity, get summaries from recent reports, and see activity logs—putting useful information at their fingertips!
Understanding and presenting data effectively is crucial in CTI. This is why we have worked on the following features.
Our OpenBAS :openbas: integration has been redesigned to support choosing the correct architecture when running simulations from OpenCTI. This includes a deprecation, detailed below.
In terms of data ingestion, OpenCTI now provides the capability to expose TAXII 2.1 data collections for pushing STIX-formatted data. Available under Data/Ingestion, the TAXII Push ingester enables users and external systems to import STIX 2.1 objects into OpenCTI through an exposed TAXII collection, ensuring full compliance with the 'Add objects' section of the TAXII 2.1 specification.
We’ve also updated and integrated a new GraphQL playground to enhance your development experience by making it easier to test and interact with our GraphQL API 😎.
Finally, we've improved performance for large dataset operations ⚡ through two backend enhancements: improved worker thread pool and relocated lock mechanism to a separate process. This means faster background task processing and more efficient operations on shared entities, resulting in fewer errors.
Regarding connectors and integrations, this milestone brought several new connectors and integrations like:
But also to enhance some connectors :
We deeply want to thank our Partner & Community for their contributions:
Finally, we have made efforts to expand the availability of our Docker containers. In addition to being hosted on Docker Hub, all OpenCTI containers are now also accessible via [GitHub Container Registry](https://github.com/orgs/OpenCTI-Platform/packages).
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.
All the details about what has been released for which repo is available here:
⚠️ Deprecation
Deprecation Notice: GenerationScenario Mutations in OpenCTI - OpenBAS
The following three mutations related to GenerationScenario have been deprecated due to changes in their signature and response format:
Key Changes in new version : + WithInjectPlaceholders
New Signature Object: SimulationConfig
New Response Object: GenerationResponse
For more information about the deprecation duration, please refer to our documentation: https://docs.opencti.io/latest/deployment/breaking-changes/.
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.4.11...6.5.0
[backend] Fix reindex error on deleting old objects (#9270) by @SouadHadjiat in https://github.com/OpenCTI-Platform/opencti/pull/9742
Full Changelog: https://github.com/OpenCTI-Platform/opencti/compare/6.4.10...6.4.11
One column per quarter.