SecObserve in a nutshell
SecObserve gathers results about potential security flaws from various vulnerability scanning tools and makes them available for assessment and reporting.
The aim of SecObserve is to make vulnerability scanning and vulnerability management as easy as possible for software development projects using open source tools. It consists of 2 major components:
Vulnerability management system SecObserve: SecObserve provides the development team with an overview of the results of all vulnerability scans for their project, which can be easily filtered and sorted. In the detailed view, the results are displayed uniformly with a wealth of information, regardless of which vulnerability scanner generated them.
With the help of automatically executed rules and manual assessments, the results can be efficiently evaluated to eliminate irrelevant results and accept risks. This allows the development team to concentrate on fixing the relevant vulnerabilities.
GitLab CI templates and GitHub actions: Integrating vulnerability scanners into a CI/CD pipeline can be tedious. Each tool has to be installed differently and is called with different parameters. To avoid having to solve this task all over again, there are repositories with GitLab CI Templates and GitHub Actions. These make the process of integrating vulnerability scanners very simple by providing uniform methods for launching the tools and uniform parameters. The tools are regularly updated in the repositories so that the latest features and bug fixes are always available.
All actions and templates run the scanner, upload the results into SecObserve and make the results of the scans available for download as artefacts in JSON format.
The sources of the GitHub actions and GitLab CI templates can be found in https://github.com/MaibornWolff/secobserve_actions_templates.
A sequence diagram explains the basic procedure how to work with SecObserve:
sequenceDiagram autonumber actor Developer Developer ->> Repository: Check in source activate Repository Repository ->> Pipeline: Start pipeline deactivate Repository activate Pipeline Pipeline ->> Pipeline: Run scanners Pipeline ->> SecObserve: Upload results deactivate Pipeline activate SecObserve SecObserve ->> SecObserve: Apply rules deactivate SecObserve Developer ->> SecObserve: View observations Developer ->> SecObserve: Assess observations Developer ->> Developer: Implement fixes Developer ->> Repository: Check in source ...
- A developer implements a feature and checks in his code to the repository
- The repository starts a pipeline for the change
- The pipeline runs several of the supported vulnerability scanners. To make integration easy, SecObserve provides predefined templates for the most relevant scanners, see GitHub actions and GitLab CI templates.
- The scanners store their results in files, which are uploaded into SecObserve.
- SecObserve applies rules to adjust severity and status of observations during the upload process.
- The developer can now look at the observations in SecObserve, to see what has changed ...
- ... and if necessary assess observations to change their status (eg. false positive or risk accepted) or severity.
- If fixes are needed to close vulnerabilities, the developer will implement the fixes ...
- ... and check them in to the repository. Now the cycle starts again.