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.
Enrich observables, understand adversary behavior and connect external intelligence with internal telemetry.
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.
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.
Research actor profiles, aliases, techniques, targets and related campaigns before pivoting into an investigation.
CHECK: Group aliases, techniques, software, procedures and known relationships.
USE FOR: Actor profiling and mapping observed behavior to ATT&CK.
↗ OpenCHECK: Threat actors, campaigns, infrastructure, reports and related TTPs.
USE FOR: Adversary research, campaign context and infrastructure pivots.
↗ OpenCHECK: Threat actors, cybercrime activity, nation-state activity and emerging threats.
USE FOR: Current threat research and Microsoft ecosystem investigations.
↗ OpenUse campaign reporting to understand targeting, attack chains, infrastructure and defensive opportunities.
CHECK: Published advisories, affected technologies, mitigations and threat activity.
USE FOR: Validating current campaigns and translating public guidance into defensive actions.
↗ OpenCHECK: Campaign research, threat actor activity, attack techniques and defensive guidance.
USE FOR: Understanding attacker behavior and Microsoft-focused campaigns.
↗ OpenCHECK: Campaign context, actor activity, infrastructure and Mandiant research.
USE FOR: Correlating campaigns with infrastructure and TTPs.
↗ OpenUse multiple intelligence sources rather than relying on a single reputation result.
CHECK: IP, domain, URL and file reputation, detections, relationships and community context.
USE FOR: Initial enrichment and pivoting across related observables.
↗ OpenCHECK: Malware-associated IPs, domains, URLs, hashes and IOC confidence/context.
USE FOR: Malware and botnet IOC hunting and infrastructure pivots.
↗ OpenCHECK: Pulses, IOCs, threat reports and community-contributed context.
USE FOR: IOC enrichment, campaign pivots and threat-hunting leads.
↗ OpenCHECK: Malicious URLs, payloads, hosting information and malware associations.
USE FOR: Phishing, malware-delivery and suspicious-URL investigations.
↗ OpenCHECK: IP abuse reports, confidence scores, categories and historical reports.
USE FOR: Source-IP context during scanning, brute-force and suspicious connection investigations.
↗ OpenCHECK: Structured threat intelligence, events, attributes and relationships.
USE FOR: Sharing and correlating structured threat intelligence across teams.
↗ OpenMap what the adversary did to techniques, evidence sources and detection opportunities.
CHECK: Tactics, techniques, sub-techniques, software and procedure examples.
USE FOR: TTP mapping, threat hunting hypotheses and detection coverage analysis.
↗ OpenCHECK: Threat indicators, analytics, workbooks and intelligence integrations.
USE FOR: Connecting threat intelligence to SIEM investigations and detections.
↗ OpenCHECK: Which logs, endpoint events, identity records and network telemetry can evidence a technique.
USE FOR: Turning intelligence into concrete detection and hunting requirements.
↗ OpenPivot from a sample or hash into family, behavior, infrastructure and related indicators.
CHECK: Malware samples, hashes, tags, family information and related intelligence.
USE FOR: Malware-sample research and hash-based investigation pivots.
↗ OpenCHECK: File detections, relationships, behavior, contacted domains/IPs and related samples.
USE FOR: Sample triage and connecting a file to infrastructure.
↗ OpenCHECK: Malware, infrastructure relationships, threat reports and campaign context.
USE FOR: Connecting malware observations to broader campaigns and actors.
↗ OpenA compact reference set for vulnerability, adversary, IOC and malware intelligence.
CHECK: Vulnerabilities added to the Known Exploited Vulnerabilities catalog.
USE FOR: Prioritizing vulnerability investigations where exploitation is documented.
↗ OpenCHECK: CVE records, affected products, references and vulnerability metrics.
USE FOR: Vulnerability enrichment and product/CVE research.
↗ OpenCHECK: Threat intelligence, security research and current threat landscape reporting.
USE FOR: Microsoft ecosystem research and defensive context.
↗ Open