-
Notifications
You must be signed in to change notification settings - Fork 177
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
Powershell console history #16
Comments
Also - yes, I double checked it’s not an added feature. Yes, This attack is more of a forensics related test, that checks what was commands were run in the past X amount of attempts. I know you dislike adding anything related to forensics; I think this is a really important test to look for what the attacker may have done to actually add the persistence. In other words helps reduce time to figure out the persistence needle in the haystack. |
It's not directly related to finding persistences but I may look into it. The thing is, it's not that I don't like forensics, it's that I think tools should do just one thing and do it in the best way possible. Extending PersistenceSniper in that way is going against this "rule", to me. Nonetheless, it may be useful, so I'll look into how to do it. |
Feature request to add a way to output the contents of powershell console history that can show the attackers commands.
https://0xdf.gitlab.io/2018/11/08/powershell-history-file.html
The text was updated successfully, but these errors were encountered: