Skip to content

Conversation

@utkutombul
Copy link
Contributor

Windows.Audit.CISCat_Lite artifact has a problematic execve command which doesn't properly execute in cases where CISCatPath has spaces in file path. I solved the problem by executing via PowerShell artifact instead of execve, it properly executes now.

Windows.Audit.CISCat_Lite artifact has a problematic `execve` command which doesn't properly execute in cases where CISCatPath has spaces in file path. I solved the problem by executing via PowerShell artifact instead of `execve`, it properly executes now.
@scudette
Copy link
Collaborator

This is actually very interesting because execve is supposed to handle spaces in paths by itself.

We usually try to avoid running PowerShell unnecessarily because it pollutes the PowerShell artifacts.

@scudette
Copy link
Collaborator

Its definitely not an issue of the spaces in paths
image

Maybe there is something else about the powershell environment that makes it work over just running the tool?

Maybe it is a powershell script and needs to be launched with powershell?

@utkutombul
Copy link
Contributor Author

Sorry for the late answer. Yes, it specifically requires PowerShell. Perhaps it would be better if execve situtation is explained this way; since it requires PowerShell, my first -inexperienced- initiative was to call PowerShell from execve but somehow it failed because of spacing. Artifact definitely does not run properly with execve.

@scudette
Copy link
Collaborator

scudette commented Nov 3, 2025

This artifact was recently updated and fixed for the latest version of cis cat.

@scudette scudette closed this Nov 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants