1200KM / detection
Detection workspace for T1590 Gather Victim Network Information: 2 Sigma sources, 1 Atlas concepts and 1 anomaly models. No live detection validation.
MATCH(dns_zone_transfer_request OR repeated_public_dns_enumeration) AND source_ip NOT_IN approved_dns_admins -> ALERTComparison unit: requesting client.
Expected behavior: clients request a limited distribution of record types and names.
Deviation: rare query types, unusually broad name coverage, or a sudden increase in authoritative queries.
Much of this activity may have a very high occurrence and associated false positive rate, as well as potentially taking place outside the visibility of the target organization, making detection difficult for defenders. Detection efforts may be focused on related stages of the adversary lifecycle, such as during Initial Access.
No reviewed association in this snapshot.
These are explicit actor-to-technique associations in the existing Threat Matrix snapshot, not attribution of an event or proof that a detector identifies the actor. No tool-to-actor relationship is inferred.
Collection configuration and event examples · Anomaly models and design worksheet · Tools and documented software · Simulation procedures · Offline synthetic collection check
Exact source tags are not semantic relevance verdicts. Review actual rule conditions and observation points; imported rules are not backend-compiled or live-validated.
Curated research views reached through an exact source technique, a catalog model, or a reviewed collection reference. These are navigation associations, not claims of detector effectiveness or sensor equivalence.
Telemetry contracts · Maintained query examples · Validation and blind spots
Pinned research references. No browser attack runner or production-validated detector is asserted. Imported procedures remain unvalidated; any bounded lab evidence has its own scope. ATT&CK / Atomic provenance · Detection provenance.