Hiring a CTI analyst: profile, role and assessment
How to hire a CTI (threat intelligence) analyst: what the role involves, prerequisites, skills to check, a practical exercise and interview questions that work.
Many security teams receive indicator feeds, advisories and vendor reports every day, and nobody has time to read them, sort them and turn them into decisions. A CTI (Cyber Threat Intelligence) analyst turns that flood of information into intelligence your organisation can act on. This guide helps you decide whether you need the role, scope it and assess candidates on what they can really do.
What a CTI analyst does
Threat intelligence answers a simple question: who might target us, how, and what should we do about it? A CTI analyst does more than collect information. They assess it, put it in context and pass it to the people who need to act.
The work usually follows a cycle borrowed from the intelligence world:
- Gather requirements. What do the CISO, the SOC, the incident response team and leadership need to know? Without stated requirements, CTI produces reports nobody reads.
- Collect. Open sources, CERT-FR advisories, sector sharing communities, vendor reports, internal telemetry, lessons from incidents.
- Process and analyse. Deduplicate, check source reliability, connect the pieces, separate fact from hypothesis.
- Disseminate. Match the format to the audience: actionable indicators for the SOC, a profile of an attacker's tradecraft for engineers, a summary note for leadership.
- Collect feedback. Was the intelligence useful? Do priorities need adjusting?
Intelligence is often split into levels, and the role covers more or fewer of them depending on your organisation:
| Level | Audience | Example output |
|---|---|---|
| Strategic | Leadership, CISO | How threats against your sector are evolving and what that means for security priorities |
| Operational | CISO, incident response | An ongoing campaign, a threat group's modus operandi, likely targets |
| Tactical | SOC, detection engineers | Techniques in use, mapped to MITRE ATT&CK, detection leads |
| Technical | Security tooling | Qualified indicators of compromise fed into the SIEM or EDR |
A good CTI analyst can move between levels. A candidate who only talks about technical indicators, or only about geopolitics, will cover part of the need at best.
Do you need a CTI analyst?
Intelligence only has value if it drives decisions and actions. Before you open the role, make sure someone can use what it produces.
| Prerequisite | Why it matters | If it is missing |
|---|---|---|
| Detection already in place (in-house or managed SOC) | Indicators and techniques need to become rules and alerts | Start by hiring a SOC analyst |
| Identified consumers | A report with no reader is wasted effort | First define who consumes intelligence, and for which decisions |
| Exposure to targeted threats | Sensitive sector, valuable data, an entity in scope of NIS2 or DORA | Good-quality sources and a curious SOC analyst may be enough at first |
| An incident response capability | Intelligence guides investigations and investigations feed intelligence | Structure response first, see our guide to hiring an incident response lead |
In many mid-sized organisations, threat monitoring starts as a shared activity between a tier 3 SOC analyst and the CISO. A dedicated role makes sense once the volume of information, the sensitivity of the sector and the number of consuming teams call for it.
CTI analyst, threat hunter, detection engineer: telling them apart
These three profiles work together, and a vague job description attracts candidates who do not fit your need.
- The CTI analyst answers "which threats concern us and how do they operate?". Their main output is intelligence, shaped for each audience.
- The threat hunter answers "are those threats already inside?". They turn intelligence into hunting hypotheses. Our guide to hiring a threat hunter covers the role.
- The detection engineer answers "how do we see this behaviour reliably, over time?". They industrialise what CTI and hunting have surfaced, as explained in our article on hiring a detection engineer.
In a small team, one person may hold two of these roles. Say so clearly in the job ad and state how their time is split.
Skills to check
Analytical rigour
This is the core of the job. A CTI analyst must assess the reliability of a source and the credibility of a piece of information, separate what is established from what is assumed, and express a level of confidence. Be wary of candidates who present attribution to a threat group as certain without being able to say what it rests on.
Knowledge of threats and tradecraft
Candidates should know the main threat families (ransomware, espionage, fraud, supply chain attacks) and be able to walk through how an intrusion actually unfolds. Frameworks such as MITRE ATT&CK, the Cyber Kill Chain or the Diamond Model provide a shared language. Good candidates use them to structure thinking, not as lists to recite.
Technical skills
Depending on the level of intelligence you expect, check:
- an understanding of indicators of compromise and their limits (an IP address or domain changes fast, behaviour much less so);
- hands-on use of a threat intelligence platform such as MISP or OpenCTI, and exchange formats such as STIX;
- the ability to read a malware analysis report and extract what is actionable, without necessarily reverse engineering themselves;
- basic scripting (usually Python) to automate collection and enrichment;
- familiarity with information sharing rules, in particular the TLP protocol.
Writing and communication
A CTI analyst spends much of their time writing. A note for leadership should fit on one page and end with recommendations. A brief for the SOC should be precise and ready to use. Adapting the message to the reader matters as much as the quality of the analysis. Our article on soft skills in cybersecurity goes further on this.
Language
Most technical sources and public reports are in English. Fluent reading is essential for a French team; depending on the sharing communities you take part in, spoken fluency may be too.
Profiles that succeed
CTI analysts come from varied backgrounds:
- The SOC or incident response analyst who is curious about the adversary behind the alerts. They know the tools and what the SOC needs.
- Someone from intelligence, international relations or research, comfortable with analytical method and writing. They often need to strengthen their technical foundations.
- The malware analyst or pentester who wants a wider view. They bring a detailed grasp of techniques but must learn to write for non-technical readers.
None of these paths guarantees success. Choose based on what your team lacks: technical depth, analytical method or the ability to speak to leadership.
How to assess candidates
The practical exercise
CVs and certifications say little about the quality of someone's analysis. A short exercise on a realistic case is the best way to decide, as we explain in our article on assessing skills beyond the CV.
A format that works well:
- Give the candidate a small pack: two or three public reports on a campaign, a few indicators and a brief description of your organisation.
- Ask them, within a set time, for a one-page note for the CISO and a list of actions for the SOC.
- Have them present their work and defend their choices: which sources they trusted, what they set aside, how confident they are in their conclusions.
Watch the approach as much as the result. A candidate who acknowledges uncertainty and proposes concrete actions is worth more than one who produces brilliant prose with nothing actionable.
Interview questions
- "Which threats should concern us most, and why?" You want reasoning tied to your sector and exposure, not a generic list.
- "How do you assess the reliability of a source?" A good answer separates source reliability from information credibility and mentions corroboration.
- "A public report attributes a campaign to a specific group. What do you do with that?" Expect caution, a look at what the attribution rests on, and a focus on what matters for defence: the techniques used.
- "Tell me about intelligence you produced that changed a decision." Look for a clear requirement, an analysis, an audience and a concrete effect.
- "What do you do with a feed that sends you thousands of indicators a day?" The answer shows how they think about qualification, indicator ageing and noise.
To align scoring across interviewers, our guide to structuring a technical cyber interview offers a simple grid.
Mistakes to avoid
- Hiring a CTI analyst with no consumers. If nobody reads or uses their output, they will burn out or leave.
- Reducing the role to indicator management. Feeding IP addresses into a tool does not need an analyst; producing intelligence does.
- Skipping writing in the assessment. A purely spoken interview tells you nothing about the ability to write a clear note.
- Overrating paid sources. The best sources do not replace method. Ask candidates how they work with open sources.
- Not defining how contribution is measured. Set qualitative expectations: requirements covered, detections built from intelligence, decisions informed.
In short
A CTI analyst adds value when your organisation has people able to act on intelligence: a SOC, an incident response team, a CISO setting priorities. Assess candidates on analytical rigour, knowledge of tradecraft and the ability to write for different readers. A short exercise followed by a debrief reveals those qualities far better than a theoretical interview.
Thinking about hiring a CTI analyst? At Cyber Recrut, a recruiter and a security practitioner scope the role with you, pin down the level of intelligence you need and run the search together. Our shortlisted candidates prove their skills on hands-on labs. See how we work or share your hiring need.