-
Notifications
You must be signed in to change notification settings - Fork 430
windows_T1558.004_active_directory_asrep_roasting_detection #3741
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Draft
thegreatmhn
wants to merge
1
commit into
splunk:develop
Choose a base branch
from
thegreatmhn:asreproasting
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
61 changes: 61 additions & 0 deletions
61
detections/endpoint/active_directory_as_rep_roasting_detection.yml
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,61 @@ | ||
| name: Active Directory AS-REP Roasting Detection | ||
| id: ab5e7322-fa7c-4752-b174-121db4ea54db | ||
| version: 1 | ||
| date: '2025-10-23' | ||
| author: Mahdi Hamedani Nezhad | ||
| status: production | ||
| type: Correlation | ||
| data_source: [] | ||
| description: The following analytic identifies potential credential access activity | ||
| targeting Active Directory (AD) user accounts through AS-REP roasting techniques. | ||
| It detects this behavior by monitoring Kerberos AS-REQ events (EventCode 4768) that | ||
| request Ticket-Granting Tickets (TGTs) without pre-authentication (PreAuthType=0). | ||
| This condition typically occurs when an account has the "Do not require Kerberos | ||
| pre-authentication" flag enabled, which adversaries can exploit to obtain encrypted | ||
| credentials for offline password cracking. This is significant for a SOC as it highlights | ||
| attempts to enumerate or harvest weakly protected user accounts, potentially exposing | ||
| valid credentials. If confirmed malicious, this activity could enable attackers | ||
| to gain unauthorized access to AD services and escalate privileges within the domain. | ||
| search: '`wineventlog_security` EventCode=4768 ServiceName=krbtgt PreAuthType=0 | ||
| | search NOT TargetUserName="*$" | ||
| | stats count min(_time) as firstTime max(_time) as lastTime by TargetUserName ServiceName src_ip dest | ||
| | `security_content_ctime(firstTime)` | ||
| | `security_content_ctime(lastTime)` | ||
| | `active_directory_as_rep_roasting_detection`' | ||
| how_to_implement: Splunk Enterprise Security is required to utilize this correlation. | ||
| Ensure that Windows Security Event Logs (EventCode 4768) are being ingested from | ||
| all domain controllers. Modify the count threshold as appropriate for your environment. | ||
| In testing, three or more events in a short period may indicate enumeration or roasting | ||
| behavior. Tune filters and thresholds to reduce false positives. | ||
| known_false_positives: False positives may occur in environments with legacy or service | ||
| accounts that legitimately have pre-authentication disabled. These accounts should | ||
| be reviewed and filtered as appropriate. | ||
| references: | ||
| - https://attack.mitre.org/techniques/T1558/004/ | ||
| - https://adsecurity.org/?p=2293 | ||
| - https://research.splunk.com/stories/active_directory_privilege_escalation/ | ||
| drilldown_searches: | ||
| - name: View the detection results for - "$TargetUserName$" | ||
| search: '%original_detection_search% | search TargetUserName = "$TargetUserName$"' | ||
| earliest_offset: $info_min_time$ | ||
| latest_offset: $info_max_time$ | ||
| - name: View related Kerberos activity for - "$src_ip$" | ||
| search: 'index=windows (EventCode=4768 OR EventCode=4769 OR EventCode=4771) src_ip="$src_ip$" | ||
| | stats count min(_time) as firstTime max(_time) as lastTime values(TargetUserName) | ||
| as "Target Users" values(EventCode) as "Event Codes" by src_ip dest | ||
| | `security_content_ctime(firstTime)` | `security_content_ctime(lastTime)`' | ||
| earliest_offset: $info_min_time$ | ||
| latest_offset: $info_max_time$ | ||
| tags: | ||
| analytic_story: | ||
| - Active Directory Privilege Escalation | ||
| - Credential Access via Kerberos | ||
| asset_type: Endpoint | ||
| atomic_guid: [] | ||
| mitre_attack_id: | ||
| - T1558.004 | ||
| product: | ||
| - Splunk Enterprise | ||
| - Splunk Enterprise Security | ||
| - Splunk Cloud | ||
| security_domain: endpoint | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In order for this to be a production level rule we would need some logs.
Can you please provide logs for this and open a PR on https://github.com/splunk/attack_data/
Once that is done I will take care of the rest of the updates.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the review!
I’ve added the sample logs and opened the PR here: splunk/attack_data#1052