Open-source AI Security Operations Center: alert fusion, LLM-agent triage, MITRE ATT&CK investigation, and a replayable decision ledger for every agent step. Self-hostable, runs with no API keys, MIT licensed. Ships an MCP server for Claude, Cursor and Continue.
Python agentic-aiai-securityalert-triageblue-teamcybersecuritydetection-engineeringincident-responselanggraphllm-agentsmcpmitre-attackmodel-context-protocolpurple-teamsecurity-operationsself-hostedsiemsoarsocthreat-detectionthreat-intelligence
id: hunt-dns-over-https-to-unapproved-resolver
name: DNS-over-HTTPS to a resolver outside the approved set
description: |
Encrypted DNS is normal and increasingly default. Using a resolver the organisation has not approved takes name resolution out of view of every DNS control.
version: 1.0.0
severity: medium
category: network
tags:
- mitre.attack.t1572
- hunt.network
log_sources:
- proxy
- firewall
schedule:
enabled: true
interval_minutes: 60
jitter_seconds: 60
hypothesis:
question: |
Did any host resolve names through an unapproved encrypted resolver?
indicators:
- field: "source"
equals: "proxy"
- field: "url_path"
equals: "/dns-query"
- field: "resolverIsApproved"
equals: false
expected:
positive_incident_id: INC-HUNT-042
positive_template_id: hunt-dns-over-https-to-unapproved-resolver
min_match_score: 0.8
negative_incident_id: INC-HUNT-042-NEG
# The negative inverts resolverIsApproved, the clause this hunt is about,
# and holds every other field constant. A negative that differed in the
# log source would pass without testing anything.
references:
- https://attack.mitre.org/techniques/T1572/
author: AiSOC
created: '2026-09-27'
modified: '2026-09-27'