text: August 2025

text: August 2025

text: August 2025

text: https://www.enisa.europa.eu/topics/threat-risk-management/threats-and-trends 2 https://www.enisa.europa.eu/publications/enisa-threat-landscape-methodology 3

text: August 2025

text: August 2025

text: August 2025

text: Figure 2: Overview of ENISA CTL production process

text: Figure 3: CTL direction definition process

text: https://filigran.io/understanding-cyber-threat-intelligence-lifecycle/ 6

text: August 2025

text: https://www.sekoia.io/en/glossary/ttp-cyber-tactics-techniques-and-procedures/ 5 https://intel471.com/blog/cyber-threat-intelligence-requirements-what-are-they-what-are-they-for-and-how-do-they-fit-in-the 6 Any intentional effort to disrupt, compromise, or damage digital assets, systems, or networks through unauthorized access or malicious actions (ENISA) 7

text: August 2025

text: Figure 4: CTL data collection process

text: https://www.first.org/global/sigs/cti/curriculum/pir 8

text: August 2025

text: What are the most deployed ransomware strains • Consult ransomware groups Data Leak Sites (DLS) against EU organisations over the reporting period? • Consult ENISA knowledge base • Consult ENISA stakeholders

text: Table 1: Example of defining data collection requirements

text: J. AMMONS, ‘How to Use MITRE ATT&CK to Improve Threat Detection Capabilities’ Gartner (2021). 9 https://www.bercynumerique.finances.gouv.fr/roso-osint-lexploitation-des-sources-ouvertes-sur-internet https://wikis.ec.europa.eu/spaces/ExactExternalWiki/pages/50109048/Context+analysis+–+PESTEL 9

text: August 2025

text: Source Type of data Collection time

text: Private vendors Operational, tactical All year

text: Institutional stakeholders Operational, strategic All year

text: Social media Operational, strategic, tactical All year

text: Vulnerability disclosure Operational, tactical All year

text: Research Operational, strategic, tactical All year

text: Table 2: TAS indicative intelligence collection plan

text: X., “Challenges to effective EU cybersecurity policy”, European Court of Auditors (2019) 10

text: August 2025

text: Source Reliability Information Credibility

text: A - Completely reliable 1 - Confirmed by other sources B - Usually reliable 2 - Probably True C - Fairly reliable 3 - Possibly True D - Not usually reliable 4 - Doubtful E – Unreliable 5 - Improbable F - Reliability cannot be judged 6 - Truth cannot be judged

text: https://www.threat-intelligence.eu/methodologies/#the-admiralty-scale-also-called-the-nato-system 11

text: August 2025

text: 15 ENISA Threat Taxonomy: first established in 2016 and updated in 2022 , the ENISA threat taxonomy became the guiding principle for CTLs and the standard for threats referenced within ENISA. The taxonomy is currently under revision for the purpose of developing a more mature, actionable framework.

text: ®17 ® • Cyber Kill Chain : developed by Lockheed Martin, the Cyber Kill Chain framework ® is part of the Intelligence Driven Defence model for the identification and prevention of activities related to cyber intrusions. The model identifies what the adversaries must

text: https://style-guide.europa.eu/en/content/-/isg/topic?identifier=part-four-publications-in-a-specific-language 14 https://www.enisa.europa.eu/topics/threat-risk-management/threats-and-trends/enisa-threat-landscape/threat-taxonomy/view 15 https://github.com/enisaeu/Reference-Security-Incident-Taxonomy-Task-Force 16 https://www.oasis-open.org/committees/cti 17 https://www.lockheedmartin.com/en-us/capabilities/cyber/cyber-kill-chain.html 12

text: August 2025

text: The following caveats should be taken into account.

text: https://euvd.enisa.europa.eu/homepage 19 https://cve.mitre.org/ 13

text: August 2025

text: Figure 5: CTL data analysis and production process

text: Figure 6: Analysis approaches

text: Heuer and Pherson, Structured Analytic Techniques for Intelligence Analysis, 2019 21 According to The Five Habits of the Master Thinker, 22 Authors Richards J. Heuer, Richards J. Heuer Jr., Randolph H. Pherson, Publisher CQ Press, 2010, ISBN 1608710181, 9781608710188 14

text: August 2025

text: Textual formats

text: Machine-readable formats

text: August 2025

text: Figure 7: CTL dissemination process

text: Current ETL report structure, ENISA.docx 24 https://x.com/enisa_eu 25 https://www.linkedin.com/company/european-union-agency-for-cybersecurity-enisa 26 https://www.enisa.europa.eu/topics/cyber-threats 16

text: August 2025

text: Figure 8: CTL feedback collection process

text: August 2025

identifier: ENISA Cybersecurity Threat Landscape Methodology

title: ENISA Cybersecurity Threat Landscape Methodology

text: ENISA CYBERSECURITY THREAT LANDSCAPE METHODOLOGY AUGUST 2025 0

