Skip to content

feat: Add DAST scan support to SSC ci action - #1088

Merged
rsenden merged 6 commits into
fortify:dev/v3.xfrom
jmadhur87:mjain6/ssc-ci-dast-scan-support
Sep 18, 2026
Merged

rsenden merged 6 commits into
fortify:dev/v3.xfrom
jmadhur87:mjain6/ssc-ci-dast-scan-support

Conversation

@jmadhur87

Copy link
Copy Markdown
Contributor

Adds the ability to start ScanCentral DAST scan from the fcli SSC ci pipeline action, reusing scan settings that are already configured in SC-DAST

@jmadhur87
jmadhur87 marked this pull request as ready for review September 7, 2026 05:41
@jmadhur87
jmadhur87 requested a review from rsenden September 7, 2026 15:00

@rsenden rsenden left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Assuming this has been properly tested, I think this looks mostly fine. As a small improvement, I think it would be better to move the DAST_WAIT step down. For example, we can already download SAST logs if the DAST scan is still running.

I think even the Aviator-related calls are SAST-only for now, so we can already do SAST audit & remediations while DAST scan is still running, meaning that DAST_WAIT step should move after those Aviator-related steps.

Note that Aviator 26.4 will bring new DAST-related commands (and renames some SAST-related commands), so we'll likely need to make some changes once that gets released, to properly support Aviator DAST audits.

@jmadhur87
jmadhur87 requested a review from rsenden September 18, 2026 11:42
@rsenden
rsenden merged commit 3bc78d7 into fortify:dev/v3.x Sep 18, 2026
10 checks passed
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