Platform Documentation

H3AD-SEC Reference

A full usage guide for every module and tool across the H3AD-SEC platform. Start with the quick-start flows or jump directly to any tool reference below.

Getting Started

Platform Overview

H3AD-SEC is a browser-based operational cyber defense platform built by a SOC analyst for day-to-day detection, investigation, and hunting work. Every tool runs client-side — nothing is stored server-side unless explicitly noted (DNSCOPE uses a managed Vercel backend for DNS lookups).

The platform is organized into seven modules, each covering a distinct SOC workflow. Most tools take raw text or a single artifact as input and return enriched, structured output.

Use Case Flows

These are the most common investigation patterns across the platform. Each flow chains multiple tools in order.

PHISHING Phishing Triage
1 MAILSCOPE — analyze email headers, check SPF/DKIM/DMARC, identify spoofing.
2 PARSE-X — paste email body, extract all IOCs (URLs, IPs, domains, hashes).
3 X-VERDIKT — deep-enrich extracted IPs against 10 sources, get verdict score.
4 PHISHOPS — open investigation tracker, log IOCs, follow 7-step workflow.
5 PHISHBOOK — reference playbook for containment, escalation, and reporting steps.
IP/DOMAIN IOC Deep-Dive
1 X-VERDIKT — enrich the IP across VT, AbuseIPDB, OTX, Shodan, GreyNoise, and more.
2 DNSCOPE — map the domain's infra: DNS, PDNS, subdomains, ASN, CDN/WAF detection.
3 PIVEX — build a pivot graph linking the IP to related domains and infrastructure.
4 ATTMAP-AI — map the behaviors to MITRE ATT&CK techniques for context.
HUNT Threat Hunt
1 HYPOS — browse or create a hypothesis, define scope and data sources.
2 TRACEPULSE — pull CVE or campaign-tied query packs matching your hypothesis.
3 QUICKTRACE — run baseline triage queries across auth, network, endpoint, cloud.
4 PIVEX — visualize discovered IOC relationships in a pivot graph.
DETECT Detection Engineering
1 TRACERULES — check if a detection rule for the technique already exists.
2 QUERYCRAFT-AI — describe the behavior in plain English to generate a KQL/Sigma/SPL query.
3 ATTMAP-AI — map your detection to ATT&CK technique IDs and tactic chain.
4 INSIGHT-AI — generate a full analyst runbook for the alert once deployed.

Quick Reference

I want to... Use this tool Input
Enrich a suspicious IP, domain, URL, or hashX-VERDIKTIP, domain, URL, or hash
Extract all IOCs from a paste/log/emailPARSE-XRaw text
Map a domain's infrastructureDNSCOPEDomain or IP
Analyze email headers for spoofingMAILSCOPERaw email headers
Generate an incident runbook fastINSIGHT-AIAlert name + context
Build a KQL / Sigma / SPL query from descriptionQUERYCRAFT-AIPlain English description
Understand why an alert is a false positiveFPLENS-AIAlert name + FP context
Map behaviors to MITRE ATT&CKATTMAP-AIThreat description or IOCs
Reconstruct an attack timelineCHRONO-AIEvent sequence
Get a malware behavior briefMALBRIEF-AIMalware name or description
Find AI prompts for SOC tasksPROMPTVAULTBrowse by category
Browse or copy detection queriesTRACERULESBrowse by tactic/technique
Create or track a hunt hypothesisHYPOSHypothesis entry
Visualize IOC pivot relationshipsPIVEXNodes and edges
Find CVE or campaign-tied hunting queriesTRACEPULSECVE ID or campaign name
Run daily triage baseline queriesQUICKTRACEBrowse by category
Track a phishing investigation step-by-stepPHISHOPSPhishing alert details
Write a shift handover reportSHIFTLOGShift notes and incidents
Analyze Windows registry for persistenceREGSCOPERegistry key paths
Follow phishing IR procedurePHISHBOOKNavigate 9 phases

