S SAINSEC CYBEROPS
05 / THREAT INTELLIGENCE

Threat Intelligence Desk.

Enrich observables, understand adversary behavior and connect external intelligence with internal telemetry.

ANALYST WORKFLOW

Observable → context → action.

Collect → Validate → Enrich → Correlate → Analyze → Act

Use external intelligence as investigation context, then validate it against the user, host, process, time window and surrounding telemetry.

ANALYST PRINCIPLE

An IOC is a lead, not a verdict.

An IP, domain, URL or hash match should be investigated in context. Reputation and intelligence sources can support a hypothesis, but internal evidence determines the incident decision.

01 / THREAT ACTORS

Know the adversary.

Research actor profiles, aliases, techniques, targets and related campaigns before pivoting into an investigation.

MITRE ATT&CK Groups

CHECK: Group aliases, techniques, software, procedures and known relationships.

USE FOR: Actor profiling and mapping observed behavior to ATT&CK.

↗ Open

Google Threat Intelligence

CHECK: Threat actors, campaigns, infrastructure, reports and related TTPs.

USE FOR: Adversary research, campaign context and infrastructure pivots.

↗ Open

Microsoft Threat Intelligence

CHECK: Threat actors, cybercrime activity, nation-state activity and emerging threats.

USE FOR: Current threat research and Microsoft ecosystem investigations.

↗ Open
02 / CAMPAIGN INTELLIGENCE

Follow the activity.

Use campaign reporting to understand targeting, attack chains, infrastructure and defensive opportunities.

CISA Cybersecurity Advisories

CHECK: Published advisories, affected technologies, mitigations and threat activity.

USE FOR: Validating current campaigns and translating public guidance into defensive actions.

↗ Open

Microsoft Threat Reports

CHECK: Campaign research, threat actor activity, attack techniques and defensive guidance.

USE FOR: Understanding attacker behavior and Microsoft-focused campaigns.

↗ Open

Google Threat Intelligence

CHECK: Campaign context, actor activity, infrastructure and Mandiant research.

USE FOR: Correlating campaigns with infrastructure and TTPs.

↗ Open
03 / IOC INTELLIGENCE

Enrich the observable.

Use multiple intelligence sources rather than relying on a single reputation result.

VirusTotal

CHECK: IP, domain, URL and file reputation, detections, relationships and community context.

USE FOR: Initial enrichment and pivoting across related observables.

↗ Open

ThreatFox

CHECK: Malware-associated IPs, domains, URLs, hashes and IOC confidence/context.

USE FOR: Malware and botnet IOC hunting and infrastructure pivots.

↗ Open

AlienVault OTX

CHECK: Pulses, IOCs, threat reports and community-contributed context.

USE FOR: IOC enrichment, campaign pivots and threat-hunting leads.

↗ Open

URLhaus

CHECK: Malicious URLs, payloads, hosting information and malware associations.

USE FOR: Phishing, malware-delivery and suspicious-URL investigations.

↗ Open

AbuseIPDB

CHECK: IP abuse reports, confidence scores, categories and historical reports.

USE FOR: Source-IP context during scanning, brute-force and suspicious connection investigations.

↗ Open

MISP

CHECK: Structured threat intelligence, events, attributes and relationships.

USE FOR: Sharing and correlating structured threat intelligence across teams.

↗ Open
04 / TTP INTELLIGENCE

Behavior over indicators.

Map what the adversary did to techniques, evidence sources and detection opportunities.

MITRE ATT&CK

CHECK: Tactics, techniques, sub-techniques, software and procedure examples.

USE FOR: TTP mapping, threat hunting hypotheses and detection coverage analysis.

↗ Open

Microsoft Sentinel Threat Intelligence

CHECK: Threat indicators, analytics, workbooks and intelligence integrations.

USE FOR: Connecting threat intelligence to SIEM investigations and detections.

↗ Open

Detection Mapping

CHECK: Which logs, endpoint events, identity records and network telemetry can evidence a technique.

USE FOR: Turning intelligence into concrete detection and hunting requirements.

↗ Open
05 / MALWARE INTELLIGENCE

Understand malicious software.

Pivot from a sample or hash into family, behavior, infrastructure and related indicators.

MalwareBazaar

CHECK: Malware samples, hashes, tags, family information and related intelligence.

USE FOR: Malware-sample research and hash-based investigation pivots.

↗ Open

VirusTotal Malware Intelligence

CHECK: File detections, relationships, behavior, contacted domains/IPs and related samples.

USE FOR: Sample triage and connecting a file to infrastructure.

↗ Open

Google Threat Intelligence

CHECK: Malware, infrastructure relationships, threat reports and campaign context.

USE FOR: Connecting malware observations to broader campaigns and actors.

↗ Open
06 / INTELLIGENCE SOURCES

Where analysts pivot.

A compact reference set for vulnerability, adversary, IOC and malware intelligence.

CISA KEV Catalog

CHECK: Vulnerabilities added to the Known Exploited Vulnerabilities catalog.

USE FOR: Prioritizing vulnerability investigations where exploitation is documented.

↗ Open

NVD

CHECK: CVE records, affected products, references and vulnerability metrics.

USE FOR: Vulnerability enrichment and product/CVE research.

↗ Open

Microsoft Security Research

CHECK: Threat intelligence, security research and current threat landscape reporting.

USE FOR: Microsoft ecosystem research and defensive context.

↗ Open