Skip to content
Knowledge base Updated: January 4, 2026

Threat intelligence in practice — how to build an intelligence program in your organization

How to build a threat intelligence program from scratch? TI levels, data sources, SIEM and SOC integration, plus MISP and OpenCTI tools — a complete guide for teams.

It is the middle of the night. An analyst on duty at the security operations center notices an anomaly in network traffic — one of the workstations is establishing connections to a domain registered just 72 hours ago. Without additional context, this is just another alert in the queue. But if the organization has a functioning threat intelligence program, that same analyst knows within minutes: the domain is linked to the infrastructure of the APT29 group, the technique matches tactic T1071.001 from the MITRE ATT&CK framework (Application Layer Protocol: Web Protocols), and similar indicators of compromise appeared two weeks earlier in the energy sector in Germany. The difference between a response based on intuition and a response based on intelligence is measured in minutes — and in the case of ransomware, those minutes determine the scale of losses.

Threat intelligence is not a product or a subscription to a feed of malicious IP addresses. It is an organizational capability — a process of systematically collecting, analyzing, and operationalizing knowledge about threats in a way that genuinely influences defensive decisions. Building this capability from scratch requires understanding the four levels of threat intelligence, selecting the right sources, integrating with existing tools, and — what is often overlooked — defining measurable objectives. This article walks through each of these stages, from conceptual foundations to specific tools and effectiveness metrics.

What is threat intelligence and how does it differ from ordinary threat monitoring?

Threat intelligence is processed, analyzed, and contextualized knowledge about cyber threats that supports decision-making — both operational and strategic. The key word is “processed”: raw threat data is not threat intelligence. IP addresses pulled from a public feed, unverified domains from a botnet list, or file hashes reported by a single vendor — all of this is raw material that must pass through the intelligence cycle before it becomes actionable information.

Threat monitoring is the continuous observation of the IT environment for signs of malicious activity — SIEM alerts, log anomalies, deviations from behavioral baselines. It is reactive by nature: the system responds to what is already happening or has just occurred. Threat intelligence complements this capability with an anticipatory dimension — it allows an organization to know what to expect before an attack occurs, because it provides context about the motivations, tactics, and targets of specific threat groups.

Technical analysis points to three fundamental differences. First, threat monitoring operates on events, while threat intelligence operates on knowledge — information about who is attacking, how, why, and with what capabilities. Second, monitoring is internally oriented (I am looking at my own logs), while TI has an external orientation (I am observing the threat ecosystem outside my organization). Third, monitoring supports incident response, whereas TI supports both IR and strategic decisions: technology purchases, budget allocation, and audit priorities.

Threat intelligence without an operationalization process remains merely academic analysis. Intelligence value is measured by the ability to change organizational behavior — blocking an indicator, updating a SIEM rule, launching a threat hunt, or changing a security policy.

The intelligence cycle in the context of cybersecurity comprises six phases: planning and direction (defining intelligence requirements), collection (gathering data from sources), processing (normalization, deduplication, translation), analysis (providing context, correlation, inference), dissemination (delivering to the right recipients in the right format), and evaluation and feedback (verifying usefulness). Skipping any of these phases — particularly the first and last — is the most common cause of low TI program effectiveness.

What are the levels of threat intelligence — strategic, tactical, operational, technical?

The MITRE ATT&CK framework classifies attacker behaviors at the level of tactics, techniques, and procedures (TTPs). Similarly, threat intelligence operates at four levels, each serving different recipients and different decision-making purposes. Understanding this hierarchy is a prerequisite for designing an effective program.

Strategic threat intelligence addresses the management level — the board, the CISO, and business directors. Its role is to inform about trends, threats to specific industries, the activity of nation-state APT (Advanced Persistent Threats) groups, and the geopolitical implications for the organization’s cybersecurity. The format is typically narrative reports, briefing decks, and impact analyses — without technical details. Example: a report on the growing activity of state-sponsored ransomware groups targeting critical infrastructure in Eastern Europe, with a recommendation to accelerate the OT network segmentation project. Time horizon: weeks to months.

Tactical threat intelligence serves security architects, SOC managers, and security engineers. It covers information about the tactics, techniques, and procedures (TTPs) of specific threat groups — how they attack, what tools they use, and how they maintain persistence in compromised environments. Tactical data is mapped directly to the MITRE ATT&CK framework, enabling an assessment of whether the organization has detection mechanisms for individual techniques. Time horizon: days to weeks.

Operational threat intelligence supports SOC analysts and incident response (IR) teams. It contains information about specific attacker campaigns — their targets, infrastructure, timing, and tools. It allows an analyst to understand whether an observed alert is part of a broader, targeted campaign directed against similar organizations. Time horizon: hours to days.

Technical threat intelligence is the most granular level — indicators of compromise (IoCs): IP addresses, domains, hashes of malicious files, URLs of C2 (command and control) servers, SSL certificate patterns. This level is directly consumed by security tools: firewalls, IDS/IPS systems, DNS servers, and EDR platforms. Its “shelf life” is the shortest — attacker infrastructure rotates very quickly, and an IoC from a week ago may already be outdated. Time horizon: minutes to hours.

The most common mistake in TI programs: focusing exclusively on technical IoCs while neglecting the tactical and operational levels. IoC-driven defense is a game that attackers win, because they change infrastructure faster than an organization can update its blocklists. TTPs change much more slowly — defense based on tactics is structurally more durable.

An effective TI program must deliver value at all four levels simultaneously, although the proportions depend on the organization’s maturity and risk profile. An organization just building its program should start with the technical level (the fastest operational value) and systematically develop analytical capabilities toward higher levels.

How to build an internal threat intelligence program from scratch?

Building a threat intelligence program from scratch does not begin with choosing tools — it begins with defining intelligence requirements: the specific questions the program is meant to answer. These questions must reflect the organization’s risk profile, its industry, geographic reach, and the value of the assets it protects. Examples of well-formulated intelligence requirements: “Are ransomware groups actively targeting the manufacturing sector in Poland in Q1 2026?”, “What phishing techniques are currently being used against financial companies in the CEE region?”, “Is our IT suppliers’ infrastructure being monitored by known APT groups?”

The first phase of building a program is inventorying existing capabilities. Before any purchasing decisions are made, the following questions must be answered: what logs are already being collected and stored? Is there a SIEM and what detection rules are active? Does the organization use any external feeds (even free ones)? What are the team’s capabilities — does anyone have experience in malware analysis or OSINT? This inventory establishes the starting point and prevents duplicate investments.

The second phase is defining the operating model. Will the program be run entirely in-house, in a hybrid model (an internal team plus an external intelligence-as-a-service provider), or fully outsourced? Each model has its trade-offs in terms of cost, response time, and depth of industry context. Organizations with fewer than 1,000 employees most commonly start with a hybrid model — an internal analyst coordinates data from external sources and integrates TI with the SIEM, while more advanced analyses are commissioned to an external partner.

The third phase is building the operational process. There must be a clearly defined workflow: who collects the data, who analyzes it, who decides on operationalization (e.g., adding an IoC to a blocklist), and who informs the board. Without a documented process, even the most expensive tools will not deliver value — data will be collected but not analyzed, or analyzed but not actioned. A typical TI operational cycle for a mid-market organization: 24 hours from the appearance of a new industry threat to updated SIEM rules and a published internal bulletin for the SOC.

A critical mistake when building a program from scratch: purchasing an expensive TI platform before defining processes. A platform without a process generates data that no one processes. Do the opposite: define the process, build it on free tools (MISP + OTX + VirusTotal Community), and only when the processes are working, consider a commercial extension.

The fourth phase, often overlooked, is building relationships with external communities. Threat intelligence is a field where cross-sector collaboration has enormous value. Joining sector-specific ISACs (Information Sharing and Analysis Centers), CERT groups (Computer Emergency Response Teams) such as CERT Poland, or closed information-sharing groups (e.g., a Slack workspace for the financial sector in the region) provides access to information that no commercial vendor offers: industry context from organizations with an identical risk profile.

What data sources feed an effective TI program?

The threat intelligence source ecosystem is extensive and diverse. The MITRE ATT&CK framework distinguishes several categories of sources that can be grouped by availability, quality, and cost. An effective TI program does not rely on a single source — diversification is a requirement, not an option, because every source has different blind spots.

