Informational Rule for BadSuccessor AD Vulnerability

What is a one sentence summary of your feature request?

Informational Rule for BadSuccessor AD Vulnerability

Please describe your idea in detail. What is your problem, why do you feel this idea is the best solution, etc.

Implement checks as described here to check for accounts and OUs related to the new BadSuccessor AD Vulnerability.
https://www.akamai.com/blog/security-research/abusing-dmsa-for-privilege-escalation-in-active-directory#mitigation

How do you currently solve the challenges you have by not having this feature?

Manual check as described in the article

Added already into a GitHub beta build. See the announcement here.

3 Likes

Changing to in progress until it is in an official release rather than a beta :slight_smile:

Was this added to the 3.3.0.12 build? Judging by the tags on GitHub, 3.3.0.12 and 3.3.0.12_beta are identical (Commit 548de82eb0d9631e7a244deffaaf63cfcd4fb460), but both of these do not include the BadSuccessor commit in the branch BadSuccessor.

Hi there,
It’s in the beta only.

I probably should have called it 3.3.0.13_beta in retrospect.

This was our first beta so will document this internally for beta releases for next time to avoid confusion.