Skip to main content
FREE SOC UTILITY • ZERO TELEMETRY

SOC Threat Indicator Workbench & IOC Defanger

Parse raw triage logs, incident reports, and email headers into clean, categorized Indicators of Compromise. Safely defang indicators before sharing on ticketing platforms, cross-reference against our live campaign database, and export one-click firewall EDL blocklists.

100% Local & Private
Zero network logs or uploads
Live Threat Cross-Check
Matches 840+ verified IOCs
Firewall Ready
EDL, Markdown & CSV exports

SOC Threat Indicator Workbenchv2.1 Client-Side

Paste raw incident notes, C2 telemetry, or firewall logs to extract, defang, and cross-reference indicators.

Input Raw Text, Firewall Logs, or Incident Notes:
Indicators Extracted:0

Ready to parse. Paste threat indicators or click "Load Sample Incident Log" above.

Zero-Telemetry Privacy Guarantee: All log parsing, regex extraction, and defanging takes place entirely within your local browser runtime. Indicators and logs are never uploaded or retained.

Why DFIR Analysts Defang Indicators

During security investigations, raw Indicators of Compromise (IOCs)—such as malicious IP addresses, phishing domains, and C2 callback URLs—are frequently shared across communications channels: Slack, Microsoft Teams, Jira tickets, and internal emails.

Posting active, clickable hyperlinks creates serious operational hazards:

  • Accidental Execution: Analysts or non-technical stakeholders may click the link, triggering drive-by downloads or credential harvesters.
  • Bot & Crawler Alerts: Modern enterprise chat apps automatically prefetch link previews (unfurling), pinging the attacker's infrastructure and tipping off threat actors that they have been discovered.
  • Proxy & Mail Gateway Drops: Security gateways and mail scanners may quarantine or block internal incident tickets because they contain active weaponized domains.

Standard Defanging Conventions

Artifact TypeRaw (Dangerous)Defanged (Safe)
HTTP URLhttp://malicious.xyzhxxp://malicious[.]xyz
HTTPS URLhttps://c2.evil.com/pinghxxps://c2[.]evil[.]com/ping
IPv4 Address185.196.11.14185[.]196[.]11[.]14
Domaintencent38003.comtencent38003[.]com
Emailbad@phish.orgbad[@]phish[.]org
HashesSHA256 / MD5Immutable (Unchanged)

Exporting to Enterprise Firewall EDLs (External Dynamic Lists)

When responding to active zero-day campaigns, perimeter engineers require formatted blocklists to inject into next-generation firewalls. The Firewall EDL export strips private RFC 1918 addresses, refangs indicators into clean networking syntax, and creates an import-ready plain-text stream.

Palo Alto Networks

Import as IP List or URL List under Objects > External Dynamic Lists. Configurable for automated 5-minute polling.

Fortinet FortiGate

Use Security Fabric > Fabric Connectors > Threat Feeds (IP Address / Domain Name) with automated policy enforcement.

pfSense / OPNsense

Feed directly into pfBlockerNG-devel IPv4 / DNSBL custom lists with automated cron update intervals.

Frequently Asked Questions (FAQ)

Are indicators uploaded to CyberNewsAI servers?

No. The parser runs 100% client-side in your local browser runtime. Indicator matching is performed against an in-memory index preloaded with the page. No sensitive triage notes ever leave your machine.

Can I refang indicators that were already defanged?

Yes. Toggle to "Direct Defang / Refang" mode or set display values to "Raw / Refanged". The engine strips brackets like [.] and translates hxxp back into standard http:// format.

Why does the extractor detect RFC 1918 Private IPs?

Incident notes often contain internal gateway IPs (192.168.1.1, 10.0.0.5). We label them distinctly and offer a one-click "Hide RFC 1918 IPs" toggle so you never accidentally push internal subnets to perimeter firewalls.

How often is the threat intelligence index refreshed?

The cross-referencing index is updated hourly as new threat briefs, zero-day CVE advisories, and verified DFIR campaigns are cataloged by the CyberNewsAI research directorate.