text: ENISA CYBERSECURITY THREAT LANDSCAPE METHODOLOGY

text: ABOUT ENISA

text: The European Union Agency for Cybersecurity, ENISA, is the Union’s agency dedicated to achieving a high common level of cybersecurity across Europe. Established in 2004 and strengthened by the EU Cybersecurity Act, the European Union Agency for Cybersecurity contributes to EU cyber policy, enhances the trustworthiness of ICT products, services and processes with cybersecurity certification schemes, cooperates with Member States and EU bodies and helps Europe prepare for the cyber challenges of tomorrow. Through knowledge sharing, capacity building and awareness raising, the Agency works together with its key stakeholders to strengthen trust in the connected economy, to boost the resilience of the Union’s infrastructure and, ultimately, to keep Europe’s society and citizens digitally secure. More information about ENISA and its work can be found at: www.enisa.europa.eu.

text: CONTACT

text: To contact the authors, please use etl@enisa.europa.eu

text: For media enquiries about this paper, please use press@enisa.europa.eu.

text: EDITORS

text: Jamila BOUTEMEUR, Ilias BAKATSIS, Ifigeneia LELLA - ENISA

text: CONTRIBUTORS

text: Apostolos MALATRAS, Razvan GAVRILA, Stefano DE CRESCENZO - ENISA

text: LEGAL NOTICE

text: This publication represents the views and interpretations of ENISA unless stated otherwise. It does not endorse a regulatory obligation of ENISA or of ENISA bodies pursuant to the

text: Regulation (EU) No 2019/881

text: ENISA has the right to alter, update or remove the publication or any of its contents. It is intended for information purposes only and it must be accessible free of charge. All references to it or its use as a whole or in part must show ENISA as its source.

text: Third-party sources are quoted as appropriate. ENISA is not responsible or liable for the content of the external sources including external websites referenced in this publication.

text: Neither ENISA nor any person acting on its behalf is responsible for the use that might be made of the information contained in this publication.

text: ENISA maintains its intellectual property rights in relation to this publication.

text: COPYRIGHT NOTICE

text: © European Union Agency for Cybersecurity (ENISA), 2025

