Confirmed on the employer's own hiring board on Nov 19, 2026. First seen by Alion on Nov 13, 2026. UST scores B on the Alion truth index.
Senior Cyber Threat Intelligence (CTI) Analyst
Location: Gurugram, India |Hybrid, 2 days in office |Reports to: Security Operations leadership |Senior individual contributor
1. Why this role exists
We are a global professional services firm. Our people, client data, and cloud systems are targets for criminals and state-linked actors.
Our security operations team already detects and responds to threats. This role makes sure we know which threats matter to us before they hit us, and turns that knowledge into better detection, faster response, and better decisions.
You will be the main owner of threat intelligence in India and work closely with security engineers, detection and response analysts, and the cloud and identity teams.
2. What you will do A. Intelligence collection and analysis
- Track threat actors, malware, phishing kits, and attack methods relevant to professional services, consulting, and finance-adjacent firms.
- Use a commercial threat intelligence platform as the main intelligence source: threat actor and malware profiles, risk scores, s, and brand and domain monitoring. Set up and tune s so they match real risks.
- Read and judge sources beyond the platform: vendor reports, government advisories, open-source reporting, dark web and criminal forum monitoring, and information-sharing groups.
- Separate real signal from noise. Rate each source and each finding for reliability and confidence.
- Write clear assessments that say what we know, what we think, and what we do not know.
B. Turn intelligence into action (the most important part)
- Convert reports into detection ideas and hunt hypotheses, mapped to MITRE ATT&CK.
- Work with security engineers to build, test, and tune detections in the SIEM.
- Turn indicators (IPs, domains, hashes) into watchlists and checks, with expiry dates so lists do not rot.
- Own the flow of intelligence from the threat intelligence platform into the SIEM. Check that feeds load correctly, match against logs, and do not flood analysts with low-value s. Do not trust platform risk scores blindly; check them against our own data.
- Run or support threat hunts across logs and tools, including cloud and monitoring platforms.
- After each hunt, record what was checked, what was found, and what gaps in log coverage exist. "No results" must be proven, not assumed.
C. Incident support
- During incidents, give fast context: who is likely behind this, what they usually do next, and what to look for.
- Help scope the incident using known attacker behavior and indicators.
- Support post-incident reviews. Feed lessons back into detections and watchlists.
D. Vulnerability and exposure intelligence
- Judge which new vulnerabilities are being exploited in the wild and which affect our systems.
- Work with vulnerability and cloud security teams so patching order is based on real attacker activity, not only severity scores.
- Review security advisories and decide quickly: "Does this apply to us? Do we need to act today?"
E. Threat intelligence reports and advisories
You will write and own the firm's threat intelligence reports and advisories. This is a core part of the job, not a side task.
- Write for three different readers, and change the content for each:
-Leadership: the risk to the firm, the business impact, what we are doing, and the decision or support we need. One page. No technical details unless they change the decision.
- Technical teams (security operations, IT, cloud, identity): exact indicators, attacker behavior, affected systems, detections, and fixes.
- All employees: short, plain warnings with clear steps (e.g., "do not open this type of email; report it here"). No jargon.
- Produce these products on a regular schedule:
- Urgent advisories when a threat needs action now (e.g., a vulnerability being exploited that affects us, or an active phishing wave). Target: out within hours, not days.
- Regular threat briefing (weekly or monthly) for leadership and security teams.
- Periodic threat landscape report (quarterly) on the actors and attack methods most relevant to the firm.
- Short incident-linked intelligence notes during and after incidents.
- Every report and advisory must answer:
-What happened or is expected?
-Does it affect us? (Say "yes", "no", or "not sure yet" and why.)
-How confident are we, and what is that based on?
-What should the reader do, and by when?
- Decide who gets what, how it is sent, and how sensitive it is. Apply a sharing marking (e.g., TLP) and make sure sensitive details do not reach people who do not need them.
- Avoid fear-driven writing. Do not exaggerate. Do not copy vendor claims without checking them against our own data.
- Get a second review for high-impact advisories before they go out.
- Use approved AI tools to draft faster, but you own the final text. Check every fact, name, and indicator yourself.
- Keep a record of what was sent, to whom, and whether readers acted on it. Use feedback to improve.
- Track and report the value of CTI: detections created, hunts run, incidents helped.
F. Automation and AI
- Build and run automations that save analyst time, using large language models (LLMs), together with scripts and existing SOAR or workflow tools.
- Typical use cases:
-Summarize long vendor reports and advisories into short "does this affect us?" notes.
-Pull indicators, actors, and techniques out of reports and map them to MITRE ATT&CK.
-Draft first versions of detection ideas, hunt plans, and weekly briefings for human review.
-Enrich s and tickets with context from threat intelligence and internal data.
- Build checks into every automation: a person must review anything that informs a decision, detection, or block. Treat LLM output as a draft, never as fact.
- Test for wrong or invented output (made-up indicators, wrong actor names, missed details). Track error rates and fix prompts and workflows.
- Follow firm rules on data handling. Do not send client data, sensitive logs, or confidential incident details to any AI tool that is not approved.
- Document each automation: what it does, what data it touches, who owns it, and how it fails.
G. Program building
- Define what intelligence the business needs (priority intelligence requirements) with security leadership.
- Build and improve CTI processes, templates, and playbooks.
- Manage threat intelligence feeds and vendors: check quality, cost, which modules are actually used, and whether the value justifies renewal.
- Coach junior analysts and share knowledge with the wider security team.
3. What we expect from you Must have
- Experience in cybersecurity, with at least 3 to 4 years in CTI, threat hunting, or detection-focused roles.
- Strong understanding of how attacks work end to end: phishing, credential theft, cloud and identity attacks, ransomware, data theft.
- Hands-on use of MITRE ATT&CK, the Diamond Model, and the Cyber Kill Chain in real work, not only in theory.
- Experience working with a SIEM (Splunk, Sentinel, QRadar or similar) and comfort reading and querying log data.
- Hands-on experience with a commercial threat intelligence platform (e.g., Mandiant, CrowdStrike Intelligence, or similar), plus MISP or OpenCTI. Working knowledge of STIX/TAXII is expected.
- Solid grounding in cloud and identity security (Azure/Entra, Google Cloud, AWS, SSO and identity providers).
- Proven writing ability. You have written threat intelligence reports or advisories for senior leaders and for non-technical staff, and you can show examples (cleaned of sensitive detail). You can explain risk simply, state confidence honestly, and give clear actions.
- Working knowledge of intelligence reporting standards: confidence and source-reliability ratings, and sharing markings such as TLP.
- Good judgment on source reliability and confidence. You can say "I am not sure" and explain why.
Strong plus
- Experience with cloud security posture tools and observability tools for hunting.
- Practical experience building automations with LLMs: writing clear prompts, using APIs, connecting to tools, and checking output quality.
- Scripting (Python or similar) to automate enrichment and reporting. Moderate skill is enough; this is not a software engineering role.
- Awareness of AI-specific risks: prompt injection from untrusted text (e.g., malicious content in a report or phishing email), data leakage, and over-trusting model output.
- Experience writing detection rules (Sigma, YARA, XQL, KQL, SPL or similar).
- Malware triage or reverse engineering basics.
- Dark web and criminal forum research experience, done safely and legally.
- Experience in professional services, consulting, financial services, or other firms that handle sensitive client data.
- Knowledge of the India and Asia-Pacific threat landscape, including regional actors and regulations (e.g., India's CERT-In reporting rules, DPDP Act).
- Participation in sharing communities (ISACs, trusted groups, CERT-In engagement).