H3AD-X

Threat exchange and IOC enrichment. Four tools covering multi-type IOC enrichment (IP, domain, URL, hash), artifact extraction, domain infrastructure mapping, and email header analysis. All are client-side except DNSCOPE, which uses a managed backend for live DNS queries.
X-VERDIKT LIVE Open ↗
Input IP address, domain, URL, or file hash (MD5/SHA1/SHA256). Defanged IOCs supported. Bulk input accepted — one per line or comma-separated. Output Per-type verdict score (0–100). IP: VT(30) + AbuseIPDB(40) + OTX(10) + ThreatFox(20). Domain: VT(50) + URLScan(20) + OTX(10) + ThreatFox(20). URL: VT(50) + URLScan(20) + OTX(10) + URLhaus(20). Hash: VT(25) + MalwareBazaar(10) + OTX(10) + ThreatFox(10) + HybridAnalysis(20) + FileScan(25). Raw data per source. Sources VirusTotal, AbuseIPDB, OTX, ThreatFox, URLScan, URLhaus, MalwareBazaar, HybridAnalysis, FileScan.io, Shodan, IPLocate — 11 total; active sources vary by IOC type.
How to use
1Paste one or more IOCs — IP, domain, URL, or hash — one per line or comma-separated. Defanged formats (e.g., 1[.]2[.]3[.]4) are accepted.
2Each IOC returns a verdict score (0–100). Scores above 70 are high-risk; 40–70 are moderate. Active sources shown depend on the IOC type.
3Expand each source panel for raw API data. For IP lookups, supplementary flags (Tor, VPN, proxy, hosting) appear from IPLocate.
4Copy the verdict summary for your ticket or PHISHOPS tracker.
PARSE-X LIVE Open ↗
Input Any raw text: log lines, email bodies, threat reports, SIEM exports. Output Flat table of extracted artifacts by type. Export as CSV, JSON, or Markdown. Types IPv4, IPv6, domain, URL, email, MD5, SHA1, SHA256, CVE, ASN, MAC, registry key, file path, user agent, base64, CIDR, phone, Bitcoin address.
How to use
1Paste raw text into the input area. Extraction runs automatically on input.
2Use the group filters at the top to show only specific artifact types.
3Click Export to download as CSV, JSON, or Markdown for your ticket.
DNSCOPE LIVE Open ↗
Input Domain name or IP address. Output DNS records, passive DNS history, subdomains, co-hosted domains, ASN/WHOIS, CDN/WAF/cloud detection, certificate transparency history. Backend Managed Vercel serverless backend handles live DNS queries — requires internet access.
How to use
1Enter the domain or IP in the input field and click Map.
2Each data layer loads in its own collapsible section. Expand the ones relevant to your investigation.
3CDN/WAF/cloud tags appear as chips. Use these to gauge whether the IP is a shared hosting address before taking action.
4Co-hosted domain results are useful for pivoting to related infrastructure via PIVEX.
MAILSCOPE LIVE Open ↗
Input Raw email headers. In Gmail: three-dot menu, Show original. In Outlook: File, Properties, Internet headers. Output SPF / DKIM / DMARC pass/fail status, full hop chain with IP and latency, spoofing risk flags, copy-ready export.
How to use
1Open the email in its original/raw form. Copy all header text (everything above the body).
2Paste the headers into MAILSCOPE. Analysis runs immediately.
3Review the SPF/DKIM/DMARC status chips. A fail here means authentication did not pass — high spoofing indicator.
4Trace the hop chain for unexpected relay servers or geographic anomalies. Copy the analysis for your ticket.

H3AD-AI

Seven AI-powered tools covering runbook generation, detection query building, false positive analysis, ATT&CK mapping, timeline reconstruction, malware briefing, and prompt management. All tools use Gemini AI via client-side calls — you supply your own API key in the tool settings.