Open source intelligence (OSINT) is the foundation of any TI program, regardless of budget. It includes public threat reports from vendors such as Mandiant, CrowdStrike, Recorded Future Unit 42, and Microsoft MSTIC — all publicly available at no charge. The OSINT category also includes IoC indicator feed channels: AlienVault OTX (Open Threat Exchange), Abuse.ch (URLhaus, MalwareBazaar, ThreatFox), PhishTank, Shodan in free mode, and VirusTotal Community. The MITRE ATT&CK repository itself is an invaluable source of tactical knowledge.

Commercial feeds and intelligence platforms offer higher data quality, faster updates, and deeper analytical context at the cost of a subscription. Market leaders are Recorded Future, Mandiant Advantage, CrowdStrike Falcon Intelligence, and with AutoFocus integration. The difference between a commercial and a free feed comes down primarily to: speed (commercial feeds update in near real time), context (every IoC is annotated with information about the group, campaign, and confidence level), and a low false positive rate (commercial vendors apply their own validation processes).

Sector-specific and government sources are an often underappreciated pillar of any TI program. CERT Poland (CERT.pl) regularly publishes bulletins on threats directed against Polish organizations, operational activity reports, and indicators of compromise from its own analyses. ENISA (the European Union Agency for Cybersecurity) publishes annual threat landscape reports (ENISA Threat Landscape) and sector-specific analyses. Industry ISACs — for the financial sector (FS-ISAC), energy sector (E-ISAC), and healthcare sector (H-ISAC) — offer access to narrowly focused industry context that has the greatest operational value for members of a given sector.

Internal intelligence sources are an area often overlooked in discussions about TI, yet they have enormous potential. An organization’s own security logs — if properly stored and analyzed — are an intelligence source of the highest contextual value, because they concern that specific organization, its environment, and its attackers. Analysis of historical incidents, attack patterns on honeypots, data from deception technology systems — all of this creates an internal, unique intelligence knowledge base that no external vendor can provide.

Dark web monitoring constitutes a separate category: monitoring cybercriminal forums, underground markets (including those on the dark net), Telegram channels, and Discord servers for mentions of the organization, leaked employee credentials, or offers to sell access to the company’s infrastructure. This is necessary for a full picture of the external attack surface, but requires specialized tools (Flashpoint, Kela, DarkOwl) or a partnership with a provider offering this service.

The source diversification rule: no single feed — even the most expensive commercial one — covers the full spectrum of threats. The optimal source architecture for a mid-market organization is: 2–3 open IoC feeds (OTX + ThreatFox + one sector-specific), 1 commercial intelligence platform (or intelligence-as-a-service), a national CERT, and its own log and honeynet analysis.

How to integrate threat intelligence with SIEM and SOC?

Integrating threat intelligence with a SIEM (Security Information and Event Management) is the critical point at which intelligence data is transformed into operational defensive value. Without effective integration, even the best-analyzed IoCs remain dead data in a PDF report — they do not block attacks, do not generate alerts, and do not reduce detection time.

The basic integration mechanism is TI lookup — the automatic correlation of SIEM events with indicators of compromise loaded into the system. Every log containing an IP address, domain, or file hash is compared in real time against the IoC database. If a match occurs, an alert is generated with a priority dependent on the confidence level and severity of the indicator. Modern SIEMs — Splunk, Microsoft Sentinel, IBM QRadar, LogRhythm, Elastic SIEM — all support native integrations with TI platforms via the STIX/TAXII protocol (Structured Threat Information eXpression / Trusted Automated eXchange of Indicator Information).

The second mechanism is alert enrichment. When the SIEM generates an alert, the TI platform automatically provides context: which APT group the indicator belongs to, what previous campaigns that group has run, what MITRE ATT&CK techniques are associated with it, and what other organizations have been targeted. This context dramatically reduces the SOC analyst’s triage time — from many minutes of manual research to seconds of automatic enrichment. The MITRE ATT&CK framework classifies this type of automation as support for technique T1595 (Active Scanning) and related reconnaissance techniques.

The third mechanism is active blocking — the automatic forwarding of IoCs to network devices (next-generation firewalls, DNS sinkholing, proxies) to block communication with malicious infrastructure. This is the fastest way to operationalize TI, but it requires an IoC validation process prior to blocking — a false positive at the DNS sinkholing level can block access to legitimate services and cause serious operational disruption.

