Added code for incremental scan issue

[satyamchaurasiapersistent]

Description

The customer is encountering abnormal behavior during concurrent scans in their Static Application Security Testing (SAST) process. This anomaly arises because the Cx-flow tool exclusively checks for successful scans, resulting in full scans for all concurrent requests. Consequently, the tool's inability to efficiently handle concurrent requests leads to redundant and resource-intensive scanning activities. This inefficiency not only prolongs scan times but also increases the likelihood of resource contention and inconsistencies in scan results. To address this issue, it's imperative to enhance the SAST tool's concurrency management capabilities.

Steps to Reproduce

set full scan after every 5 scan and then perform 5 scans one by one it will be incremental after that perform more than one scans parallelly for and then check in SAST all concurrent request will have full scan ideally only one should have full scan and other requests should be incremental Actual Result

set full scan after every 5 scan and then perform 5 scans one by one it will be incremental after that perform more than one scans parallelly for and then check in SAST all concurrent request will have full scan ideally only one should have full scan and other requests should be incremental Expected Result

set full scan after every 5 scan and then perform 5 scans one by one it will be incremental after that perform more than one scans parallelly for and then check in SAST all concurrent request will have full scan ideally only one should have full scan and other requests should be incremental Possible solution

https://sast94.cxquality.com/cxrestapi/sast/scans?projectId=885&scanStatus=7&last=5 instead of scan status 7 we should consider queued scans as well

[AvivCx]

Checkmarx One – Scan Summary & Details – 9a1cdfdf-b9d6-4e5f-b473-63ff9dc67db9

No New Or Fixed Issues Found