This guide is focused on getting Kansa up and running in an enterprise environment. PowerShell has a few safeguards you have to remove before it will let you run with the privileges you require.
What is Kansa?
Kansa is an Incident Response Framework that runs in PowerShell. Its primary purpose is to pull logs from multiple Windows machines that are running the same AD domain.
Resources:
Setup Process
Initial Setup
Run PowerShell as Administrator and navigate to your working directory. Download and extract the scripts:
|
|
Configure PowerShell Execution Policy
Navigate to the KansaScripts directory and set the execution policy:
|
|
Unblock PowerShell Files
If you encounter script blocking issues, unblock the PowerShell files:
|
|
Install Prerequisites
If you hit errors for missing prerequisites, run the setup script:
|
|
Download Kansa Framework
Download the main Kansa framework:
|
|
Running Kansa
Navigate to the master directory and execute Kansa with target parameters:
|
|
Note: The variable $env:COMPUTERNAME
returns the current host’s name. This can be replaced with hostnames of any machines you wish to target.
Output and Results
After a short time, you should have the logs stored in an output folder.
Tip: If Kansa gets stuck, Ctrl+C
will only cancel the current log type and move to the next one.
Additional Resources
For more detailed information, read the comprehensive documentation at: Kansa Documentation
Happy Hunting! 🔍
This framework is invaluable for incident response teams working in Windows environments. Kansa’s ability to quickly gather forensic data across multiple systems makes it an essential tool in any IR toolkit.
Last modified on 2025-06-25