Integration with SOC processes goes beyond technical API connections. It requires an operational change: defining playbooks for TI-enriched alerts, escalation procedures for high-priority matches, and standards for handling new indicators (how quickly after the appearance of a new external report should IoCs be loaded into the SIEM?). In mature SOCs, these procedures are automated through SOAR (Security Orchestration, Automation and Response) platforms: a new external report triggers an automated workflow — parsing, validation, loading into the SIEM, updating detection rules, and notifying analysts.

A TI-to-SOC integration maturity indicator: Mean Time to Detect (MTTD) for attacks using known IoCs should be expressed in minutes, not hours. If an analyst must manually look up every alert in an external database, the integration is not working properly.

What is threat hunting and how does it differ from reactive detection?

Threat hunting (proactive threat hunting) is one of the most commonly misunderstood concepts in security operations. Reactive detection is a response to an alert generated by a system — an analyst responds to what the SIEM, EDR, or NGFW has already detected. Threat hunting assumes the reverse logic: the analyst formulates a hypothesis (“I assume an attacker is already in the network and is using a living-off-the-land technique — i.e., system tools — to avoid detection”) and actively searches for evidence to confirm or refute it in the data, without any prior system alert.

Threat intelligence is the fuel for threat hunting. Hunting hypotheses should not be arbitrary — they should stem from current threat knowledge: a report indicates that the Lazarus group is actively targeting the financial sector using a new lateral movement technique via WMI? That is an immediate hypothesis to verify: do the WMI logs from the past 30 days show any patterns indicating this technique (MITRE ATT&CK T1047)?

The TI-based threat hunting cycle consists of four steps. First: generating a hypothesis based on current intelligence — information about active campaigns, TTPs of observed groups, and new techniques noted by a CERT or commercial vendors. Second: defining the data to analyze — what logs, from what time period, from what systems are needed to verify the hypothesis. Third: active analysis — manual or semi-automated searching of data using advanced queries (SPL in Splunk, KQL in Sentinel, EQL in Elastic). Fourth: documenting the results — regardless of whether the hypothesis was confirmed, the hunting results are valuable: confirmation of a “clean” environment builds a confidence baseline, while confirmation of an attack triggers IR.

Threat hunting requires a different competency profile than classic SOC operations. A Tier 1 SOC analyst responds to alerts according to a playbook. A threat hunter formulates their own hypotheses, can write advanced queries, understands TTPs at a technical level, and can interpret low-level system artifacts (Windows registry artifacts, prefetch files, Windows Security log events 4624, 4625, 4768). The MITRE ATT&CK framework is a working tool — the hunter must be able to translate a technique description into the specific artifacts they are looking for in the logs.

The results of threat hunting have bidirectional value: operational (detecting a threat or confirming the absence of compromise) and intelligence-based. When hunting uncovers new artifacts, techniques, or indicators not present in external feeds, they become internal intelligence indicators — elements of proprietary intelligence that enrich the TI program with unique data from the organization’s own environment.

How to measure the effectiveness of a threat intelligence program?

Measuring the effectiveness of a TI program is one of the most difficult aspects of managing this function. Traditional volume-based metrics — the number of IoCs collected, the number of feeds, the number of reports generated — do not measure value, but activity. An organization can collect millions of indicators and still have zero intelligence value if none of those indicators are operationalized, none reduce detection time, and none influence decisions.

Operationally effective metrics concern the impact on SOC and IR processes. Mean Time to Detect (MTTD) for threats covered by TI versus threats without TI coverage — the quantified difference shows the value of the program. Alert enrichment coverage rate: what percentage of SOC alerts are automatically enriched with TI data? Operationalization rate: how many of the delivered IoCs were actually loaded into blocking systems or SIEM rules within 24 hours of acquisition? Feed accuracy rate: what percentage of IoCs from individual sources generate actual alarms (not false positives) — this allows low-quality sources to be eliminated.

Strategic metrics concern the value delivered to the board and CISO. MITRE ATT&CK matrix coverage: what percentage of techniques used by APT groups relevant to the industry are covered by current detection rules? Threat hunting effectiveness rate: how many campaigns were detected proactively through hunting versus reactively through alerts? Cost per confirmed incident: a TI program that reduces MTTD by hours has a measurable financial value in the context of incident cost reduction.

