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

Score balancing #241

Open
ruppde opened this issue Jul 19, 2024 · 0 comments
Open

Score balancing #241

ruppde opened this issue Jul 19, 2024 · 0 comments

Comments

@ruppde
Copy link
Contributor

ruppde commented Jul 19, 2024

hi Vincent,

thanks for using some of my proposed changes but I dare to disagree on the score balancing. (let me open this issue that it doesn't get overlooked in one of the closed PRs: #235, #239, #240)

how is it well balanced when a totally unhackable domain can have 200 points, compared to another domain, where any newbie ransomware gang can become domain admin in 3 different ways, has only 20 points?

easy hackable domain:

unhackable domain:

  • krbtgt 4+ years old: 50
  • 30+ inactive computer accounts: 30
  • 25+ inactive users: 10
  • some other hygiene rules, which don't make a domain automatically hackable

and admins using these scores to prioritize their clean up will do it in the wrong order or maybe not do it at all because the report is green enough. if purple knight wouldn't suck so much, I would check there, how it's scored for a comparison :)

best regards
arnim

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant