Timeline for Frameworks for collecting all activities in a pentest?
Current License: CC BY-SA 3.0
11 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
May 25, 2016 at 20:35 | answer | added | Rory McCune | timeline score: 0 | |
May 25, 2016 at 19:55 | history | tweeted | twitter.com/StackSecurity/status/735559817419427846 | ||
May 9, 2016 at 7:21 | history | edited | Anders | CC BY-SA 3.0 |
edited tags; edited title
|
Apr 13, 2016 at 14:30 | review | Close votes | |||
Apr 13, 2016 at 20:49 | |||||
Apr 13, 2016 at 14:19 | answer | added | Abe Miessler | timeline score: 1 | |
Apr 13, 2016 at 14:09 | answer | added | RandomSecGuy | timeline score: 1 | |
Apr 13, 2016 at 13:44 | comment | added | coffeethulhu | could you do some sort of screen sharing or streaming program and simply record the output? | |
Apr 11, 2016 at 2:24 | comment | added | C.J. Steele | @Jeroen-ITNerdbox no, not sufficient. We need timestamps to correlate to activities. it'd be easy enough to wrap busybox with some sort of wrapper, or re-write a variety of applications, but who's got time for that? | |
Apr 11, 2016 at 1:55 | comment | added | h4ckNinja | Ahhh, a question that has been plaguing enterprise pentesters for years. I've been searching for such a tool as well. Faraday is one such tool, but it has cons, like relies on Qt3 and other outdated libraries, making installation and maintenance extremely difficult. I've been considering writing my own tools. You can log your bash/zsh history, which will capture your commands, but how to ship them off for centralized management? | |
Apr 11, 2016 at 1:51 | comment | added | Jeroen | Perhaps this is not enough, but what about the Linux command 'history'? | |
Apr 11, 2016 at 1:38 | history | asked | C.J. Steele | CC BY-SA 3.0 |