A framework for measuring TI program maturity can be based on the TI Maturity Assessment model, which evaluates an organization across five areas: data collection, analysis, operationalization, sharing (exchange with partners), and measurement. Each area is rated on a scale of 1–5, where 1 denotes absence or ad-hoc processes, and 5 denotes fully automated, measured, and optimized processes.

The TI measurement rule: if you cannot show how a specific piece of intelligence changed a decision or operational action, you are not measuring effectiveness — you are measuring activity. Every TI report should include a “recommended actions” section with a measurable expected outcome.

Regular tabletop exercises are an underappreciated method of measuring TI program effectiveness. Simulating an attack scenario (e.g., “Ransomware group X attempts to attack the sector using techniques Y and Z”) and verifying whether the team has the knowledge to respond effectively provides a qualitative picture of gaps in the program. The results of tabletop exercises translate directly into development priorities for the TI program in the following quarter.

What tools support threat intelligence — MISP, OpenCTI, commercial platforms?

The ecosystem of tools for managing threat intelligence is rich and varied in terms of cost, capabilities, and operational requirements. The choice of tools should be a derivative of the defined process and integration requirements — not the other way around.

MISP (Malware Information Sharing Platform) is an open-source platform for sharing indicators of compromise and intelligence data, developed by CIRCL (Computer Incident Response Center Luxembourg). It is the de facto standard in the CERT community and sector-specific sharing groups. MISP supports the STIX/TAXII format, enables synchronization with other MISP instances (so-called MISP feeds), and integrates with most SIEMs and security tools. For organizations joining sector-specific sharing communities (e.g., the MISP Community of Polish financial institutions coordinated by the KNF), MISP is often the platform required by partners. Implementation costs: zero licensing cost, plus the cost of maintaining the infrastructure and technical expertise.

OpenCTI (Open Cyber Threat Intelligence) is another open-source platform, developed by ANSSI (the French National Information Systems Security Agency) and Luatix. OpenCTI is more oriented toward relationship analysis and knowledge graphs — it allows the visualization of connections between threat groups, campaigns, techniques, and indicators. The platform natively integrates with MITRE ATT&CK, MISP, and many commercial feeds. OpenCTI is particularly valuable for teams that want to build analytical context around IoC data — instead of a bare list of indicators, they create a structured threat knowledge base with graph query capabilities.

Commercial TI platforms offer full enterprise-class solutions with higher automation capabilities, larger data resources, and vendor support. Recorded Future is the market leader with a rich intelligence database based on analysis of the open web, dark web, and technical indicators. Mandiant Advantage (Google Cloud) offers unique context drawing on Mandiant’s global telemetry and incident responses. CrowdStrike Falcon Intelligence combines TI with the EDR platform, providing intelligence context directly within the endpoint detection process.

To the everyday analyst toolkit it is worth adding: VirusTotal Enterprise (file and URL analysis with cross-correlation across multiple AV engines and TI databases), Shodan and Censys (internet infrastructure reconnaissance, monitoring of the attack surface and attacker infrastructure), ANY.RUN and Hybrid Analysis (sandboxes for malware analysis with MITRE ATT&CK integration), and Maltego (connection network visualization for OSINT and attacker infrastructure analysis).

For organizations building a program from scratch, the recommended tooling path is: phase 1 (months 1–3) — MISP + free feeds (OTX, ThreatFox, Abuse.ch) + VirusTotal Community + MITRE ATT&CK Navigator; phase 2 (months 4–12) — MISP integration with SIEM, OpenCTI for relationship analysis, pilot of one commercial sector-specific feed; phase 3 (year 2+) — commercial TI platform, automation through SOAR, regular TI-driven threat hunts.

What does TI program maturity look like in an organization?

The following table presents a threat intelligence program maturity model at five levels. Each level describes organizational capabilities, typical tools, and key effectiveness metrics. The model is based on the Threat Intelligence Maturity Model (TIMM) framework and the practices described by the SANS Institute.

