A PowerShell-based live response and forensic collection tool for targeted incident response on Windows systems.
Invoke-LiveResponse is a PowerShell module for live response and forensic data collection on Windows systems during security incidents. It provides two main modes: ForensicCopy for targeted artifact collection and memory acquisition, and Live Response for executing custom PowerShell scripts to gather system data. The tool helps incident responders quickly collect evidence from remote or local machines with minimal footprint.
Security analysts, incident responders, and forensic investigators who need to perform live response on Windows environments, especially in enterprise or targeted investigation scenarios.
Developers choose Invoke-LiveResponse for its flexibility in supporting both predefined forensic collection and custom script execution, compatibility with PowerShell 2.0+, and ability to run over WinRM or locally without requiring heavy dependencies.
Invoke-LiveResponse
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
ForensicCopy mode reflectively loads Powerforensics for raw disk access, enabling collection of common artifacts and custom files without installing dependencies, as highlighted in the README.
Live Response mode executes any PowerShell scripts from a content folder, inspired by the Kansa Framework, allowing easy operationalization of new capabilities with standard output results.
Supports running over WinRM, locally via scriptblock generation, and on PowerShell 2.0+ targets, providing versatility for different deployment scenarios, including legacy systems.
Integrates WinPMem for memory dump collection during forensic operations, a critical feature for live response investigations, as mentioned in the key features.
Designed exclusively for Windows systems, making it ineffective for mixed or non-Windows environments, which limits its use in cross-platform incident response.
The one-liner install involves downloading and executing scripts from the internet with a trust note, posing risks in locked-down environments and potentially triggering security alerts.
Relies on an external wiki for documentation, which may not be as comprehensive or up-to-date as inline help, hindering quick adoption and troubleshooting.