-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[REQ]Is there a way to pull SAST results from CLI #581
Comments
Internal Jira issue: AST-29883 |
@MAP4H have you tried --report-format json |
My problem is not the format, by default i get .json format file, what i need is to get only the SAST result, but i don't see any filter to perform this action for a json format This is what says in the documentation: --report-pdf-options (Default: All Sections) This flag can only be used when --report-format is set as pdf. Available sections are: Sast, Sca, Iac-Security, Api-Security, ScanSummary, ExecutiveSummary, and ScanResults. ScanResults includes results for all scanners (IaC-Security, Sast and Sca). |
@MAP4H can you filter the json results to only look at SAST engine results? |
@MAP4H I am using as scripted pipeline approach to run scans. This may not pertain to your approach. However, I send my output to a temporary output file, and I can then parse it for key patterns with regex. sh(returnStatus: true, script: "CX1CMDSCRIPT > output.txt") |
Hi @logan5735 I understand that you run ast-cli in a pipeline and you want to update the just the sast results. I suggest you add these options to your scan create command: ./cx scan create --report-format json --output-name myreport.json Thanks. |
Currently i'm trying to export only SAST results from CLI into json format.
When i use ./cx results command i saw in the documentation that only when generating a PDF report i can specify SAST results, but not for .json formats.
Is there a way i can get only SAST results for .json format in CLI?
We have Checkmarx one.
Regards
The text was updated successfully, but these errors were encountered: