diff --git a/README.md b/README.md index ccbcd89..c61b1f7 100644 --- a/README.md +++ b/README.md @@ -161,6 +161,34 @@ Once allowed endpoints are set in the policy in the workflow file, or in the [Po Policy recommended by harden-runner

+### 📋 View the name and path of every file written during the build process + +> Applies to both GitHub-hosted and self-hosted runners + +View the name and path of every file that was written during the build process. This feature is supported with a commercial license. + +- Harden-Runner tracks every file written to the GitHub Actions working directory during the build process. +- In the insights page in the `File Write Events` tab you can see a file explorer view of each file that was written to. +- Clicking on any file reveals a list of processes that wrote to it, providing complete transparency. + +

+ View the name and path of every file written during the build process +

+ +### 🔄 View process names and arguments + +> Applies to both GitHub-hosted and self-hosted runners + +View process names, PIDs, and process arguments. This feature is supported with a commercial license. + +- Harden-Runner tracks every process that is run during the build process. +- Clicking on any file reveals a list of processes that wrote to it. +- You can walk up the process tree and view process arguments to understand the build process and detect suspicious activity. + +

+ View process names and arguments +

+ ### 📁 Detect tampering of source code during build > Applies to both GitHub-hosted and self-hosted runners diff --git a/images/file-write-events.png b/images/file-write-events.png new file mode 100644 index 0000000..aa60f46 Binary files /dev/null and b/images/file-write-events.png differ diff --git a/images/process-events-2.png b/images/process-events-2.png new file mode 100644 index 0000000..6670f36 Binary files /dev/null and b/images/process-events-2.png differ