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

T1028 "Windows Remote Management": split in several techniques #1042

Closed
cnotin opened this issue Jun 15, 2020 · 5 comments · Fixed by #1225
Closed

T1028 "Windows Remote Management": split in several techniques #1042

cnotin opened this issue Jun 15, 2020 · 5 comments · Fixed by #1225

Comments

@cnotin
Copy link
Contributor

cnotin commented Jun 15, 2020

T1028 currently has 5 atomic tests implemented:

  1. Atomic Test Broken links #1 - Enable Windows Remote Management
  2. Atomic Test UAC Bypass #2 - PowerShell Lateral Movement
  3. Atomic Test small change #3 - WMIC Process Call Create
  4. Atomic Test Submitting two new Mac techniques #4 - Psexec
  5. Atomic Test Windows - Collection #5 - Invoke-Command

T1028 is very specific to "Windows Remote Management", also called WinRM which is used by PowerShell Remoting (and others) but not by psexec, mmc20 or remote WMI.

Therefore, I suggest keeping only those in T1028:

And here are my suggestions for the others:

  • Atomic Test UAC Bypass #2 - PowerShell Lateral Movement: it uses PowerShell but actually the technique is based on "mmc20" which has its own T1175 "Component Object Model and Distributed COM" currently non existent
  • Atomic Test small change #3 - WMIC Process Call Create: I'd move it to T1047 - Windows Management Instrumentation which already has a very similar test "Atomic Test Updated Windows Matrix #6 - WMI Execute Remote Process"
  • Atomic Test Submitting two new Mac techniques #4 - Psexec: it's actually T1035 - Service execution, which already has a relevant test "Atomic Test UAC Bypass #2 - Use PsExec to execute a command on a remote host"

What do you think? Would you like me to implement these suggestions?

@cnotin
Copy link
Contributor Author

cnotin commented Jun 26, 2020

Need to adapt this to new subtechniques. Ex. T1021.006

@mgraeber-rc
Copy link
Collaborator

@cnotin Apologies for the late reply on this. With the transition to sub-techniques, do you feel the tests align to their respective T1021 sub-techniques?

@cnotin
Copy link
Contributor Author

cnotin commented Sep 16, 2020

@mgraeber-rc no worries :)
Here's an update of my original message (I've copied and adapted some parts)

Those are now T1021.006 and I agree:

Those others still need change IMO:

  • Atomic Test UAC Bypass #2 - PowerShell Lateral Movement
    currently still in T1021.006
    it uses PowerShell but actually the technique is based on "mmc20" which has its own T1021.003 "Remote Services: Distributed Component Object Model"

  • Atomic Test small change #3 - WMIC Process Call Create
    currently still in T1021.006
    I'd move it to T1047 - Windows Management Instrumentation which already has a very similar test "Atomic Test Updated Windows Matrix #6 - WMI Execute Remote Process"

  • Atomic Test Submitting two new Mac techniques #4 - Psexec
    currently still in T1021.006
    it's actually T1569.002 - "System Services: Service Execution", which already has a relevant test "Atomic Test UAC Bypass #2 - Use PsExec to execute a command on a remote host"

@mgraeber-rc
Copy link
Collaborator

Thanks for the update, @cnotin! Completely agree with moving test 2 to T1021.003. I'd support removing test 3 and 4 as well if they are duplicates of existing tests. Thoughts? You wanna submit the PR? Thanks again!

@cnotin
Copy link
Contributor Author

cnotin commented Sep 17, 2020

I cannot suggest a PR immediately but maybe later. Except if you prefer it faster and in that case no worries I let you do it :)

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

Successfully merging a pull request may close this issue.

2 participants