Scanning Frequencies

soos uses different scanning frequencies based on the type of scan being run we'll outline those below and also explain how to configure these frequencies before diving into the frequencies, we should note that unlike other platforms, soos encourages the use of per commit scanning as well as daily rescans meaning, we suggest that you configure your build or deploy pipeline to run soos on every change and also support automatic daily rescans so that even less active projects are continually checked for new issues and vulnerabilities soos provides advanced configuration options to allow scan configurations per branch, as outlined below this approach is different than many other platforms which simply perform one daily scan sca, sbom, and container scan frequencies running a scan on every commit using a ci/cd or webhook integration with soos ensures that code changes, as well as new vulnerabilities detected during the day, will be identified immediately using soos' patented analysis engine at any point in time you can also force a scan by selecting "rescan" under your project/branch in the ui soos rescan button branch based scan configuration additionally, soos can be configured to rescan specific branches on a daily schedule if no scans previously ran that day you may also notice here that there are a few other settings that can be configured per branch, learn more about these under branch scan configurations docid\ qxkpnhncs83jdovwwxjrn configure daily rescans dast scan frequencies we recommend running more frequent baseline scans, such as with each deployment and running scheduled (usually daily) full scans visit dast scan modes docid\ in46me9k 6otbmok9hids to learn more about the differences between these types of scans sast and secret scan frequencies because soos provides a sast/secrets connector and not an implementation we recommend following the recommendations from the tool provider, but we are happy to ingest sast results as often as necessary