Vulnerability Handling Guidelines
Recommendations and best practices for the handling of vulnerabilities detected in your applications.
As an automated security testing tool, Seeker detects and reports a variety of vulnerabilities from highly severe to just informational. The following sections focus on the recommended activities that should help you get the most out of Seeker detections with minimal time and effort.
Activity | Information |
---|---|
When implementing Seeker in an active SDLC, you need to distinguish between the new detections, which should be addressed quickly, and existing historical detections, which can be addressed over time. You can achieve this by baselining the initial set of results. | Baselining |
Seeker provides a variety of vulnerability checkers, however not every checker is relevant for your particular application. If you identify any checkers that generate too many detections, try to adjust these checkers' configuration. | Checker Configuration |
Since no development organization has a bandwidth to handle every detection right away, effectively managing your application risk requires prioritization. Setting up and applying phased remediation policies in Seeker can help you with that. | Remediation policies |
In Seeker, vulnerabilities have a lifecycle, in which they move between different stages from detection to close. Each stage is indicated by a status. In many cases, the vulnerability status changes are managed by Seeker automatically. In addition, users have an option to do that by triaging vulnerabilities manually or by using APIs. | Vulnerability Lifecycle Management |
Seeker Test Runs APIs enable you to facilitate your vulnerability handling by automatically triaging vulnerabilities in bulk during test runs. | Auto-Triage Vulnerabilities Using APIs |