You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/detections/prebuilt-rules/rule-details/abnormally-large-dns-response.asciidoc
+9-6Lines changed: 9 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,11 +33,11 @@ Specially crafted DNS requests can manipulate a known overflow vulnerability in
33
33
* Threat Detection
34
34
* Lateral Movement
35
35
36
-
*Version*: 5 (<<abnormally-large-dns-response-history, version history>>)
36
+
*Version*: 6 (<<abnormally-large-dns-response-history, version history>>)
37
37
38
38
*Added ({stack} release)*: 7.10.0
39
39
40
-
*Last modified ({stack} release)*: 7.16.0
40
+
*Last modified ({stack} release)*: 8.1.0
41
41
42
42
*Rule authors*: Elastic
43
43
@@ -63,16 +63,16 @@ also known as [SigRed](https://www.elastic.co/blog/detection-rules-for-sigred-vu
63
63
- This specific rule is sourced from network log activity such as DNS or network level data. It's important to validate
64
64
the source of the incoming traffic and determine if this activity has been observed previously within an environment.
65
65
- Activity can be further investigated and validated by reviewing available corresponding Intrusion Detection Signatures (IDS) alerts associated with activity.
66
-
- Further examination can be made by reviewing the `dns.question_type` network fieldset with a protocol analyzer, such as Zeek, Packetbeat, or Suricata, for `SIG` or `RRSIG` data.
66
+
- Further examination can include a review of the `dns.question_type` network fieldset with a protocol analyzer, such as Zeek, Packetbeat, or Suricata, for `SIG` or `RRSIG` data.
67
67
- Validate the patch level and OS of the targeted DNS server to validate the observed activity was not large-scale Internet vulnerability scanning.
68
68
- Validate that the source of the network activity was not from an authorized vulnerability scan or compromise assessment.
69
69
70
70
#### False Positive Analysis
71
71
- Based on this rule which looks for a threshold of 60k bytes, it is possible for activity to be generated under 65k bytes
72
72
and related to legitimate behavior. In packet capture files received by the [SANS Internet Storm Center](https://isc.sans.edu/forums/diary/PATCH+NOW+SIGRed+CVE20201350+Microsoft+DNS+Server+Vulnerability/26356/), byte responses
73
73
were all observed as greater than 65k bytes.
74
-
- This activity has the ability to be triggered from compliance/vulnerability scanning or compromise assessment, it's
75
-
important to determine the source of the activity and potential whitelist the source host
74
+
- This activity can be triggered by compliance/vulnerability scanning or compromise assessment, it's
75
+
important to determine the source of the activity and potentially allowlist the source host.
76
76
77
77
78
78
### Related Rules
@@ -86,7 +86,7 @@ patched machines. If unable to patch immediately: Microsoft [released](https://s
86
86
restart. This can be used as a temporary solution before the patch is applied.
87
87
- Maintain backups of your critical systems to aid in quick recovery.
88
88
- Perform routine vulnerability scans of your systems, monitor [CISA advisories](https://us-cert.cisa.gov/ncas/current-activity) and patch identified vulnerabilities.
89
-
- If observed true positive activity, implement a remediation plan and monitor host-based artifacts for additional post-exploitation behavior.
89
+
- If you observe a true positive, implement a remediation plan and monitor host-based artifacts for additional post-exploitation behavior.
0 commit comments