Establish safety nets to guard against exceptional behavior in SAST and Secret Detection analyzers
There are paths through the analyzers which will cause them to behave in unexpected ways. The most common exceptions we have observed are the following:
1. Generate malformed JSON security reports.
1. Analyzers keep working in sidekiq after the CI job has expired.
1. Generated report sizes are huge.
Fortunately, these are truly exceptional events that occur a small fraction of the total number of executions. However, solving these scenarios in the analyzers will allow them to work more consistently within the expected parameters of the system.
epic