API key required. All H3AD-AI tools call the Gemini API from your browser. Your key is stored in localStorage and never sent to any H3AD-SEC server. Get a free key at aistudio.google.com and paste it into the settings panel on any H3AD-AI tool.

INSIGHT-AI LIVE Open ↗
Input Alert name, SIEM type (Sentinel / Splunk / XDR), and optional investigation context. Output 10-section runbook: hypothesis, scope queries (DETECT/HUNT prefix format), triage steps, escalation criteria, MITRE mapping (technique + sub-technique), FP considerations, containment actions, and IR notes. Three sections auto-populate from alert metadata.
How to use
1Enter the alert name. Add any known context (user, asset, behavior observed).
2Select your SIEM from the dropdown. This tailors the query syntax in the output.
3Click Generate. The runbook builds section by section.
4Copy individual sections or the full runbook for your case management tool.
QUERYCRAFT-AI LIVE Open ↗
Input Plain English description of the behavior to detect. Example: "detect PowerShell downloading a file from the internet using Invoke-WebRequest". Output Query in the selected language with explanation, field references, and tuning notes.
How to use
1Describe the detection goal clearly. Include the data source if known (e.g., "from Sysmon event ID 1").
2Select the target query language: KQL (Sentinel), Sigma (generic), or SPL (Splunk).
3Generate. Review the query and the tuning notes before deploying.
FPLENS-AI LIVE Open ↗
Input Alert name, rule logic (optional), observed context (user, asset, behavior), and reasons you suspect it is a false positive. Output FP risk score, root-cause classification, whitelist/exclusion suggestions, and tuning recommendations.
How to use
1Paste the alert name and any rule logic you have access to.
2Describe what happened: who triggered it, what the asset does normally, why it looks benign.
3Generate. The output includes specific exclusion patterns you can add to the rule.
ATTMAP-AI LIVE Open ↗
Input Threat description, observed behaviors, IOC context, or raw alert text. Output Tactic chain, technique IDs (T1xxx), sub-technique IDs (T1xxx.xxx), and short reasoning per mapping.
How to use
1Paste or type the threat behavior description. More detail produces more precise mappings.
2Generate. Review the tactic chain to understand the full attack flow, not just the detection point.
3Copy technique IDs for your runbook, ticket, or HYPOS entry.
CHRONO-AI LIVE Open ↗
Input Event sequence: log excerpts, alert titles with timestamps, or a text description of what happened in order. Output Structured timeline with stage labels (Initial Access, Execution, Persistence, etc.), timestamps, and MITRE technique tags per event.
How to use
1Input events in order, one per line or as a paragraph. Include timestamps if available.
2Generate. The timeline output adds ATT&CK stage context to each event.
3Export the timeline for your IR report or post-incident review.
MALBRIEF-AI LIVE Open ↗
Input Malware name (e.g., Cobalt Strike, QakBot), SHA256 hash, or a description of observed behavior. Output Behavior brief: capabilities, persistence mechanisms, C2 patterns, IOC list, MITRE technique mapping, and hunting queries.
How to use
1Input a known malware name for a general brief, or paste a hash or behavioral log for context-specific output.
2Generate. Review the capability list and hunting queries sections first for immediate action items.
3Copy hunting queries directly into TRACERULES or your SIEM.
PROMPTVAULT LIVE Open ↗
Input Browse by category: detection engineering, threat hunting, incident response, threat intelligence, reporting. Output Copy-ready prompts optimized for Gemini, ChatGPT, or Claude. No generation needed — pure reference library.
How to use
1Browse categories or search by keyword for the task you need a prompt for.
2Click a prompt to expand it. Edit the placeholder fields (marked in brackets) with your specific context.
3Copy and paste into your AI tool of choice. Prompts are designed to produce direct, analyst-ready output.

H3AD-DETECT

