-
Notifications
You must be signed in to change notification settings - Fork 41
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
8.C) Windows Admin Shares, Service Execution, Valid Accounts #20
Comments
This logic seems to catch or gives you visibility over services being created over the network:
Results
|
Working on a translation to OSQuery query based on Windows event logs like above. |
All of my analytics are using this tool set (https://github.com/idaholab/Malcolm) the first query I used was SMB.FN (SMB filename) == EXISTS!, This shows me all sessions that contain SMB files. ( with a small data set like this its quick way to ID things that stand out) We notice a few stand out items rather quickly, using the unique with counts we can see any we may have missed Opening up the /temp/python session we can see the share they are using (Newer moloch parses the share being used bettter) We can also see the same type of behavior with the PSEXE into admin$ |
I love that @DarthRaki ! I have never used that tool. looks great! Do you think that it would possible to translate that to a rule following some of the examples from @neu5ron and @patrickjohn ??
Thank you in advance!! |
8.C.1 Valid AccountsProcedure: Logged on to remote host Scranton (10.0.1.4) using valid credentials for user Pam Security Event Logs
Results
|
8.C.2 Windows Admin SharesProcedure: Established SMB session to remote host Scranton's (10.0.1.4) IPC$ share using PsExec |
Security Logs
Results
|
8.C.3 Service ExecutionProcedure: Executed python.exe using PSExec Security Logs
Results
|
Sysmon
Results
|
Description
This new payload is executed on the secondary victim via the PSExec utility (T1077, T1035) using the previously stolen credentials (T1078).
The text was updated successfully, but these errors were encountered: