[Skims] - Separate SCA checks from SAST
Problem to solve
Currently, when using the sast key in the config.yaml file, the SCA checks are run, which can be unintuitive for the user.
Intended users
External users.
Proposal
In favor of independent development of the 4 components of skims (SCA, CSPM, DAST, and SAST), it would be ideal if there was a key (sca) in the skims configuration file used to specify that this type of scan should be performed on the targets.
What does success look like, and how can we measure that?
Links / references
Edited by Julian Gomez