Detection rule and query arsenal for SIEM deployment. Currently one live tool; additional tools are planned.
TRACERULES LIVE Open ↗
Input Filter by query language, ATT&CK tactic, technique, or keyword search. Output Rule name, description, ATT&CK mapping, confidence rating, and copy-ready query code. Data source QUERYVAULT repo at github.com/h3ad-sec/QUERYVAULT under detections/kql, detections/sigma, detections/xql.
How to use
1Use the language filter to select KQL, Sigma, or XQL based on your SIEM.
2Filter by tactic (e.g., Persistence, Execution) or search by technique ID or keyword.
3Select a rule. Review the confidence rating and test conditions before deploying.
4Copy the query. For Sigma rules, convert to your SIEM format using sigma-cli or pySigma before deploying.

H3AD-HUNT

Structured threat hunting tools: hypothesis management, IOC pivot visualization, and CVE or campaign-tied query pack delivery.
HYPOS LIVE Open ↗
Input Browse curated entries or fill in a new hypothesis form: hypothesis statement, ATT&CK technique, required data sources, priority. Output Structured hypothesis card with tactic/technique tags, data source checklist, and analytics view showing technique distribution and priority breakdown.
How to use
1Browse the curated hypothesis library. Filter by tactic or technique to find hypotheses relevant to your hunt.
2Tag search lets you find hypotheses by ATT&CK sub-technique or data source type.
3To create a new entry, fill the hypothesis form and save it to your session.
4Use the analytics tab to review coverage across tactics before beginning your hunt.
PIVEX LIVE Open ↗
Input Node definitions (IOC type + value) and edge definitions (relationship type between nodes). Output Interactive force-directed graph with dark-ring nodes, colored typed edges, and highlight/dim on selection. Supports up to 36 nodes and 168+ edges.
How to use
1Add nodes for each IOC or infrastructure element: type the value and select the node type (IP, domain, hash, etc.).
2Define edges between nodes: select source, target, and relationship type (resolves to, communicates with, drops, etc.).
3Click a node to highlight it and dim unrelated connections. Useful for tracing a specific IOC's relationships.
4Note: node positions do not animate on click by design. Only highlight/dim behavior triggers on selection.
TRACEPULSE LIVE Open ↗
Input Browse by CVE ID, threat actor, or campaign name. Output Query pack containing KQL/Sigma/XQL queries scoped to the selected threat, with context on exploitation behavior and MITRE mapping. Data source QUERYVAULT repo under pulse/2025/ (pulse-manifest.json).
How to use
1Search or browse for the CVE or campaign relevant to your hunt.
2Open the pack. Review the context section to understand what the queries detect and what log sources they need.
3Copy the queries in your SIEM's format and run them. Cross-reference any hits with X-VERDIKT for IP enrichment.

H3AD-OPS

Daily SOC workflow tools: baseline triage queries, shift handover reporting, and phishing investigation tracking. Built for shift analysts who need fast, repeatable procedures.
QUICKTRACE LIVE Open ↗
Input Browse by category: Authentication, Network, Endpoint, Cloud. Output Copy-ready KQL queries with context on what each query surfaces and when to use it. Data source QUERYVAULT repo under quicktrace/ (quicktrace-manifest.json).
How to use
1At shift start, run the auth and endpoint baseline queries to establish a normal baseline.
2During investigation, switch to the relevant category. Network queries help trace lateral movement; cloud queries surface IAM anomalies.
3Click Copy on any query. Paste directly into your SIEM. Adjust time ranges and entity filters as needed.
SHIFTLOG LIVE Open ↗
Input Form fields: active incidents, escalations, priority items, pending actions, notes for incoming shift. Output Formatted handover report, copy-ready for email, chat, or ticketing system.
How to use
1Fill in each section before your shift ends. Keep incident descriptions brief but specific.
2Generate the report. Review it for any missing context before handing over.
3Copy the report and paste into your team communication channel or case management tool.
PHISHOPS LIVE Open ↗
Input Phishing alert details entered step by step as you investigate. Output Completed 7-step investigation record with all IOCs logged, exportable summary for ticketing. Persistence State saved to localStorage. Investigations persist across page reloads until manually cleared.
How to use
1Open PHISHOPS when a phishing alert fires. Start a new investigation and name it by ticket or incident ID.
2Work through each of the 7 steps in order. Each step has a dedicated IOC input for what you find at that stage.
3The live IOC aggregator collects all IOCs entered across steps into a single list as you go.
4Export the final summary for your case or pass to PHISHBOOK for escalation procedure reference.

