Skip to content

Conversation

@thegreatmhn
Copy link

Details

What does this PR have in it? Screenshots are worth 1000 words 😄

This PR adds a new analytic titled "Active Directory AS-REP Roasting Detection" designed to identify potential credential access activity within Active Directory environments.
It detects Kerberos AS-REQ events (EventCode 4768) where PreAuthType=0, a condition indicative of AS-REP roasting attempts.
Adversaries can exploit accounts configured with "Do not require Kerberos pre-authentication" to retrieve encrypted ticket responses and perform offline password cracking.

This correlation analytic provides early behavioral detection of credential harvesting attempts against AD, mapping to MITRE ATT&CK T1558.004 – AS-REP Roasting under the Credential Access tactic.

Checklist

  • Validate name matches <platform>_<mitre att&ck technique>_<short description> nomenclature
  • CI/CD jobs passed ✔️
  • Validated SPL logic.
  • Validated tags, description, and how to implement.
  • Verified references match analytic.
  • Confirm updates to lookups are handled properly.

Notes For Submitters and Reviewers

  • If you're submitting a PR from a fork, ensuring the box to allow updates from maintainers is checked will help speed up the process of getting it merged.
  • Checking the output of the build CI job when it fails will likely show an error about what is failing. You may have a very descriptive error of the specific field(s) in the specific file(s) that is causing an issue.
  • In some cases, there may be YAML formatting issues; pre-commit hooks can catch many of these locally.
  • Updates to existing lookup files can be tricky due to how Splunk handles application updates. Be sure to bump the date and version fields in the YAML file when modifying existing content.

version: 1
date: '2025-10-23'
author: Mahdi Hamedani Nezhad
status: production
Copy link
Contributor

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.

Copy link
Author

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

@nasbench nasbench added the WIP DO NOT MERGE Work in Progress label Oct 23, 2025
@nasbench nasbench marked this pull request as draft October 23, 2025 18:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Detections WIP DO NOT MERGE Work in Progress

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants