AWS Route53: Add DNS query log example for alerted queries and disposition fields
Summary
Updates the Route 53 Global Resolver DNS query log documentation to add an 'Access alert' OCSF log example and new disposition/disposition_id fields, and renames/updates several log fields (protocol_ver_id, firewall_domain_list_id, token_expiration_time, token_ttl_days) in the allowed and denied examples.
Security assessment
The change documents the OCSF log schema for DNS query logging, including allowed, denied, and alerted dispositions, which supports security monitoring and audit visibility. It is documentation of a logging/visibility feature rather than a fix for a specific vulnerability.
Evidence
+ "disposition": "Alert",
Diff
diff --git a/Route53/latest/DeveloperGuide/gr-gain-visibility-into-dns-activity.md b/Route53/latest/DeveloperGuide/gr-gain-visibility-into-dns-activity.md index 778d87b..47149b2 100644 --- a//Route53/latest/DeveloperGuide/gr-gain-visibility-into-dns-activity.md +++ b//Route53/latest/DeveloperGuide/gr-gain-visibility-into-dns-activity.md @@ -47 +47 @@ DNS query logs use the Open Cybersecurity Schema Framework (OCSF), which provide -Route 53 Global Resolver DNS query logs follow the OCSF schema structure, providing detailed information about each DNS query, response, and security action. The following examples show the log format for allowed and denied queries. +Route 53 Global Resolver DNS query logs follow the OCSF schema structure, providing detailed information about each DNS query, response, and security action. The following examples show the log format for allowed, denied, and alerted queries. @@ -49 +49 @@ Route 53 Global Resolver DNS query logs follow the OCSF schema structure, provid -#### Route 53 Global Resolver DNS log - Access allowed example +#### Route 53 Global Resolver DNS log - Example – Access allowed @@ -75 +75 @@ This example shows a DNS query that was allowed through firewall rules. The log - "protocol_ver": "", + "protocol_ver_id": 4, @@ -77,0 +78,2 @@ This example shows a DNS query that was allowed through firewall rules. The log + "disposition": "Allowed", + "disposition_id": 1, @@ -102,4 +104,2 @@ This example shows a DNS query that was allowed through firewall rules. The log - "token_id": "t-a1b2c3d4fexample", - "token_name": "device-123456", - "token_expiration": "1789419206", - "access_source_cidr": "3.3.3.0/24", + "firewall_domain_list_id": "fdl-a1b2c3d4fexample", + "access_source_cidr": "3.3.3.0/24" @@ -132,4 +131,0 @@ This example shows a DNS query that was allowed through firewall rules. The log - "src_endpoint": { - "ip": "3.3.3.3", - "port": 28276 - }, @@ -144 +140 @@ This example shows a DNS query that was allowed through firewall rules. The log -#### Route 53 Global Resolver DNS log - Access denied example +#### Route 53 Global Resolver DNS log - Example – Access denied @@ -172,0 +169,2 @@ This example shows a DNS query that was blocked by firewall rules. The log inclu + "disposition": "Blocked", + "disposition_id": 2, @@ -187 +185,2 @@ This example shows a DNS query that was blocked by firewall rules. The log inclu - "token_id": "t-a1b2c3d4fexample", + "firewall_domain_list_id": "fdl-a1b2c3d4fexample", + "token_id": "at-a1b2c3d4fexample", @@ -189,2 +188,2 @@ This example shows a DNS query that was blocked by firewall rules. The log inclu - "token_expiration": "1789419206", - "access_source_cidr": "3.3.3.0/24", + "token_expiration_time": "1789419206", + "token_ttl_days": 134 @@ -225,0 +225,91 @@ This example shows a DNS query that was blocked by firewall rules. The log inclu +#### Route 53 Global Resolver DNS log - Example – Access alert + +This example shows a DNS query that triggered an alert rather than being blocked. The log includes the `disposition` value of `Alert`, indicating the query was allowed through and resolved, but flagged for review. + + + { + "action_id": 1, + "action_name": "Allowed", + "activity_id": 6, + "activity_name": "Traffic", + "category_name": "Network Activity", + "category_uid": 4, + "class_name": "DNS Activity", + "class_uid": 4003, + "cloud": { + "provider": "AWS", + "region": "eu-west-1", + "account": { + "uid": "123456789012" + } + }, + "connection_info": { + "direction": "Inbound", + "direction_id": 1, + "protocol_name": "tcp", + "protocol_num": 6, + "protocol_ver_id": 4, + "uid": "b7e4a1f2c6d84e39" + }, + "disposition": "Alert", + "disposition_id": 19, + "duration": 1, + "end_time": 1761358379996, + "answers": [{ + "rdata": "3.3.3.3", + "type": "A", + "class": "IN", + "ttl": 300 + }, + { + "rdata": "3.3.3.4", + "type": "A", + "class": "IN", + "ttl": 300 + }], + "src_endpoint": { + "ip": "3.3.3.2", + "port": 58492 + }, + "enrichments": [{ + "name": "global-resolver", + "value": "gr-a1b2c3d4fexample", + "data": { + "dns_view_id": "dnsv-a1b2c3d4fexample", + "firewall_rule_id": "fr-a1b2c3d4fexample", + "firewall_domain_list_id": "fdl-a1b2c3d4fexample", + "access_source_cidr": "3.3.3.2/32" + } + }], + "message": "", + "metadata": { + "version": "1.2.0", + "product": { + "name": "Global Resolver", + "vendor_name": "AWS", + "feature": { + "name": "DNS" + } + } + }, + "query": { + "hostname": "example.com.", + "class": "IN", + "type": "A", + "opcode": "Query", + "opcode_id": 0 + }, + "query_time": 1761358379995, + "rcode": "NOERROR", + "rcode_id": 0, + "response_time": 1761358379995, + "severity": "Informational", + "severity_id": 1, + "start_time": 1761358379995, + "status": "Success", + "status_id": 1, + "time": 1761358379995, + "type_name": "DNS Activity: Traffic", + "type_uid": 400306 + } +