Maturity levelCharacteristicsCapabilitiesTypical toolsKey metrics
1 — Ad-hocNo formal TI program. Responding to threats only after an incident. No dedicated process or tools.No systematic IoC collection. Occasional reading of industry reports. No SIEM integration.Spreadsheets, VirusTotal (ad-hoc), manual IP lookups.No defined metrics. MTTD measured in days or weeks.
2 — InitialFirst attempts at systematization. Subscription to free feeds. Manual SIEM integration via blocklists.Collecting IoCs from 1–3 open feeds. Manual analysis and loading into SIEM once a week or less frequently. First IR playbooks.AlienVault OTX, Abuse.ch, Excel spreadsheets, basic SIEM.Number of IoCs collected. Time to load IoC into SIEM (days). Alert enrichment: <10%.
3 — DefinedFormal TI program with defined processes and responsibilities. Automatic feed integration with SIEM. First TTP analyses.Automatic IoC loading into SIEM (STIX/TAXII). Tactical analysis for selected APT groups. Regular TI bulletins for SOC. Incipient threat hunting (1–2 times per quarter).MISP, OpenCTI, Splunk/Sentinel, MITRE ATT&CK Navigator, one commercial feed.MTTD for IoCs <4h. Alert enrichment >40%. ATT&CK coverage: 20–40% of industry-relevant techniques.
4 — ManagedIntegrated TI program covering all four levels (strategic, tactical, operational, technical). Regular threat hunts. Exchange with sector partners.Full IoC → SIEM → blocking automation. TI-based threat hunting (monthly). Strategic reports for the board. Participation in an ISAC or other sharing platform. Malware analysis in-house or via a partner.Commercial TI platform (Recorded Future/Mandiant), MISP, OpenCTI, SOAR, sandbox (ANY.RUN).MTTD for IoCs <1h. Alert enrichment >70%. ATT&CK coverage >60%. Threat hunting: at least 1 per month. True positive rate from TI >80%.
5 — OptimizingFully integrated, measured, and continuously improved TI program. Dedicated CTI team. Active participation in creating external intelligence (sharing with the sector, publications).Continuous threat hunting (dedicated team). Proprietary intelligence from honeynets and own sensors. Predictive threat analysis. Active participation in communities (MISP Community, ISAC leadership). Adversary simulation testing ATT&CK coverage.Dedicated CTI platform, own sensors (honeypots, canaries), Maltego, advanced sandbox, full SOAR automation.MTTD for IoCs <15 min. Alert enrichment >90%. ATT&CK coverage >80% of industry profile techniques. Contribution to external platforms (IoC sharing).

Most mid-market organizations in Poland operate at level 1–2. Moving from level 2 to level 3 is a transformational moment, typically requiring 6–12 months of work and an investment of human resources more than tooling budget. Levels 4 and 5 are the domain of organizations with dedicated CTI (Cyber Threat Intelligence) teams — typically large financial institutions, critical infrastructure operators, and global corporations.

How does nFlo integrate threat intelligence with 24/7 SOC services?

nFlo builds its Security Operations Center (SOC) services around the concept of intelligence-driven defense — an approach in which threat intelligence is not an optional add-on, but the foundation of every operational process: from alert triage to planning threat hunts and reporting to the client’s board. This stems from an observation of a recurring pattern in organizations that come to us after an incident: the threat was visible in external intelligence sources weeks before the attack, but the organization lacked the capability or process to translate that information into defensive action.

The technical architecture of nFlo’s SOC integrates multiple TI layers with a 24/7 SIEM platform. At the technical level — automatic IoC feeds updated continuously, correlated in real time against client telemetry. At the operational level — every high-priority alert is automatically enriched with TI context before it reaches the analyst’s queue: information about the group, campaign, associated ATT&CK techniques, and a recommended action. At the tactical level — regular threat hunts based on current knowledge of sector threats, launched proactively, without waiting for an alert.

For every client we build an individual intelligence risk profile — an intelligence requirement document — which defines which threat groups, which sectors, and which geographic areas are relevant for that specific organization. This is a living document, updated quarterly, that shapes hunting priorities, feed selection, and reporting format. A client in the manufacturing sector receives a different set of intelligence information than a financial firm or a critical infrastructure operator.

The response time we commit to in contracts with SOC clients is achievable precisely because of this intelligence-driven architecture. When a new high-confidence IoC appears in the ecosystem of external feeds, an automated SOAR workflow loads it into the blocking systems in client environments and enriches SIEM rules — before an analyst has had time to respond. The human in this process makes decisions that require business context and risk assessment, not manual lookups in databases.

Experience serving more than 200 clients and completing more than 500 security projects has given nFlo a unique intelligence resource on threats typical to the Polish and regional market. Attack patterns we observe in telemetry from different organizations create proprietary intelligence impossible to build by any single organization without this scale of observation. This resource — anonymized and aggregated — feeds detection mechanisms and hunts for all clients, creating a network effect: every detected attack technique strengthens protection across the entire client ecosystem.

The effectiveness of this approach is reflected in a 98% client retention rate — organizations that have once experienced an intelligence-driven SOC understand the difference between reacting to alerts and proactive protection based on knowledge.


FAQ — frequently asked questions about threat intelligence

What is the difference between threat intelligence and threat data?

Threat data is raw data — a list of IP addresses, file hashes, domains. Threat intelligence is processed information with context: who is behind the indicators, what their motivations are, what techniques they use, and why a specific organization should or should not be concerned about them. Transforming data into intelligence requires an analytical process and context.

Does a small organization need threat intelligence?

Yes, but scaled appropriately to its capabilities. Even an organization without a dedicated TI analyst can use free IoC feeds integrated with a SIEM, subscribe to CERT Poland bulletins, and apply detection rules from the MITRE ATT&CK database. An alternative is outsourcing to a SOC-as-a-Service provider that delivers TI as part of the service.

How much does it cost to build a threat intelligence program?

Costs vary enormously. A minimal program based on open sources (MISP + free feeds) requires primarily analyst time — a few hours per week. Commercial TI platforms (Recorded Future, Mandiant) cost from tens of thousands to hundreds of thousands of PLN per year. SOC-as-a-Service with built-in TI is a subscription model scaled to the size of the organization.

How long does it take to implement a threat intelligence program?

The basic elements — integrating several feeds with a SIEM, the first set of ATT&CK-based rules, defined intelligence requirements — can be launched in 4–8 weeks. A mature program covering all four TI levels, regular hunts, and strategic reports typically takes 12–24 months to build. Maturity at levels 4–5 requires years of systematic work.

What is STIX/TAXII and why is it important?

STIX (Structured Threat Information eXpression) is a standard format for exchanging threat intelligence data — it allows indicators, threat groups, techniques, and campaigns to be described in a structured, machine-readable form. TAXII (Trusted Automated eXchange of Indicator Information) is the transport protocol for exchanging STIX data between systems. These standards enable automatic integration between TI platforms, SIEMs, and security tools from different vendors.

How do you assess the quality of a threat intelligence feed?

Four assessment criteria: relevance — how many IoCs from the feed are relevant to my industry and environment? Timeliness — how quickly after a threat appears does the feed deliver the information? Accuracy — what percentage of IoCs are false positives? Uniqueness — does the feed provide information not available in other sources? Regular analysis of these metrics makes it possible to eliminate low-quality sources and focus resources on valuable feeds.


Explore key terms related to this article in our cybersecurity glossary:

  • Cybersecurity — Cybersecurity is a set of techniques, processes, and practices for protecting IT systems…
  • SOC — Security Operations Center is a specialized center for monitoring and responding to security incidents…
  • SIEM — Security Information and Event Management is a platform for collecting, correlating, and analyzing security logs…
  • Threat analysis — Threat analysis is the process of identifying, assessing, and prioritizing potential…
  • Blue Team — Blue Team is a group of specialists responsible for defending systems…

Learn more

Explore related articles in our knowledge base:


Check our services

Do you need cybersecurity support? See:

Explore Our Products

Solutions mentioned in this article that can help protect your organization:


See also:

Share:

Talk to an expert

Have questions about this topic? Get in touch with our specialist.

Sales Representative
Grzegorz Gnych

Grzegorz Gnych

Sales Representative

Response within 24 hours
Expert consultation
Individual approach

Providing your phone number will speed up contact.

Want to Reduce IT Risk and Costs?

Book a consultation - we respond within 24h

Response in 24h Custom quote No obligations