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

ATT&CK: create user #579

Closed
VakarisZ opened this issue Mar 19, 2020 · 1 comment · Fixed by #582
Closed

ATT&CK: create user #579

VakarisZ opened this issue Mar 19, 2020 · 1 comment · Fixed by #582
Labels
Beginner friendly New to the project? This issue is good for you! Enhancement Issue that describes an enhancement to a current feature.

Comments

@VakarisZ
Copy link
Contributor

We already have a "create user account" post breach action, but it's not mapped to the ATT&CK matrix.
image

Let's add this PBA to the matrix as Create Account attack technique.

  1. The "Create Account" technique should be present in attack matrix and user should be able to toggle it.
  2. On hover a brief with information about this particular attack technique should appear.
  3. This technique should be mapped with "Back door user" post breach action. This means that when "Create Account" is turned off, "Back door user" should turn off and vice versa.
  4. After exploitation, "Create Account" technique should be present on the ATT&CK report page.
@ShayNehmad ShayNehmad added Enhancement Issue that describes an enhancement to a current feature. Island Beginner friendly New to the project? This issue is good for you! labels Mar 26, 2020
@ShayNehmad
Copy link
Contributor

Important to note @VakarisZ @shreyamalviya - The other PBA also creates a new user and even impersonates as it to perform actions:
https://attack.mitre.org/techniques/T1204/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Beginner friendly New to the project? This issue is good for you! Enhancement Issue that describes an enhancement to a current feature.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants