Step 2: Investigate and disseminate threat intelligence
The Sekoia CTI team verifies, consolidates, and enriches thousands of reports in STIX 2.1 format, coming from third-party sources. In addition, the team writes and publishes its own research, under the name FLINT (Flash Intelligence). This step shows you how to find and read these reports, cross-reference their indicators with your environment, and disseminate intelligence to your detection and response tools.
Before you begin
- You have completed Step 1: Explore the threat intelligence database.
Find threat reports
Search for reports
- In the navigation menu, select Observe > Intelligence.
- Enter a topic in the search bar (for example, a threat actor name, a malware family, or a sector).
- In the results, open the Objects tab.
- Filter by Type > Report to display only reports.
Find all FLINT reports
Add the filter Source = Sekoia to your search to display only the reports written by Sekoia's own analysts, including all FLINT reports.
Browse all reports
To see all available reports:
- Open the filter panel on the Intelligence page.
- Set Type to Report.
- Sort by Last edited to see the most recent reports first.
Understand FLINT reports
FLINT (Flash Intelligence) reports are rapid-response publications released when a significant threat event occurs, such as a new ransomware campaign or an actively exploited vulnerability. They are designed to be actionable within hours of publication.
A FLINT report typically contains:
| Section | What it provides |
|---|---|
| Executive summary | A plain-language overview of the threat for non-technical stakeholders |
| Technical analysis | Detailed breakdown of the attack chain, tools, and techniques |
| MITRE ATT&CK mapping | The tactics and techniques used by the threat actor |
| Indicators of compromise | File hashes, IP addresses, domains, and other artifacts for detection |
| Recommended actions | Steps to detect, contain, or remediate the threat |
📸 [SCREENSHOT SUGGESTION: A FLINT report detail page showing the executive summary section, MITRE ATT&CK mapping, and a list of indicators of compromise. | ALT TEXT: FLINT report page with executive summary, MITRE mapping, and IOC list.]
Act on report indicators
When a FLINT report includes indicators of compromise, you can cross-reference them with your Sekoia Defend environment.
If you have Sekoia Defend, the CTI-based detection rule SEKOIA Intelligence Feed is active by default. This rule automatically triggers alerts in Defend when a valid Sekoia Intelligence indicator appears in your event stream. You do not need to manually import indicators from reports.
To check whether any indicator from a report has already appeared in your environment:
- Copy an IP address, domain, or file hash from the report.
- Paste it into the search bar on the Intelligence page.
- Switch to the Observables tab to see if it is known.
- Navigate to Investigate > Events and search for the value in your event history.
Disseminate intelligence to your tools
Beyond Sekoia Defend, you can operationalize Sekoia Intelligence in your own detection and response stack. There are three main ways to do this.
| Method | When to use it |
|---|---|
| Native connector | For technologies with a dedicated Sekoia connector (SIEM, SOAR, firewall). Always prefer this option when available: native connectors support dynamic updates and revocation, and follow Sekoia's STIX taxonomy correctly. |
| TAXII 2.1 connector | For technologies that natively support ingesting STIX 2.1 data through the TAXII 2.1 protocol. |
| API | For custom consumption needs, with the ability to run precise, segmented queries against the database. See the Intelligence API reference. To consume the full feed reliably over time, including revoked objects, build your integration following the API consumption guide. |
Model Context Protocol (MCP)
Sekoia is also developing an MCP-based way to consume Intelligence. This capability is still in progress. Check the changelog for updates.
Set up a feed for your firewall
A feed is a filtered, personalized subset of the Intelligence database that contains only the content you select.
Sekoia Intelligence customers commonly use feeds to create dynamic blocklists for their firewalls. Because these blocklists only support network artifacts, a dedicated feed limited to network indicators is the most efficient way to build them.
To create the feed:
- In the navigation menu, select Observe > Feeds.
- Click + New Feed.
- Enter a name for the feed (for example,
Firewall blocklist). - Set filters based on your firewall's requirements, for example: object type is Indicator, indicator type is IPv4.
- Optionally, filter to include only indicators from Sekoia sources (C2 tracker, honeypots, etc.).
- Save the feed.
Your feed appears in the Feeds section and updates automatically as new matching content is published. The feed has an API URL that your firewall can use to fetch its indicator list.
Feeds support API and TAXII consumption
A feed lets you build a filtered subset of the Intelligence database for consumption through the API or TAXII 2.1, independently of the dissemination method you use for your main detection stack.
Receive notifications for new reports
To be notified whenever a new report matching your criteria is published:
- Navigate to Settings > Notifications.
- Click + New notification rule.
- Set the trigger to A report is available.
- Add conditions to match your feed criteria (for example, sector, TLP level, or specific threat names).
- Select your delivery channel (in-app, email, Slack, or Teams).
- Save the rule.
You now receive an alert each time Sekoia publishes a relevant new report.
See: Create a notification for the full procedure.
Related links
- Quick start: Intelligence: Return to the overview of the Intelligence quick start.
- Data model: Full reference on STIX objects, observables, confidence, and reliability.
- Create a notification: Full procedure for setting up notification rules.
- Glossary: Definitions of FLINT, IOC, TLP, indicator, and feed.