Fix 'Counters mismatch' error on dangling symlink #4093
Triggered via pull request
April 20, 2026 06:58
robertwoj-microsoft
Status
Failure
Total duration
1d 0h 15m 43s
Artifacts
74
universalnrp-test.yml
on: pull_request
Annotations
22 errors and 48 warnings
|
Module Test (debian, 12, amd64)
Process completed with exit code 143.
|
|
MC Test (ubuntu, 24.04, amd64, Remediate, LinuxSshServerSecurityBaseline, SSH, 20)
The operation was canceled.
|
|
Local Tests
The operation was canceled.
|
|
Module Test (oraclelinux, 8, amd64)
The operation was canceled.
|
|
MC Test (rhel, 9, amd64, Remediate, AzureLinuxBaseline, ASB, 169)
The operation was canceled.
|
|
MC Test (oraclelinux, 8, amd64, Remediate, AzureLinuxBaseline, ASB, 169)
The operation was canceled.
|
|
MC Test (rhel, 9, amd64, Remediate, LinuxSshServerSecurityBaseline, SSH, 20)
Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under '/mnt/vss/_work/_actions/actions/checkout/v4'. Did you forget to run actions/checkout before running your local action?
|
|
MC Test (rhel, 9, amd64, Remediate, LinuxSshServerSecurityBaseline, SSH, 20)
Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under '/mnt/vss/_work/_actions/actions/upload-artifact/v4'. Did you forget to run actions/checkout before running your local action?
|
|
MC Test (rhel, 9, amd64, Remediate, LinuxSshServerSecurityBaseline, SSH, 20)
Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under '/mnt/vss/_work/_actions/actions/upload-artifact/v4'. Did you forget to run actions/checkout before running your local action?
|
|
MC Test (rhel, 9, amd64, Remediate, LinuxSshServerSecurityBaseline, SSH, 20)
Access to the path '/mnt/vss' is denied.
|
|
MC Test (rhel, 9, amd64, Remediate, LinuxSshServerSecurityBaseline, SSH, 20)
Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under '/mnt/vss/_work/azure-osconfig/azure-osconfig/.github/actions/check-perf'. Did you forget to run actions/checkout before running your local action?
|
|
MC Test (rhel, 9, amd64, Remediate, LinuxSshServerSecurityBaseline, SSH, 20)
Process completed with exit code 143.
|
|
MC Test (rhel, 8, amd64, Remediate, AzureLinuxBaseline, ASB, 169)
The self-hosted runner lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
MC Test (ubuntu, 22.04, amd64, Remediate, LinuxSshServerSecurityBaseline, SSH, 20)
The self-hosted runner lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
MC Test (ubuntu, 20.04, amd64, Remediate, AzureLinuxBaseline, ASB, 169)
The self-hosted runner lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
MC Test (debian, 11, amd64, Remediate, AzureLinuxBaseline, ASB, 169)
The self-hosted runner lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
MC Test (almalinux, 9, amd64, Remediate, AzureLinuxBaseline, ASB, 169)
The self-hosted runner lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
Module Test (debian, 11, amd64)
The self-hosted runner lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
Module Test (ubuntu, 22.04, amd64)
The self-hosted runner lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
MC Test (sles, 15, amd64, Remediate, AzureLinuxBaseline, ASB, 169)
The self-hosted runner lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
MC Test (azurelinux, 3, amd64, Remediate, LinuxSshServerSecurityBaseline, SSH, 20)
The self-hosted runner lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
MC Test (azurelinux, 3, amd64, Remediate, AzureLinuxBaseline, ASB, 169)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
Package / package
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
MC Test (ubuntu, 20.04, amd64, Audit, AzureLinuxBaseline, ASB, 169)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
MC Test (ubuntu, 24.04, amd64, Audit, LinuxSshServerSecurityBaseline, SSH, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
MC Test (ubuntu, 22.04, amd64, Audit, LinuxSshServerSecurityBaseline, SSH, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
MC Test (ubuntu, 24.04, amd64, Audit, AzureLinuxBaseline, ASB, 169)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
MC Test (debian, 12, amd64, Audit, LinuxSshServerSecurityBaseline, SSH, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
MC Test (debian, 11, amd64, Audit, AzureLinuxBaseline, ASB, 169)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
MC Test (ubuntu, 20.04, amd64, Audit, LinuxSshServerSecurityBaseline, SSH, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
MC Test (rhel, 8, amd64, Audit, LinuxSshServerSecurityBaseline, SSH, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
MC Test (ubuntu, 22.04, amd64, Audit, AzureLinuxBaseline, ASB, 169)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Module Test (debian, 12, amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
MC Test (ubuntu, 24.04, amd64, Remediate, LinuxSshServerSecurityBaseline, SSH, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Local Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, azure/login@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Module Test (almalinux, 9, amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
MC Test (debian, 12, amd64, Audit, AzureLinuxBaseline, ASB, 169)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Module Test (rhel, 8, amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
MC Test (rhel, 8, amd64, Remediate, LinuxSshServerSecurityBaseline, SSH, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
MC Test (debian, 12, amd64, Remediate, LinuxSshServerSecurityBaseline, SSH, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
MC Test (almalinux, 9, amd64, Audit, LinuxSshServerSecurityBaseline, SSH, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
MC Test (ubuntu, 20.04, amd64, Remediate, LinuxSshServerSecurityBaseline, SSH, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
MC Test (debian, 11, amd64, Remediate, LinuxSshServerSecurityBaseline, SSH, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
MC Test (almalinux, 9, amd64, Audit, AzureLinuxBaseline, ASB, 169)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
MC Test (rhel, 8, amd64, Audit, AzureLinuxBaseline, ASB, 169)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
MC Test (ubuntu, 24.04, amd64, Remediate, AzureLinuxBaseline, ASB, 169)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
MC Test (debian, 11, amd64, Audit, LinuxSshServerSecurityBaseline, SSH, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
MC Test (debian, 12, amd64, Remediate, AzureLinuxBaseline, ASB, 169)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
MC Test (ubuntu, 22.04, amd64, Remediate, AzureLinuxBaseline, ASB, 169)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
MC Test (oraclelinux, 8, amd64, Audit, LinuxSshServerSecurityBaseline, SSH, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
MC Test (oraclelinux, 8, amd64, Audit, AzureLinuxBaseline, ASB, 169)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Module Test (rhel, 9, amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
MC Test (almalinux, 9, amd64, Remediate, LinuxSshServerSecurityBaseline, SSH, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
MC Test (rhel, 9, amd64, Audit, LinuxSshServerSecurityBaseline, SSH, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
MC Test (rhel, 9, amd64, Audit, AzureLinuxBaseline, ASB, 169)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
MC Test (oraclelinux, 8, amd64, Remediate, LinuxSshServerSecurityBaseline, SSH, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Module Test (oraclelinux, 8, amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
MC Test (rhel, 9, amd64, Remediate, AzureLinuxBaseline, ASB, 169)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
MC Test (oraclelinux, 8, amd64, Remediate, AzureLinuxBaseline, ASB, 169)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
MC Test (rhel, 9, amd64, Remediate, LinuxSshServerSecurityBaseline, SSH, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Module Test (sles, 15, amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Module Test (azurelinux, 3, amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
MC Test (sles, 15, amd64, Audit, LinuxSshServerSecurityBaseline, SSH, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
MC Test (sles, 15, amd64, Audit, AzureLinuxBaseline, ASB, 169)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
MC Test (sles, 15, amd64, Remediate, LinuxSshServerSecurityBaseline, SSH, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
MC Test (azurelinux, 3, amd64, Audit, AzureLinuxBaseline, ASB, 169)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Module Test (ubuntu, 24.04, amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Module Test (ubuntu, 20.04, amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
MC Test (azurelinux, 3, amd64, Audit, LinuxSshServerSecurityBaseline, SSH, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Report
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
almalinux-9_ASB-Audit_logs
|
46.2 KB |
sha256:319fcd1ff4b71b53c77260892e21d04a70420b4814342a4150dc4b4bb9fe73eb
|
|
|
almalinux-9_ASB-Audit_report
|
813 Bytes |
sha256:c646e0656c5b3c03bc3f6981dce6a820ea91b90e8fdc67cc6cf1ee033f29359d
|
|
|
almalinux-9_SSH-Audit_logs
|
8.96 KB |
sha256:7025b2770236a45b50ffd068735a4c349c1459723be7a29e77f84394a6ce5a16
|
|
|
almalinux-9_SSH-Audit_report
|
815 Bytes |
sha256:8de411d018193a396b1712ab5c870d784ca67a329f522638063b2c16328adbaa
|
|
|
almalinux-9_SSH-Remediate_logs
|
20.1 KB |
sha256:be686ba7d05eedaefae3a9336020cce40105ea43272eb3714904c810ab2fb250
|
|
|
almalinux-9_SSH-Remediate_report
|
796 Bytes |
sha256:ace8f279dcf14e270ff3674fcb665a6f1c5c0457fec6204b0fdca232bee7b30d
|
|
|
almalinux-9_logs
|
46.6 KB |
sha256:1572e474c26d6d83e3f998566f74c10a1c7a6ccd7f9bd478e5be71a80b6228dc
|
|
|
azurelinux-3_ASB-Audit_logs
|
45.3 KB |
sha256:cdc0f55b32174dac38b8390cda73fcd20a1d67cd52f8279b3dbc36ec78f944af
|
|
|
azurelinux-3_ASB-Audit_report
|
806 Bytes |
sha256:4fcdfc6dcaada3c0d21178b221d00c8d8eed848238c6758ec1f49bdea6440aff
|
|
|
azurelinux-3_SSH-Audit_logs
|
8.48 KB |
sha256:fdf2fc21e0aa671a212df6f9e1fe05c0fa935e30946c5737889d8b4d5405f2b3
|
|
|
azurelinux-3_SSH-Audit_report
|
808 Bytes |
sha256:161e8308ac3f2733e649f442f55122e850f8437950ae48119d88a4522584ee90
|
|
|
azurelinux-3_logs
|
45.2 KB |
sha256:0c7eb6543b9d8eb6642ecec02d0e9b94747c7c61a630fe2ed0a797cb089816b0
|
|
|
debian-11_ASB-Audit_logs
|
46.2 KB |
sha256:a758d11adcee05ffd5c2d9b7ad7db8c5cb1348391c422de03c4d5e9ecf2efd4d
|
|
|
debian-11_ASB-Audit_report
|
803 Bytes |
sha256:5562465beaf6cc00194aafd1a1e1f9865fc294dfaa0dbd119a3b6fa3d69f2704
|
|
|
debian-11_SSH-Audit_logs
|
8.94 KB |
sha256:2f91aaba8a8ab83797e2a1cda9a0034f4f402b3f7743a068a9ca29ad08efc0f7
|
|
|
debian-11_SSH-Audit_report
|
803 Bytes |
sha256:ac986f7b764401ff11e26146eddd652b556047773320d105b2d8584d8c824ffb
|
|
|
debian-11_SSH-Remediate_logs
|
20.1 KB |
sha256:07e8ba155c5a0feb7b4dd000c950f999f0c93b649730f0f5505949b8ff928416
|
|
|
debian-11_SSH-Remediate_report
|
787 Bytes |
sha256:968fbe3bf570027334e8bf62543a6c528d657c12885cc4a0b88a45fb19951cef
|
|
|
debian-12_ASB-Audit_logs
|
45.4 KB |
sha256:e3d3b99782cc59b893361b6dec4d3a67d6874473659c530af8a1ed3ceee0e984
|
|
|
debian-12_ASB-Audit_report
|
804 Bytes |
sha256:7cb1453cde2969b3c15932eb40f600f959cb2316ff2494246b611f4d1584487c
|
|
|
debian-12_ASB-Remediate_logs
|
119 KB |
sha256:1a6c0f91ea36ceef7cb3b0174f561a500308530fdff8d7a2e13fd4395a1af1d3
|
|
|
debian-12_ASB-Remediate_report
|
783 Bytes |
sha256:719df2a0bddd651e5d66e2d8bc6e976ee6431a89d269458f2a9e51769565dc73
|
|
|
debian-12_SSH-Audit_logs
|
8.78 KB |
sha256:1b033f91670c11078d84b1631e1588da72aa058024fb925b95528d0a0107953d
|
|
|
debian-12_SSH-Audit_report
|
799 Bytes |
sha256:90b367aef7fce2c240e7768be7dbdd7fc1b182da8f74b3428a60ab006f21d2eb
|
|
|
debian-12_SSH-Remediate_logs
|
19.7 KB |
sha256:aa8539f31152fdd2a21275694a15b90160effcda66ee099e58ebd81d871353e0
|
|
|
debian-12_SSH-Remediate_report
|
783 Bytes |
sha256:e6877b1c1e6e80ac480e00412bf693adc25ff6c1e0006acc63ae957b62efd4f6
|
|
|
nrp-test
|
29.3 MB |
sha256:bd95188464ed95f27c1d33cf2fe4526cba246d6d893c757a243bd95209881235
|
|
|
oraclelinux-8_ASB-Audit_logs
|
47 KB |
sha256:136346395e31b81287703d9bae9386ca4835a3bca0cb65a7b4539ab770b9d0d1
|
|
|
oraclelinux-8_ASB-Audit_report
|
822 Bytes |
sha256:c4d33548e2655d49afa46e5d36ac867b09780d8c4cd8807ab79f5e294c75a936
|
|
|
oraclelinux-8_SSH-Audit_logs
|
8.66 KB |
sha256:ef250cbf8369bc0cc2e2d0f6c63d6de811fc55b43b26d756b12962dc8100128c
|
|
|
oraclelinux-8_SSH-Audit_report
|
819 Bytes |
sha256:0c518f2b23b49c8c70a9a6a2f8675288e1ca73e446c706810bdc0083a780b4e1
|
|
|
oraclelinux-8_SSH-Remediate_logs
|
19.4 KB |
sha256:61c98f6b5bde513ff2672a998a811be27363a0ca5b0c9451c5fd162b94c398b6
|
|
|
oraclelinux-8_SSH-Remediate_report
|
798 Bytes |
sha256:0cf7edfff3405ba540e6f22497c3d1b9ab784721395039f845c4e392a03873d3
|
|
|
rhel-8_ASB-Audit_logs
|
46.5 KB |
sha256:fdb33c93aef85c41ab744e7866222183b181f9d9c08b057eb6330e3ee06a58e7
|
|
|
rhel-8_ASB-Audit_report
|
804 Bytes |
sha256:22b6cc970659387513cdbcf3a79ae9185e6b39b86cad6514b343ca37e4048288
|
|
|
rhel-8_SSH-Audit_logs
|
8.78 KB |
sha256:060678a69f041abef3b0a09116a88628312c18ec79a130b44280f18c2d83ea1b
|
|
|
rhel-8_SSH-Audit_report
|
808 Bytes |
sha256:8c72818fa56042072476bace23c50d48be8971aae8bdd8f244b69b26877ca904
|
|
|
rhel-8_SSH-Remediate_logs
|
19.7 KB |
sha256:0ae5837344628677b6416dcab61d9e8209652c8c4b13abb20f8171563c78a410
|
|
|
rhel-8_SSH-Remediate_report
|
787 Bytes |
sha256:04afb0904cce18153785347a078ee792e995cdc939358062215357eb0e5f5cd1
|
|
|
rhel-8_logs
|
46.4 KB |
sha256:042d35a678715674c1cf91d5f81d17dafbe106a9a369a510665bd1558e2c10f7
|
|
|
rhel-9_ASB-Audit_logs
|
46.4 KB |
sha256:42a4fcc60e32fd20a130ebb55637dd1e577e6d2cdef0e397a661157689a59f3c
|
|
|
rhel-9_ASB-Audit_report
|
806 Bytes |
sha256:600bec79d1b4e957a1fb8733342e2966715b7d7bd38031ba7afcff024430f135
|
|
|
rhel-9_SSH-Audit_logs
|
9.03 KB |
sha256:8d55ece8bde5b9db045b197f7c198d84b7fc0529272947da68e811048444127e
|
|
|
rhel-9_SSH-Audit_report
|
805 Bytes |
sha256:bc0c2bc10ffd7213faec9492777fccb6a98dd1eb6dbb2354ee47510632968b64
|
|
|
rhel-9_logs
|
46.6 KB |
sha256:6af377ea59207282ff21f1cb1c590f19ac7d7ba2ba42ff75709f7df2c65abacc
|
|
|
sles-15_ASB-Audit_logs
|
46.4 KB |
sha256:064ca3fb4cafc753767f5ff3c8096dc573fdab284f70c08469c298f0cf4eeaa8
|
|
|
sles-15_ASB-Audit_report
|
807 Bytes |
sha256:88216af6d7c81953d8fce5c39ee5936307a032567eb085a8fa8dbf9dc1c569a0
|
|
|
sles-15_ASB-Remediate_logs
|
119 KB |
sha256:215eec1ccd0b59ee611c48dec38e94dd6d82e190f67c0cc07609759947c87eee
|
|
|
sles-15_ASB-Remediate_report
|
785 Bytes |
sha256:b3e257c64118671a077dc8dce8f377406b3b9777997a5710e9e4811c6e117238
|
|
|
sles-15_SSH-Audit_logs
|
8.96 KB |
sha256:1ccd42758d92d0d76bebd0aeb09fb6fe2f84af7b7b611e568dc56249781f5cb6
|
|
|
sles-15_SSH-Audit_report
|
804 Bytes |
sha256:b1efed6925f9c85472d2a595fba25db420f173eacd9c174dae9fa1b87e21bfa5
|
|
|
sles-15_SSH-Remediate_logs
|
20.1 KB |
sha256:8292d2cf082a93918a370810431bf357137d5195f39886d29ac7849504fdd3e3
|
|
|
sles-15_SSH-Remediate_report
|
785 Bytes |
sha256:ccaae9ec00c121f9013b947e08968750016796da68a165461ad70429caf0ecdf
|
|
|
sles-15_logs
|
45.8 KB |
sha256:f82fea0fb683d89a3010b5adba7e449de6baaba3e5cbc5af3e283fc2db63c060
|
|
|
ubuntu-20.04_ASB-Audit_logs
|
47.4 KB |
sha256:c4e89e49a1fb04510ffe9738d5c1e89c632c6458c81505bfdd59311c9c3e7348
|
|
|
ubuntu-20.04_ASB-Audit_report
|
807 Bytes |
sha256:e90250f73e05cf9103a5a6095cf67bd26be5ec4abd2ec0176d0b5cf5891ccb09
|
|
|
ubuntu-20.04_SSH-Audit_logs
|
8.82 KB |
sha256:b396b83907a435454e266c9eee4d871364910f890793bc2bbc386ca3cbcdbd08
|
|
|
ubuntu-20.04_SSH-Audit_report
|
806 Bytes |
sha256:fb61b80febfe21c05a41e17e8b7eb4a9e399f0819a6d5944a6316dd5633b5e6b
|
|
|
ubuntu-20.04_SSH-Remediate_logs
|
20.1 KB |
sha256:213361505badf16a726957d31b1c047791d60c234205cc32d6c7d62d76abd20b
|
|
|
ubuntu-20.04_SSH-Remediate_report
|
787 Bytes |
sha256:4761e07534f6449ce3e90e2b867035b4ca7a754513367adce8f0073081a5f3f2
|
|
|
ubuntu-20.04_logs
|
45.9 KB |
sha256:df7683e0cb0db7555aae33dc08f9dfddbcf00cde5121c61b39e5eb343ca2e88c
|
|
|
ubuntu-22.04_ASB-Audit_logs
|
47.5 KB |
sha256:18a459802c9f4b6374e081f9114fd6bc9f2a6b96854ecf7d71e08e5c7a09725f
|
|
|
ubuntu-22.04_ASB-Audit_report
|
805 Bytes |
sha256:715cdaf979fd1ba848ea24bf82f33a9085b9a074d593427d6b346938a4cbfaec
|
|
|
ubuntu-22.04_ASB-Remediate_logs
|
119 KB |
sha256:fc19dcd8a8fefbe3db71ebe744cd709f4f7b98f787e4bc6bb78bcff4b444c6bf
|
|
|
ubuntu-22.04_ASB-Remediate_report
|
791 Bytes |
sha256:c686cc9c8203c749b8e6ada0f80e5a518a588d497d6dd46b887206f81a7aa5c5
|
|
|
ubuntu-22.04_SSH-Audit_logs
|
8.93 KB |
sha256:1144708d21fef0b140701554aae6eab4c240fb05b4c4a5be22b84dd09a8b484a
|
|
|
ubuntu-22.04_SSH-Audit_report
|
805 Bytes |
sha256:2f366b8f5d4ac335a7ea1fedd23860e351b1b5d20a7975318978979e1d66ff00
|
|
|
ubuntu-24.04_ASB-Audit_logs
|
44.4 KB |
sha256:e731250b61df07fe6666fcb9798784fc7549f8030146825b25354872157bddcb
|
|
|
ubuntu-24.04_ASB-Audit_report
|
804 Bytes |
sha256:824404d726d0c5d7f30e48a825005c7faa6656d5c8d4713ed6d1add18ff11898
|
|
|
ubuntu-24.04_ASB-Remediate_logs
|
114 KB |
sha256:a1e87743641741463edadf7277a1427917f202d0f587fb7f7ca0613ce5f4d583
|
|
|
ubuntu-24.04_ASB-Remediate_report
|
789 Bytes |
sha256:fde4bc4294e064a5c78a2be5024d3fb35d01dabdbbd384ae852824f139a424ab
|
|
|
ubuntu-24.04_SSH-Audit_logs
|
6.38 KB |
sha256:552dccda85b6eb5ebe86a1ec4984944c743711db01e4fb394feaef548d48eda3
|
|
|
ubuntu-24.04_SSH-Audit_report
|
806 Bytes |
sha256:7edf094d991e595d44e2adc5df300edfb969add6444ffb55204a6afd3b269f4f
|
|
|
ubuntu-24.04_logs
|
45.1 KB |
sha256:867ce48e415f8900fc1969c196de9b8cdf2423fcb26eea690b8153df08818a16
|
|