← Cortex XDR detections
Cortex XDR · Indicator
Traffic to known C2 IP 43.136.175.43
- Correlation
- set the rule's MITRE tactic to command-and-control and technique to T1071
- severity
- high
- confidence
- 100/100
- generated
- 19 Nov 2026
Connection to an IP tracked by skopnix as Cobalt Strike C2.
False-positive notes
Scoped to one indicator with skopnix confidence 100/100 from 2 independent sources; checked against RFC1918/reserved space, CDN / cloud / scanner ranges and top-site lists (public known-good lists), sinkholes, internet-noise reputation when enriched, and skopnix's benign-infrastructure list. Threat-feed evidence: listed by 2 independent non-scanner sources, seen within the last 90 days. Re-validate against last_seen before blocking: infrastructure is re-assigned.
References
preset = network_story| filter action_remote_ip in ("43.136.175.43")| fields agent_hostname, action_local_ip, action_remote_ip, action_remote_port, action_app_id, _time| sort desc _timeskopnix-cortex-ioc-ip-43-136-175-43-9b66eff7.xql
How to deploy on Cortex XDR
- Step 1
- Paste the XQL into Incident Response > Investigation > Query Builder > XQL Search.
- Step 2
- To alert, save it as a Correlation Rule and set the MITRE tactic and technique printed with the rule.
- Step 3
- Schedule it on the interval you hunt at; keep the fields stage for the alert's columns.
- Check
- CVE rules read PAN-OS URL logs (panw_ngfw_url_raw), which need the NGFW integration and, for HTTPS, decryption.