H3AD-DF

Digital forensics tools focused on Windows artifact analysis and malware behavior briefing. MALBRIEF-AI appears here and in H3AD-AI as it serves both contexts.
REGSCOPE LIVE Open ↗
Input Registry key paths (e.g., HKCU\Software\Microsoft\Windows\CurrentVersion\Run) or raw exported .reg content. Output Persistence classification, known-bad pattern flags, ATT&CK technique tags (T1547, T1546, etc.), and hunting context.
How to use
1Export registry keys from the suspect system using reg export or collect via EDR artifact pull.
2Paste the content into REGSCOPE. It scans for persistence keys across Run, RunOnce, Services, Scheduled Tasks, and other known locations.
3Review flagged entries. Known-bad entries are highlighted with technique IDs for your IR report.

MALBRIEF-AI is also part of H3AD-DF for forensic malware analysis. See the full entry under H3AD-AI / MALBRIEF-AI.

H3AD-IR

Structured incident response procedures. Currently covers phishing IR with a full 9-section playbook.
PHISHBOOK LIVE Open ↗
Input No input required. PHISHBOOK is a reference document. Navigate to the relevant phase based on where you are in the investigation. Output Phase-specific procedures, decision points, pre-built KQL queries, and links to enrichment tools (MAILSCOPE, X-VERDIKT, DNSCOPE). Keyboard navigation, progress tracking, and print export.
How to use
1Open PHISHBOOK at the start of a phishing incident. Use the 9-phase sidebar to jump to your current stage.
2Follow the decision tree in each phase. Embedded tool links open the relevant H3AD-SEC tool directly.
3Copy the KQL templates from each phase and adapt them to your environment. Pre-built queries cover header analysis, URL reputation, attachment hash lookups, and user activity tracing.
4Use keyboard shortcuts (J/K or arrow keys) to navigate phases quickly. Mark phases complete to track progress.
5Print or export the playbook for offline reference or to attach to your incident report.

H3AD-LEARN

Browser-native security training for SOC analysts and detection engineers. Each module is structured as chapters with reading, technique breakdowns, and detection query examples. Progress persists in localStorage.
Threat Hunting Module LIVE Open ↗
Chapters 9 — PEAK framework, TaHiTI methodology, Admiralty scoring, KQL/Sigma query construction, hypothesis development, advanced pivot techniques. Format Chapter-by-chapter reading with embedded code examples. Progress tracked per chapter.
How to use
1Open H3AD-LEARN and select the Threat Hunting module from the module selector.
2Work through chapters in order. Each chapter builds on the prior one — start from Chapter 1 if you're new to structured hunting.
3Copy the embedded KQL and Sigma examples directly into your SIEM for practice or production use.
LOLBAS Module LIVE Open ↗
Chapters 8 — certutil, mshta, regsvr32, wscript/cscript, signed binary tradecraft, detection query construction, APT campaign examples. Format Technique breakdowns paired with detection queries for each binary. Covers both offensive technique and defensive detection perspective.
How to use
1Select the LOLBAS module from the module selector.
2Read each chapter's technique breakdown first. Understand how the binary is abused before looking at detection.
3Use the embedded detection queries as starting points. Adapt field names to match your SIEM's data model.
VISITORS