Skip to content
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

feat: collect ECA RoleSeparation #120

Merged
merged 3 commits into from
May 2, 2024
Merged

feat: collect ECA RoleSeparation #120

merged 3 commits into from
May 2, 2024

Conversation

JonasBK
Copy link
Contributor

@JonasBK JonasBK commented Apr 26, 2024

Description

Collection of enterpriseCA setting RoleSeparationEnabled

Ticket: BED-4351

Motivation and Context

If this setting is enabled, you cannot perform any CA actions if you have both ManageCA and ManageCertificates permissions. Only CA admins can modify the setting.

We need it for the ESC7 implementation, as some attack narratives require both ManageCA and ManageCertificates and could therefore be blocked by this setting.

More info on the setting: Q: How can I make sure that a given Windows account is assigned only

How Has This Been Tested?

Collection in my lab:
20240426013313_BloodHound.zip

Screenshots (if appropriate):

Types of changes

  • Chore (a change that does not modify the application functionality)
  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • Documentation updates are needed, and have been made accordingly.
  • I have added and/or updated tests to cover my changes.
  • All new and existing tests passed.
  • My changes include a database migration.

@JonasBK JonasBK enabled auto-merge (squash) April 26, 2024 09:09
@JonasBK JonasBK merged commit 6ea0272 into v3 May 2, 2024
3 checks passed
@JonasBK JonasBK deleted the collect-ca-roleseparation branch May 2, 2024 07:16
@github-actions github-actions bot locked and limited conversation to collaborators May 2, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants