defensive-xxe

Detect and triage XXE vulnerabilities in XML processing pipelines.

1|Updated Apr 27, 2026
One-click install
npx skills add https://github.com/riparino/Claude-Cyber --skill defensive-xxe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: defensive-xxe
Source: https://github.com/riparino/Claude-Cyber/tree/main/Claude-Blue/Skills/defensive-xxe
Command: npx skills add https://github.com/riparino/Claude-Cyber --skill defensive-xxe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

XML processing often exposes applications to XXE vulnerabilities via DOCTYPE and ENTITY definitions. This skill provides a structured approach to detect and triage XXE indicators in XML inputs, enabling faster remediation.

Core Features & Use Cases

  • Detection Coverage: identifies DOCTYPE/ENTITY usage, OOB callback patterns, and file:// based read attempts.
  • Threat Coverage: includes Sigma rules for XML injection, YARA rules for XXE payloads, and KQL for Azure WAF and MDE network telemetry.
  • Use Case: SOC teams can harden XML parsers and set up monitoring to alert on XXE indicators during XML processing.

Quick Start

Load the XXE detection methodology into the XML processing pipeline to identify DOCTYPE/ENTITY patterns and OOB callbacks.

Frequently Asked Questions about defensive-xxe

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect XXE vulnerabilities in XML processing pipelines?

Detect XXE vulnerabilities by identifying DOCTYPE and ENTITY definitions, out-of-band callback patterns, and file read attempts. This approach applies Sigma rules, YARA patterns, and KQL queries to triage malicious XML inputs in web services and applications.

What Sigma and YARA rules help identify XML External Entity injection payloads?

Sigma rules for XML injection and YARA patterns for XXE payloads identify DOCTYPE and ENTITY usage. These rules detect malicious XML inputs, enabling SOC teams to monitor and alert on XML External Entity injection attempts during processing.

How do I monitor Azure WAF and MDE network telemetry for XXE callbacks?

Monitor Azure WAF and MDE network telemetry for XXE callbacks using KQL queries. These queries identify out-of-band callback patterns and file read attempts, providing visibility into XML External Entity exploitation across web services and network traffic.

Does this XXE detection approach work for both web services and applications that parse XML?

Yes, this XXE detection applies to web services and applications that parse XML. It triages XML inputs by identifying DOCTYPE and ENTITY patterns, OOB callbacks, and file read attempts, enabling SOC teams to harden XML parsers.

What is the best way to harden XML parsers against DOCTYPE and ENTITY definitions?

The best way to harden XML parsers against DOCTYPE and ENTITY definitions is to apply structured detection rules. By deploying Sigma, YARA, and KQL queries, SOC teams can identify XXE indicators and implement monitoring to alert on malicious XML processing.

Why should I use KQL queries to triage XML External Entity attacks?

Use KQL queries to triage XML External Entity attacks because they query Azure WAF and MDE network telemetry. This identifies out-of-band callbacks and file read attempts, enabling SOC teams to detect and respond to XXE vulnerabilities across network infrastructure.