text: Unless otherwise noted, the reuse of this document is authorised under the Creative Commons Attribution 4.0 International (CC BY 4.0) licence (https://creativecommons.org/licenses/by/4.0/). This means that reuse is allowed, provided appropriate credit is given and any changes are indicated.

text: For any use or reproduction of elements that are not owned by the European Union Agency for Cybersecurity, permission may need to be sought directly from the respective rightholders.

text: ISBN 978-92-9204-719-1, DOI 10.2824/1888892

text: TABLE OF CONTENTS

text: 1. INTRODUCTION 3

text: 1.1 CTL SCOPE AND DRIVING PRINCIPLES 3

text: 2. CTL METHODOLOGY 5

text: 2.1 OVERVIEW OF THE METHODOLOGICAL APPROACH 5

text: 2.2 DIRECTION 6

text: 2.2.1 Establish CTL Purpose 6 2.2.2 Define Audience 7 2.2.3 Define Intelligence Requirements 7

text: 2.3 COLLECTION 8

text: 2.3.1 Define collection plan 8 2.3.2 Validate Sources 10 2.3.3 Input data collection 11

text: 2.4 PROCESSING 11

text: 2.4.1 Preparation for processing 11 2.4.2 Language processing 11 2.4.3 Cyber threat taxonomy 12 2.4.4 CTI frameworks 12 2.4.5 Consolidate processed content 13 2.4.6 Correlate and enrich processed content 13

text: 2.5 ANALYSIS & PRODUCTION 14

text: 2.5.1 Analysis preparation 14 2.5.2 Performing analysis 14 2.5.3 Validate CTL 15 2.5.4 Validate dissemination medium 15 2.5.5 Deliverable production 16

text: 2.6 DISSEMINATION 16

text: 2.6.1 Prepare dissemination 16 2.6.2 Disseminate CTL deliverable 16

text: 2.7 FEEDBACK 17

text: 2.7.1 Receiving feedback 17 2.7.2 Actioning feedback 17

text: 3. FUTURE WORK 18

text: 3.1 MOVING TOWARDS AUTOMATED INFORMATION PROCESSING 18

text: 1. INTRODUCTION

text: Policy makers, risk managers and information security practitioners need up to date and accurate information on the current threat landscape, supported by situational awareness and threat analysis. The EU Agency for Cybersecurity (ENISA) Cyber Threat Landscape (CTL) reports have been published on an annual basis since 2013. These reports use publicly available data and provides an independent view on observed threats agents, trends and attack vectors, with a focus on the EU threat landscape.

text: ENISA aims at building on its expertise and enhancing this activity for its stakeholders to receive relevant information for policy-creation and decision-making, as well as in increasing knowledge and information for specialised cybersecurity communities or for establishing a solid understanding of the cybersecurity challenges. By providing a snapshot of the constantly shifting cyber threat landscape, ENISA's cyber threat analysis efforts add value. By identifying mid- to long-term trends, these initiatives foster situational awareness and the ability to anticipate future difficulties.

text: ENISA seeks to provide targeted as well as general reports, recommendations, analyses and other actions on threat landscapes, supported through a clear and publicly available methodology. By establishing the ENISA CTL methodology, the Agency aims at setting a baseline for the transparent and systematic delivery of horizontal, thematic, and sectorial cybersecurity threat landscapes. The overall focus of the methodological framework involves the identification and definition of the process, methods, stakeholders and tools as well as the various elements which, content-wise, constitute a CTL.

text: Following the revised form of the ENISA Threat Landscape Report 20211 and the ENISA Threat Landscape Report methodology 2022 , ENISA continues to further develop and document this initiative. This updated methodology aims at synthetizing the document to make it more actionable, and provide further details as to the different phases of the CTL production process.

text: 1.1 CTL SCOPE AND DRIVING PRINCIPLES

text: This methodology applies to ENISA’s annual (ENISA Threat Landscape, ETL), sectorial (STL), and other thematic (TTL) threat landscapes, as well as all other reports written by ENISA’s Threat Analysis Services (TAS) for situational awareness purposes.

text: The following considerations and principles are considered critical when drafting a CTL:

text: • Accuracy: a report’s accuracy depends on the information collected, processed, correlated and analysed. The TAS team reflects on the information input strategy and scores the quality of sources based on their accuracy, relevancy and comprehensiveness, the types of presentation format (e.g., report or machine-readable formats) and focus areas (e.g., sector, EU victimology, adversary nexus, threat group, threat type). This is also of particular importance when ENISA publishes sectorial threat landscapes (STL) since their input strategy will need to be refined accordingly. In addition, the accuracy of the report is directly influenced by the quality of analysis and the inferences derived.

text: • Timeliness: Time influences a report’s actionability, especially when a report also accounts for tactical or operational information. The periodicity of a report is influenced by its scope, criticality and the stakeholder requirements it addresses. Based on those criteria, reports can be published as it happens, monthly, quarterly, biannually or annually.

text: • Actionability: the CTL should increase stakeholders’ awareness of threats in the cyber domain, support their decision-making processes and improve their proactive, active defence, and retroactive postures against cyber threats. This can be achieved at both strategic and operational levels. ENISA focuses on this aspect of the CTL by providing cybersecurity recommendations for different categories of threats in its reports, at both operational level and at strategic level. The operational aspect is covered by delivering the basis for the development of a mitigation strategy for prevention against and response to a given threat. The strategic high-level aspect is covered in its annual review of the threat landscape. When delivering thematic or sectorial threat landscapes, the countermeasures proposed reflect the specificity of the sector or the thematic topic under analysis.

text: 2. CTL METHODOLOGY

text: 2.1 OVERVIEW OF THE METHODOLOGICAL APPROACH

text: The CTL production methodology aims at addressing the following questions:

text: • Which type of data is collected? • Who is the targeted audience? • How is the data collected and processed? • How is the data analysed? • What is the structure (components and contents) of a CTL? • How are CTLs disseminated? • What is the process for collecting feedback?

text: For the purpose of the methodology, ENISA’s approach focusses on cooperation, starting with the collection and processing of inputs, performing analysis, interacting with key stakeholders and providing clear recommendations for the improvement of the CTL.

text: As shown in Figure 1, the content of our reports is continuously assessed by ENISA in-house analysts. The visual illustration presented hereunder displays elements of the process of developing the CTL methodology and the areas of focus consolidated in the various steps of the process. The process involves planning the requirements for the threat landscape (scope, target audience), identifying and validating the types and formats of information sources from both internal and external stakeholders. Collected data are processed and analysed, the final draft report is then reviewed and discussed with ENISA relevant stakeholders, before the cybersecurity threat landscape is finalized and published.

text: Figure 1: High level overview of ENISA CTL methodology

text: A CTL represents information or analysis on past and current events, allowing audiences to have a contextualized understanding of the threats they are likely to face. To understand what content a CTL should contain or what taxonomies should be used, one must first understand how the CTL is drafted. An ‘intelligence-driven’ approach adopts practical and useful lessons from the intelligence community to produce the CTL, for example allowing authors to explicitly

text: translate what audiences and stakeholders would like to understand from their CTL (e.g., intelligence requirements) to the respective answers (e.g., findings of analysis).

text: The following figure details a high-level structure for such a process within ENISA, based on the intelligence lifecycle .

text: The upcoming chapters detail the different elements as highlighted in the figure above, and, in each chapter, we explicitly refer to how the methodology is satisfied in the context of the ENISA CTL.

text: 2.2 DIRECTION

text: The aim of this first step is to establish the purpose, the scope, and the audience of CTLs. By establishing these requirements and by taking into consideration ENISA’s legal mandate, we can then define what are the intelligence requirements for the report, what type of information is needed, who might be the stakeholders to provide the information, and to whom the report would be addressed.

text: 2.2.1 Establish CTL Purpose

text: All CTLs aim at sharing information to contribute to enhanced threat analysis for the following purposes:

text: - Providing an accurate EU-level cyber threat overview, - Raising awareness, - Contributing to risk management, - Identifying opportunities for training, exercises and capacity building, - Contributing to strategic decision-making, - Contributing to policy making.

text: ENISA CYBERSECURITY THREAT LANDSCAPE METHODOLOGY 2.2.2 Define Audience

text: Once the purpose for a CTL is established and the deliverable is commissioned, the audience is considered. The audience for a CTL should be as follows.

text: • Strategic: information about developments associated with threats that can be used to drive a high-level strategy. Consumed by security strategist or other senior decisionmakers, it can even reach board level. • Tactical: information about most common Tactics, Techniques and Procedures (TTPs) used by Intrusion Sets to conduct malicious cyber activities. This information is typically consumed by architects (network, system, product or process), security control owners and HR related roles, red/blue/purple teams, incident responders, threat hunters and digital forensics. • Operational: information about precursory and indicatory signals of impending attacks. Usually generated by monitoring the threat environment, contextualized if and when possible, it is usually consumed by incident responders and high-level security staff, such as security managers.

text: As the content and sharing or marking level of the CTL is dependent on the defined audience and vice versa, it is essential to emphasize the significance of clearly defining the audience. For strategic audiences a summary and references to key research assessments should be provided. Additionally, different sections of a CTL should be addressed at different levels. As an example, there could be a separate annex detailing references to TTPs in a graphical way, so detection engineers may explore this more effectively. The document structure can also be used to send a signal to the targeted audience. Therefore, tailoring the structure and analytical depth of the CTL to match audience needs — and explicitly stating those choices — enhances the document’s relevance, actionability, and impact.

text: 2.2.3 Define Intelligence Requirements

text: We define intelligence requirement as any subject, general or specific, upon which there is a need for the collection of information, or the production of intelligence .

text: There is a distinction between what is needed to produce an intelligence report (production requirement), and what information needs to be collected to answer the production requirement (intelligence requirement). Production requirements come from stakeholders, posing a more abstract question. This production requirement is translated into multiple intelligence requirements, breaking down the main question into separate pieces, answerable by the production team.

text: ENISA’s primary production requirement is cyber threats faced by EU Member States (EU MS).

text: Intelligence requirements notably include cyberattacks targeting NIS2 sectors, carried out by State-nexus intrusion sets, cybercrime groups, and hacktivists. For each collected incident or event, the following questions should be addressed:

text: • Does this incident targets and / or impacts at least one EU Member State? • Is this a cross-border incident?

text: • Which sectors are affected? • Which system(s) and/or asset(s) are affected by the incident? • What is the impact of the incident? • How did the associated intrusion set carry out the attack (TTPs)? • What is the intrusion set’s assessed motivation? • Is there a specific context related to this incident? • Which mitigation measure can be applied to counter this threat?

text: Analysis of collected incidents then allows to draw trends and assessments, which are then included in a synthetized manner in the threat landscape reports.

text: Period for which the collected data should be considered is defined. Usually, it specifies the time frame for which we collect the data. Of note, while the majority of incidents selected and analysed to draft CTLs occurred during the defined time period, in some cases, it is possible CTLs will include incidents reported during this timeframe that occurred previously.

text: To assess relevance of a specific event to the EU threat landscape, ENISA analysts rely on a simple scoring system called EU relevance scoring, characterised with the following values:

text: HIGH: A cybersecurity event that may have significant effect to the resilience of the European Union against cyber threats and to the trustworthiness and reliability of services and digital tools for European citizens and businesses.

text: MEDIUM: A cybersecurity event that may have moderate effect to the resilience of the European Union against cyber threats and to the trustworthiness and reliability of services and digital tools for European citizens and businesses.

text: LOW: A cybersecurity event that may have minor or no effect to the resilience of the European Union against cyber threats and to the trustworthiness and reliability of services and digital tools for European citizens and businesses.

text: 2.3 COLLECTION

text: The collection process entails the coordination of a number of operations, including the collection plan, as well as the continuous evaluation of identified sources to ensure accurate and actionable intelligence . Data are collected from multiple sources (publicly available reports, subscription services, information shared by EU Member States and Private Partners with ENISA, etc.). This step of the methodology deals with the data collection plan, and the rating of data sources. It also includes the actual collection of data from the sources before they can be processed and transformed into actionable intelligence in the next phase.

text: 2.3.1 Define collection plan

text: The next step in the process is to clearly define the data collection requirements, identifying and breaking down the information that needs to be collected to meet the intelligence requirements, and from where this data can be monitored and collected. This can be external collection, such as open-source intelligence, cyber threat intelligence (CTI) providers or knowledge sharing groups, and information shared by EU MS or private partners.

text: An example how this would work in practice is present in the table below.

text: Intelligence requirement Collection requirement

text: The data collection requirements are usually stored in an Intelligence Collection Plan (ICP), listing all intelligence requirements, mapping that to type of sources and allowing TAS analysts to collect data on a daily basis. An indicative intelligence collection plan is presented in Table 2. This listing allows analysts to spot overlaps, gaps or inconsistencies, so that they can act accordingly. Data-driven analysis requires skills and relevant tools and services. Since January 2025, the ENISA CTL has been integrated to the ENISA Threat Analysis Services (TAS) processes and catalogue, with a strong focus on the data collection phase, to ensure accuracy of the EU cyber threat picture at a certain point in time.

text: ENISA daily data collection is refined based on production and intelligence requirements,

text: as well as timeframe of the CTL. While data-gathering is a repetitive task, it is essential to foresee an adequate level of continuous evaluation and redundancy to ensure that if an information asset fails, it is replaced by a duplicate or complementary asset that can meet the established collection demand . Most sources are based on open-source intelligence (OSINT), theoretically described as intelligence derived from publicly accessible data that is collected, processed, and distributed to the proper audience in a timely manner to meet intelligence objectives or collection requirements . To avoid information overload and to maximise the value of this abundance of information for a CTL, a structured and continuous assessment of source accuracy and relevance will help in preparing a good collection plan.

text: Based on the direction of the CTL, we define what types of sources we will need and use. The different types of data have the following characteristics.

text: • Operational – tends to include technical details such as Indicators of Compromise (IoCs). • Tactical – contains information about Tactics, Techniques and Procedures (TTPs) associated to a certain incident, malware, or intrusion set. • Strategic – assessed motivation, associated threat actor, contextual information, notably based on the PESTEL method .

text: ENISA CYBERSECURITY THREAT LANDSCAPE METHODOLOGY 2.3.2 Validate Sources

text: The cybersecurity ecosystem of the European Union is complex and multi-layered, cuts across an array of national and EU policy areas – such as justice and home affairs, the digital single market and research policies . Moreover, the EU is heavily invested in public-private cooperation, which is structured in various cooperation formats. While this complex structure – and difference in vantage point and visibility– certainly results in some challenges, it also offers

text: a unique opportunity from a CTL perspective in that intelligence collection can draw upon

text: various trusted sources.

text: Internal sources include anything from internal people, processes and technology assets providing input to intelligence requirements. This is mostly relevant in cases where a CTL is produced by ENISA, to build situational awareness and threat intelligence reports.

text: Institutional sources – represent the numerous EU institutional actors within cybersecurity and their envisaged interrelationships with ENISA. This includes, but is not limited to the CSIRTs Network (incl. CERT-EU), EUROPOL/EC3, EEAS’ STRATCOM, and the Network and Information Security Directive Cooperation Group (NIS-CG).

text: External sources include anything that is collected externally by ENISA. For example, technical indicator repositories, social media, forums. External sources can be categorised as open-source or closed source. External sources provide:

text: • Raw or processed data: data sources can differ greatly. For example, these could be a data provider that delivers output on demand, a tool that can be queried manually or a forum that needs to be visited and interacted with manually.

text: • Information, based on data they themselves collected and/or processed: providers having access to extensive telemetry, for example end point vendors, regularly analyse and establish interesting insights for (potential) clients. This information is published in periodic reports, some of them being CTLs themselves.

text: • Finished intelligence products, based on data and information collected, processed, analysed, and disseminated: the transition from information to intelligence, at least in concept, is mostly done by companies who understand how to produce it.

text: Contextualising should be done at the time of collecting, with source trust levels, as described in the next section. Contextualising is usually taken from the direction and purpose of the report.

text: 2.3.2.1 Source confidence level

text: At this phase of data collection, the source confidence level should be established. It is based on a two-character notation of the Admiralty system , characterising the reliability of the source and the credibility of the information.

text: 2.3.3 Input data collection

text: TAS analysts collect data on a daily basis and based on the sources’ confidence level and EU relevancy score, perform an initial triage in accordance to the requirements set in the previous phases, before processing to the processing of selected data.

text: 2.4 PROCESSING

text: Data processing is the process of converting acquired data into a format that is suitable for human-centric analysis and the output of intelligence. In this stage, the collected data is converted into

text: formats that TAS analysts may use to generate reports and

text: assessments in a more efficient manner. This processing includes the semi-manual correlation of collected data.

text: Figure 4: CTL data processing process

text: 2.4.1 Preparation for processing

text: The data processing of all collected information is prepared and planned in accordance with the defined priority intelligence requirements. A close inter-relationship between the processing and analysis phases of the CTL should be followed, by giving feedback from the analysis phase to the processing.

text: 2.4.2 Language processing

text: When developing a CTL, analysts need to decide upon the language to be used. Although this might sound trivial, it could introduce challenges that need to be addressed accordingly. For example, when collecting reports in English from published open-source threat reports, there is a risk that sources written in other languages could be excluded. Similarly, when monitoring primary sources in various languages, they must be processed into a single coherent language

text: to meet the needs and objectives of the analysis. CTL is using European languages and English sources, and is published in English .

text: 2.4.3 Cyber threat taxonomy

text: Another important element of the methodology for delivering CTL is the definition of ‘content taxonomies’ as the classification used to structure the cyber threat ecosystem. This is crucial for processing as this dictates the structure of how collected data are organised and historical data sets are developed. In this phase, one can observe the immense importance of having consequent taxonomies and frameworks to produce reliable and consistent output.

text: In March 2021, ENISA conducted a survey intended for the improvement of ENISA’s yearly CTL by collecting the requirements and needs of its stakeholders. Following input from this survey, several suggestions were made by relevant stakeholders to consider additional taxonomies.

text: 2.4.4 CTI frameworks

text: Currently, several CTI frameworks exist to structure cyber threats. Each has different focus areas, hence specific uses, ultimately allowing to efficiently capture and organise intelligence based on the threat taxonomy used and the requirements set during the direction and planning phase of the CTL process. In the case of TAS reports, including the ENISA CTL, this part of the process focuses on translating data or information to a common language (STIX2.1), and transforming large volumes of data into usable form or structuring TTP (Tactics, Techniques, ® Procedures) data sets according to MITRE ATT&CK .

text: • OASIS Cyber Threat Intelligence (CTI) STIX™ : one threat intelligence representation and sharing standard developed by OASIS Cyber Threat Intelligence Technical Committee (OASIS CTI TC) is Structured Threat Information eXpression (STIX™) and its counterpart relay mechanism, Trusted Automated Exchange of Intelligence Information (TAXII). In 2021 STIX™ was released as an OASIS Standard. STIX™ is an ontology and a language that describes cyber threats and observable information. It enables organisations to share cyber threat intelligence in a consistent and machine-readable manner allowing them to better understand what computerbased attacks they are most likely to see and anticipate and/or respond to those attacks faster and more effectively. STIX™ has influenced the underlying format for the representation of different platforms for threat intelligence.

text: • STIX 2.1 integrates other framework, like MITRE ATT&CK : is a globally-accessible knowledge base of the tactics of adversaries and techniques based on real-world observations. The ATT&CK knowledge base is used as a foundation for the development of specific threat models and methodologies in the private sector, in government and in the cybersecurity product and service community.

text: finish doing in order to achieve their objectives. The seven steps of the Cyber Kill ® Chain enhance visibility into an attack and enrich an analyst’s understanding of an adversary’s tactics, techniques and procedures.

text: • European Union Vulnerability Database (EUVD) : Launched in 2025 by the European Union, the EUVD was established in response to growing concerns over fragmented vulnerability reporting across member states and to support compliance with the NIS2 Directive. The EUVD’s mission is to identify, define, and catalogue cybersecurity vulnerabilities affecting EU digital infrastructure. Each vulnerability is assigned a unique EUVD Record to ensure consistent tracking and cross-border coordination. Records are contributed by national CERTs, trusted researchers, and industry partners. Each entry includes severity, sector impact, mitigation references, ® 19 and links to related CVEs based on MITRE CVE Programme .

text: • Be wary of the implications due to betting on a single framework. Sometimes selecting a single framework for structuring the entire CTL can yield great benefits, such as the content is so structured that it is immediately actionable for any defender. On the other hand, this also introduces a narrow scope, as it is only relevant for the audience for which the framework is intended.

text: • Reconsider the framework used. Reassessing whether the selected framework meets the purpose and objectives set during the direction and planning phase of the CTL can be controversial and challenging though necessary.

text: 2.4.5 Consolidate processed content

text: Consolidating processed content consists of forming all available processed data into a more efficient usable form. It might consist of the format conversion of pure data, language translation, evaluating the relevance and reliability of data, to name a few. Data consolidation also ensures accuracy of the dataset.

text: 2.4.6 Correlate and enrich processed content

text: Correlation consists of connecting data points, when possible, to identify relationships and patterns across datasets. Correlation enhances analytical accuracy and supports a comprehensive understanding of threat activity.

text: Enrichment involves enhancing processed data by adding relevant contextual information such as geopolitical context, possible drivers for reported incident, or assessed objective of a cyberattack. This step helps to transform isolated indicators or incidents into meaningful intelligence, improving both relevance and usability.

text: ENISA CYBERSECURITY THREAT LANDSCAPE METHODOLOGY 2.5 ANALYSIS & PRODUCTION

text: During the analysis and production phase, the CTL team is trying to answer questions raised in the requirements section. Additionally, the team will identify gaps that could potentially be then used for creating recommendations, based on past ENISA recommendations and other sources.

text: In this step, the ETL editorial team conducts expert analysis to be able to provide meaningful assessments

text: based on the collected information. Based on these assessments, the ETL provides actionable recommendations as well as cybersecurity measures.

text: 2.5.1 Analysis preparation

text: There are different methodologies that one can employ to perform the analysis, e.g., a manual analysis, an automated analysis or a mix of automated and manual. Manual analysis typically involves different teams looking at a data set and trying to reach assessments.

text: When drafting a CTL, the application of Structured Analytical Techniques (SATs) can prove very valuable . The aim of SAT is to help the analysts and developers of CTLs to build and expand their thinking in a structured way, and advance their assessment by removing any bias, so that the quality of intelligence analysis is improved and therefore trust in the results of the analysis is increased.

text: ENISA analysts employ a range of methods and analytic techniques, which can be grouped into four broad categories based on the nature of the analytic methods used and the type of data that are available, i.e., unaided expert judgment, structured analysis, quasi-quantitative analysis and empirical analysis . Depending on the data available, techniques from two or more of these categories can be employed when drafting a CTL. Currently the ETL is based on structured analytical techniques as well as unaided expert judgement, referred to as traditional analysis, which entails critical thinking and expert reasoning.

text: 2.5.2 Performing analysis

text: As mentioned at the analysis preparation step, there are different methodologies that one can follow to carry out the analysis, i.e., manual analysis, automated analysis or a mix of automated and manual analysis as in a hybrid mode. When applying Structured Analytical Techniques (SAT) analysts intuitively think about how they think, whether a certain technique is required and how to visualise output.

text: The challenges that may be faced during analysis can be related to a potential lack of confidence in the data and information collected, to the multiple authors and experts involved, to the need to draft reliable content and statistics to mention a few. In this respect, some considerations to be taken include:

text: • Checking your assessments: establish key assessments, understand when to challenge them; • Considering alternatives: consider alternative explanations or hypotheses for all events; • Consider inconsistencies: look for inconsistent data that provides sufficient justification to quickly discard a working hypothesis or address the inconsistency; • Consider the key driver: focus on the key drivers that best explain what has occurred or what is about to happen; • Focus on context: anticipate the needs of stakeholders and understand the overarching context within which the analysis is being done.

text: 2.5.3 Validate CTL

text: The CTL reports need to be validated before being released and disseminated to the relevant audience. Validation is meant in the form of review and the provision of feedback, commenting and fine tuning. In this way, we ensure that the CTL content is accurate and relevant.

text: 2.5.4 Validate dissemination medium

text: There are various mediums that can be used for disseminating a CTL. This is something to be defined during the initial directions step. At this stage, the dissemination medium needs to be validated to ensure that it is fit for purpose. For example, CTLs can be delivered through download-via-our-website features, by establishing dedicated interactive websites, or publishing key findings directly on social media. This methodology identifies two different broad categories of presentation formats for CTI: textual (prose documents) and machine-readable.

text: With regards to textual CTLs, introducing reference (semi-standardised) presentation or output templates is a necessary task. Reference templates provide several benefits, such as consistency in writing composition and semi-standardising a repetitive process. In addition, an output template is designed based on stakeholder requirements and the messages the originator and, in this case, ENISA wants to deliver (answers to stakeholder questions). As a result, a presentation or output template is influenced by and influences the processes of intelligence collection and analysis as it interprets the stakeholders’ requirements for intelligence. For example, a reference template infers what information should be gathered, processed, analysed and, finally, the way it is to be represented. In 2025, some changes will be brought to the CTL templates.

text: Machine-readable representation formats provide defenders with the means to operationalise and share CTI. Using dedicated software, defenders use machine-readable formats to increase the delivery speed of situational awareness and CTI, and enable automated machine-oriented processing (collection, normalisation, correlation) and analysis. Such formats and their counterpart software for collecting, processing and analysing data and information (threat intelligence platforms) often integrate with other technological solutions to derive additional threat context and seamlessly inform defence components and human agents about detecting, preventing or mitigating attacks. In addition, standardised approaches for representing CTI in a machine-readable format enable interoperability and allow defenders to share and consume intelligence across organisational and geographical boundaries more seamlessly. Currently CTLs

text: are published in text format (pdf), and is enriched with infographics providing a visual representation of the results of analysis.

text: 2.5.5 Deliverable production

text: Once the analysis is completed, findings are documented and the final deliverable is created. This produces a deliverable, where the findings are stored in a certain structure after collection and analysis. Before the final text is compiled to produce the CTL

text: • Text must be synthesised for each threat and combined into one or several documents; • The document(s) must be reviewed (internal, expert group, management approval, proof reading). • Final edits are undertaken, followed by publication.

text: 2.6 DISSEMINATION

text: Dissemination is the part of the intelligence cycle that delivers the CTL reports to the appropriate stakeholders after analysis and drafting are complete. Usually, based on stakeholder requirements, intelligence can be disseminated through public or private channels such as public releases with reports, briefings, blog posts, emails, social media, sharing machine-readable feeds using digital transports or a dedicated threat intelligence platform, as well as briefings and presentations.

text: 2.6.1 Prepare dissemination

text: At this stage, one should choose the model of interaction with the intended audience. There are three models to explore interaction with a CTL audience: push, pull or interactive. All the models have different values, so choosing one should be aligned with the requirements, audience and objectives of the CTL.

text: 2.6.2 Disseminate CTL deliverable

text: This is the actual dissemination of the CTL report based on the different discussed parameters and decided upon in the previous steps. Engagement with the CTI community would be 24 25 beneficial, which would mean using social channels, e.g., X , LinkedIn , or other means of community engagement, in addition to publishing on ENISA’s website . Additionally, this step of the process can also feed the direction or planning phase of the CTL in the sense that after dissemination, feedback, comments, observations, reflections, ideas can be received from the different audiences on how to advance the CTL. The means of receiving this feedback may vary depending on the medium through which a CTL is disseminated.

text: ENISA CYBERSECURITY THREAT LANDSCAPE METHODOLOGY 2.7 FEEDBACK

text: Collecting and acting on received feedback is essential to improve CTLs. The feedback can touch upon the content of the CTL (direction, data collection, analysis method) or the format. The feedback received should be handled bearing in mind the initial objectives of the given CTL and the CTL development team should act accordingly. Having a clear and detailed understanding of the individual needs of the various CTL audiences can be enforced by putting in place a constant feedback loop. Maintaining a continuous stakeholders’ feedback communication process throughout all the individual phases of the CTL development lifecycle is key to the success of the CTL.

text: 2.7.1 Receiving feedback

text: There are various ways to ask for feedback. Feedback on CTLs can be received continuously, through provided email addresses, surveys, social media or in person. In addition to understanding ‘who’ is providing the feedback, it is always relevant to collect as much feedback as possible. Sometimes even the smallest suggestions can lead to great long-term improvements.

text: 2.7.2 Actioning feedback

text: Actioning feedback is probable the most important step, as it involves deciding on the actions to be made after adopting the comments received. Feedback received on a regular basis or an adhoc basis is not immediately actionable as it requires some processing by the CTL team beforehand. This takes time and sometimes this time is not included in the estimates for production resources.

text: To further improve acting on the feedback collected, it is crucial to have more insight into who provided it. This can include CTL audiences but also stakeholders. Having a more granular understanding helps the making of conscious choices on what feedback to action and what to ignore. Once the feedback is processed, suggestions can be made to the relevant parties who can decide on the matter and what improvements are to be approved or rejected.

text: 3. FUTURE WORK

text: The ENISA methodology provides a high-level overview of how to draft a CTL. In a way this is a living document. The Agency and the ETL editorial team are always looking for feedback and ways to improve and update the methodology. The process is not attempting to be exhaustive, and provide a few key steps.

text: Another reason for publishing the ENISA methodology is to enable other entities to create their own annual reports. That way ENISA aims at supporting the community to mature and achieve a higher level of cybersecurity, which is also one of the main objectives of the Agency.

text: 3.1 MOVING TOWARDS AUTOMATED INFORMATION PROCESSING

text: In 2025, the methodology still involves a lot of manual work. Although human interaction and analysis will still be a critical part of the process, most of the work could be automated. For example, different solutions specialise in one or more areas to identify, collect, preserve, process, review, analyse and produce electronically stored information (ESI).

text: Such solutions would allow for the efficient processing, cross-validation and analysis of a variety of ESIs that are currently used to shape the CTL, ranging from common information sources such as OSINT, vulnerability databases, and information received from EU MS and private partners. In this context, these automated solutions could enable the exploration of patterns, trends and relationships within unstructured and structured data with the objective of uncovering insights and intelligence that will enable stakeholders to respond to future cybersecurity challenges proactively or reactively.

text: Additionally, machine readable is increasingly used in the cybersecurity community. In the midterm, the CTL will aim at increasing machine-readable formatting to allow ENISA’ stakeholders for facilitated ingestion of situational awareness.

text: -N -EN -023 5 -2 1 -0 TP

text: ABOUT ENISA

text: The European Union Agency for Cybersecurity, ENISA, is the Union’s agency dedicated to achieving a high common level of cybersecurity across Europe. Established in 2004 and strengthened by the EU Cybersecurity Act, the European Union Agency for Cybersecurity contributes to EU cyber policy, enhances the trustworthiness of ICT products, services and processes with cybersecurity certification schemes, cooperates with Member States and EU bodies, and helps Europe prepare for the cyber challenges of tomorrow. Through knowledge sharing, capacity building and awareness raising, the Agency works together with its key stakeholders to strengthen trust in the connected economy, to boost resilience of the Union’s infrastructure, and, ultimately, to keep Europe’s society and citizens digitally secure. More information about ENISA and its work can be found here: www.enisa.europa.eu.

text: ISBN 978-92-9204-719-1 DOI 10.2824/1888892