Tool Tip: Kansa Stafford released, PowerShell for DFIR

Tool Tip: Kansa Stafford released, PowerShell for DFIR
In his most recent post, Guy asked "Are You a Hunter?". Here's one way to become one. Dave Hull has just published the Stafford release of his exemplary PowerShell DFIR tool, Kansa. For the uninitiated, Kansa is a modular incident response framework in Powershell.(PS v3 or higher preferred) that uses Powershell Remoting to run user contributed modules across hosts in an enterprise to collect data for use during incident response, breach hunts, or for building an environmental baseline. Per Dave's release notes for Stafford, Kansa.ps1 has several new command line parameters, including: -OutputFormat: an optional parameter that takes an argument that specifies the format of collected output. Valid values are CSV, JSON, TSV and XML (yuck). -UseSSL: if present, this will be passed to the New-PSSession call and remote sessions will use Secure Sockets Layer. Note this does require that you've installed appropriate certificates. -Port: an optional parameter that takes a port number. Use this when WinRM is configured to listen on a non-standard port. -Authentication: an optional parameter that takes an argument that specifies what authentication mechanism should be used. Kerberos is still the default, but all WinRM authentication mechanisms are now supported. You can even do risky things like Basic or CredSSP, but I wouldn't recommend it. -JSONDepth: an optional parameter that takes an integer argument specifying the level of depth for object serialization to JSON. For more details you can read why Kansa's Stafford release is more capable, more forensically sound, and more flexible via Dave's TrustedSignal blog. From personal experience, in both work-place and lab environments, Kansa is well worth your time to review and adopt. Additional reference material follows: http://trustedsignal.blogspot.com/search/label/Kansa http://www.powershellmagazine.com/2014/07/18/kansa-a-powershell-based-incident-response-framework/ http://holisticinfosec.blogspot.com/2015/01/toolsmith-kansa-vs-operation-cleaver.html Russ McRee \| @holisticinfosec	Russ McRee 184 Posts ISC Handler
Subscribe	Aug 17th 2015 4 years ago
Another tool which is very useful to collect evidences remotely: MIG ("Mozilla InvestiGator") (mig.mozilla.org/)	Xme 484 Posts ISC Handler
Quote	Aug 17th 2015 4 years ago
very cool, learning this just got entered in a fairly high spot on my todo list. thanks!	TuggDougins 37 Posts
Quote	Aug 18th 2015 4 years ago

In his most recent post, Guy asked "Are You a Hunter?". Here's one way to become one.

Dave Hull has just published the Stafford release of his exemplary PowerShell DFIR tool, Kansa. For the uninitiated, Kansa is a modular incident response framework in Powershell.(PS v3 or higher preferred) that uses Powershell Remoting to run user contributed modules across hosts in an enterprise to collect data for use during incident response, breach hunts, or for building an environmental
baseline.

Per Dave's release notes for Stafford, Kansa.ps1 has several new command line parameters, including:

-OutputFormat: an optional parameter that takes an argument that specifies the format of collected output. Valid values are CSV, JSON, TSV and XML (yuck).
-UseSSL: if present, this will be passed to the New-PSSession call and remote sessions will use Secure Sockets Layer. Note this does require that you've installed appropriate certificates.
-Port: an optional parameter that takes a port number. Use this when WinRM is configured to listen on a non-standard port.
-Authentication: an optional parameter that takes an argument that specifies what authentication mechanism should be used. Kerberos is still the default, but all WinRM authentication mechanisms are now supported. You can even do risky things like Basic or CredSSP, but I wouldn't recommend it.
-JSONDepth: an optional parameter that takes an integer argument specifying the level of depth for object serialization to JSON.

For more details you can read why Kansa's Stafford release is more capable, more forensically sound, and more flexible via Dave's TrustedSignal blog.

From personal experience, in both work-place and lab environments, Kansa is well worth your time to review and adopt. Additional reference material follows:

http://trustedsignal.blogspot.com/search/label/Kansa
http://www.powershellmagazine.com/2014/07/18/kansa-a-powershell-based-incident-response-framework/
http://holisticinfosec.blogspot.com/2015/01/toolsmith-kansa-vs-operation-cleaver.html

Russ McRee | @holisticinfosec

Russ McRee