This repository contains multiple PowerShell scripts that can help you respond to cyber attacks on Windows Devices.
The following Incident Response scripts are included:
The DFIR script collects information from multiple sources and structures the output in the current directory in a folder named ‘DFIR-hostname-year-month-date’.
This folder is zipped at the end, so that folder can be remotely collected. This script can also be used within Defender For Endpoint in a Live Response session (see below).
The DFIR script collects the following information when running as normal user:
For the best experience run the script as admin, then the following items will also be collected:
The forensic artefacts are exported as CSV files, which allows responders to ingest them into their tooling. Some example tools in which you can ingest the data are Sentinel, Splunk, Elastic or Azure Data Explorer. This will allow you to perform filtering, aggregation and visualisation with your preferred query language.
The folder CSV Results (SIEM Import Data) includes all the CSV files containing the artefacts, the folder listing is shown below.
Name
----
ActiveUsers.csv
AutoRun.csv
ConnectedDevices.csv
DefenderExclusions.csv
DNSCache.csv
Drivers.csv
InstalledSoftware.csv
IPConfiguration.csv
LocalUsers.csv
NetworkShares.csv
OfficeConnections.csv
OpenTCPConnections.csv
PowerShellHistory.csv
Processes.csv
RDPSessions.csv
RemotelyOpenedFiles.csv
RunningServices.csv
ScheduledTasks.csv
ScheduledTasksRunInfo.csv
SecurityEvents.csv
ShadowCopy.csv
SMBShares.csv
The DFIR Commands page contains invidividual powershell commands that can be used during your incident response process. The follwing catagories are defined:
The script can be excuted by running the following command.
.\DFIR-Script.ps1
The script is unsigned, that could result in having to use the -ExecutionPolicy Bypass to run the script.
Powershell.exe -ExecutionPolicy Bypass .\DFIR-Script.ps1
It is possible to use the DFIR Script in combination with the Defender For Endpoint Live Repsonse. Make sure that Live Response is setup (See DOCS). Since my script is usigned a setting change must be made to able to run the script.
There is a blog article available that explains more about how to leverage Custom Script in Live Response: Incident Response Part 3: Leveraging Live Response
To run unsigned scripts live Response:
Execute script:
run DFIR-script.ps1
to start the script.getfile DFIR-DeviceName-yyyy-mm-dd
to download the retrieved artifacts to your local machine for analysis.Kali Linux 2024.4, the final release of 2024, brings a wide range of updates and…
This Go program applies a lifetime patch to PowerShell to disable ETW (Event Tracing for…
GPOHunter is a comprehensive tool designed to analyze and identify security misconfigurations in Active Directory…
Across small-to-medium enterprises (SMEs) and managed service providers (MSPs), the top priority for cybersecurity leaders…
The free and open-source security platform SecHub, provides a central API to test software with…
Don't worry if there are any bugs in the tool, we will try to fix…