ShellOpsLog is a versatile tool designed to capture and log all executed commands during various operations, such as red and purple team engagements.
It provides a lightweight solution for tracking command history without recording their output. The logged commands are saved in a CSV file, making it easy to analyze and include in client deliverables or internal reviews.
ShellOpsLog offers two primary implementations:
PROMPT_COMMAND
in Bash or preexec
in Zsh to log commands in Unix-based shells.source /path/to/ShellOpsLog.sh
to your shell startup file (e.g., ~/.bashrc
or ~/.zshrc
).start_operation_log ~/Projects/MyClient
.stop_operation_log
.New-Item -ItemType File -Path $PROFILE -Force
.Start-OperationLog "C:\Projects\MyClient"
.Stop-OperationLog
.While CMD support is available, it currently has limitations and is slated for updates in the future.
ShellOpsLog provides a simple yet effective way to track command history across different shell environments, making it a valuable tool for maintaining a clear record of activities during various operational engagements.
Nmap (Network Mapper) is a free tool that helps you find devices on a network,…
Introduction to the Model Context Protocol (MCP) The Model Context Protocol (MCP) is an open…
While file extensions in Linux are optional and often misleading, the file command helps decode what a…
The touch command is one of the quickest ways to create new empty files or update timestamps…
Handling large numbers of files is routine for Linux users, and that’s where the find command shines.…
Managing files and directories is foundational for Linux workflows, and the mv (“move”) command makes it easy…