Home
Best Practices Guide
Recommended best practices for implementing Seeker in your organization
Vulnerability Handling Guidelines
Recommendations and best practices for the handling of vulnerabilities detected in your applications.
Baselining
Some useful techniques to prioritize vulnerability handling by distinguishing between the new and historical detections in your application.

Best Practices Guide
Recommended best practices for implementing Seeker in your organization
- Best Practices
  Rolling out a new security testing tool in any organization requires quite a bit of planning and preparation.
- Planning and Preparations
  Things to plan and prepare before starting an actual Seeker implementation.
- Server Deployment and Initial Setup
  Things to consider when planning your Seeker server deployment.
- Configuration and Integration Checklist
  Make the most of Seeker by fine-tuning its settings and integrating the external tools that complement its functionality.
- Securing Seeker Deployment
  Recommended measures that can help you secure your Seeker deployment.
- Application Onboarding Checklist
  Tasks to perform to enable Seeker to test your application for security vulnerabilities.
- Application Testing Guidelines
  Once you have onboarded your application, you need to generate activity and traffic in the application for Seeker to monitor. In most cases, this happens during regular manual or automated QA testing.
- Reviewing Test Results
  Review the results of security testing of your application and included third-party and open-source components, and handle the detected vulnerabilities.
- Vulnerability Handling Guidelines
  Recommendations and best practices for the handling of vulnerabilities detected in your applications.
  - Baselining
    Some useful techniques to prioritize vulnerability handling by distinguishing between the new and historical detections in your application.
  - Checker Configuration
    You can substantially reduce the number of vulnerability detections without compromising on their significance just by fine-tuning the checker configuration.
  - Remediation policies
    To streamline the handling of security vulnerabilities detected by Seeker, consider establishing phased remediation policies.
  - Vulnerability Lifecycle Management
    How Seeker manages vulnerability lifecycle stages and transitions between them.
  - Auto-Triage Vulnerabilities Using APIs
    How to use Seeker APIs to auto-triage vulnerabilities to a selected status.
- Maintenance
  To ensure your Seeker system's health, perform periodic maintenance tasks.
- Performance Optimization
  How to minimize the potential impact of Seeker operation on application performance.

Baselining

Some useful techniques to prioritize vulnerability handling by distinguishing between the new and historical detections in your application.

At some point in your testing cycle, when you have collected enough detections, you might want to focus on the newly detected severe vulnerabilities, and put the previously collected historical and/or less important detections aside to address later. Baselining can help you with this.

To create a baseline, select the vulnerabilities that you want to put aside, or rather to hide from the default view. For example, set the filters in the Vulnerabilities view to medium and low severity and detected before a certain date, and do the following either in bulk or for individual vulnerabilities.

Triage these vulnerabilities to the Baseline status or a custom status that you want to use for this purpose. Consider documenting the details of current baselining in a comment.
Instead of or in addition to this, define a custom tag for the same purpose, and apply it to these vulnerabilities.

Then, toggle the status and/or tag filters to hide or show the baselined vulnerabilities according to your handling priorities.