Skip to content
Cyber Recrut

Becoming a CTI analyst: skills and first roles

How to become a CTI (threat intelligence) analyst: the real job, the skills to build, entry paths, the practice to show and the roles that get you started.

Published on 7 min read

A CTI (Cyber Threat Intelligence) analyst studies attackers to help their organisation defend itself better. The job attracts very different people, from curious SOC analysts to international relations graduates, and it is hard to know how to get in. This guide describes the actual work, the skills to build, the possible paths and how to land a first role.

The job, beyond the clichés

People often picture CTI analysts deep in hidden forums, tracking famous attacker groups. The reality is more methodical. The role answers a simple question: which threats actually concern our organisation, how do they operate, and what should we do about them?

A typical week can include:

  • reading and sorting sources: CERT-FR bulletins, public vendor reports, sector sharing communities, internal incident findings;
  • analysing a campaign that hits your sector, to extract the techniques used and detection leads;
  • qualifying indicators before passing them to the SOC, so analysts are not drowned in noise;
  • writing a summary note for the CISO or a technical sheet for the detection team;
  • supporting an investigation, when the incident response team needs context on an attacker's methods;
  • maintaining the tooling: threat intelligence platform, collection scripts, automatic enrichment.

Keep one point in mind: a CTI analyst produces for others. Intelligence that supports no decision and no action has no value, however fascinating the analysis.

Four levels of intelligence

The job covers several levels, and roles emphasise one or another. Knowing them helps you read job ads and choose your target.

LevelAudienceWhat you produceSkills that matter most
StrategicLeadership, CISOHow threats against the sector are evolving, what it means for prioritiesAnalysis, writing, economic and geopolitical context
OperationalCISO, incident responseBriefs on a campaign or an attacker's methodsAnalytical method, knowledge of attackers
TacticalSOC, detection engineersTechniques mapped to MITRE ATT&CK, detection leadsDefensive technique, log reading
TechnicalSecurity toolsQualified indicators, fed into the SIEM or EDRAutomation, exchange formats, tooling

In large teams these levels are sometimes split between several people. In smaller ones, a single analyst covers them all, with a focus that depends on their background.

The skills to build

Analytical method

This is what separates an analyst from someone who collects information. You need to be able to:

  • assess the reliability of a source and, separately, the credibility of a piece of information;
  • cross-check before concluding;
  • clearly separate what is established from what is assumed;
  • state a confidence level and stand by it.

Attribution to attacker groups is good practice ground. Take a public report, identify what the attribution rests on, and ask yourself what would really change for a defender if it were wrong. Most of the time, the techniques used matter more than the group's name.

Technical foundations

Even for a strategy-oriented role, a solid technical base is expected. Aim for:

  • understanding how an intrusion unfolds: initial access, execution, persistence, lateral movement, exfiltration;
  • shared frameworks such as MITRE ATT&CK, the Cyber Kill Chain or the Diamond Model, used as structuring tools;
  • indicators of compromise and their limits: an IP address changes fast, a behaviour much less so;
  • a threat intelligence platform such as MISP or OpenCTI, and the STIX exchange format;
  • sharing rules, in particular the TLP protocol;
  • a scripting language, usually Python, to automate collection and enrichment;
  • reading a malware analysis report and extracting what is actionable, without necessarily doing the reverse engineering yourself.

Writing

A CTI analyst writes a lot. A note for leadership fits on one page and ends with recommendations. A sheet for the SOC is precise and directly usable. Adapting the message to the reader is often decisive in hiring, and it can be trained like any technical skill.

English

Most public reports and community exchanges are in English. Fluent reading is essential, and being comfortable speaking it quickly becomes an advantage.

Paths into CTI

Roles fully dedicated to intelligence are rarely open to complete beginners. Most analysts come from a neighbouring job.

  1. From the SOC. This is the most common path. You know the tools, the alerts and what analysts need. Show your interest in the adversary behind the alerts: offer briefs on campaigns that affect your scope, contribute to detection rules. Our guide to becoming a SOC analyst describes this starting point.
  2. From incident response or forensics. You see attacks up close and know how to reconstruct an attacker's methods. What remains is stepping back and writing for non-technical readers. See our article on becoming a forensic analyst.
  3. From intelligence, international relations or research. You master analytical method and writing. Your main task is the technical base, which you need to build seriously before applying.
  4. From pentesting or malware analysis. You understand offensive techniques in depth. Your effort will go into producing intelligence that serves defence, and into synthesis.
  5. From initial education. A cybersecurity degree with a work-study placement in a SOC or CTI team can open a first junior role, often attached to the SOC.

If you are starting from outside IT, plan an intermediate technical step. Our article on the questions to ask before switching into cybersecurity will help you plan it.

Practise and make your work visible

The good news: CTI can be practised with open sources and no special equipment. A few ideas:

  • write briefs on publicly documented campaigns: summary, techniques mapped to ATT&CK, detection leads, confidence level;
  • install MISP or OpenCTI on your own machine and feed them with public feeds;
  • write a small script that enriches indicators and measures how fresh they are;
  • follow CERT-FR publications and practise turning them into recommendations for a specific type of organisation;
  • publish part of your work, as articles or a code repository.

Always respect the legal framework and sharing rules: do not visit spaces where your presence would be unlawful, and never republish information marked as restricted. To present your work, see our advice on building a cybersecurity portfolio.

Landing a first role

Stepping-stone roles

The "CTI analyst" title appears less often than others. Also look at:

  • tier 2 or tier 3 SOC analyst with a threat monitoring remit;
  • incident response analyst in a team that produces intelligence;
  • junior consultant in a firm offering intelligence services;
  • analyst in a sector CERT or a large group's threat monitoring team.

What matters: the time actually spent on intelligence, and whether there are people who use what you produce. Ask about it in the interview.

What interviews assess

Expect a practical exercise: a few public reports on a campaign, some indicators, and a request for a summary for a CISO with actions for the SOC. Employers assess your method, your caution with conclusions and the clarity of your writing. Our employer guide to hiring a CTI analyst details what they look for, and our advice on preparing for a practical test will help you train.

On pay, differences are wide depending on sector, region, team size and the level of intelligence expected. Compare offers across all these criteria.

In short

Becoming a CTI analyst means learning to turn a mass of information into useful decisions for an organisation. Build a rigorous analytical method, a solid defensive technical base and real writing skills. Start from your current job, often the SOC or incident response, and show concrete work produced from open sources.

Aiming for a threat intelligence role? Join the Cyber Recrut network for free: our shortlisted candidates prove their skills on hands-on labs, so your background counts for what you can actually do. You can also see how we work.

Related articles