Home
Best Practices Guide
Recommended best practices for implementing Seeker in your organization
Server Deployment and Initial Setup
Things to consider when planning your Seeker server deployment.

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.
- 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.

Server Deployment and Initial Setup

Things to consider when planning your Seeker server deployment.

Deployment considerations

The first decision to make before deployment is to determine whether the Seeker server will be installed in your data center or private cloud. In most cases, a simple all-in-one node solution that runs the Seeker server software and Postgres database will suffice.

For further information about the deployment options, system requirements, sizing guidelines, and installation steps, refer to Installation.

Server and database setup

If you require a fault-tolerant database, we recommend configuring an external Postgres cluster with 1 writer and at least 1 reader. If the writer fails, the reader will take over. If you are using cloud providers such as AWS, you can use Amazon RDS to configure your cluster.

A single Seeker server is capable of handling 10,000 concurrent agents and 2000 projects. Typically, we recommend just having a standby server to perform upgrade testing and to also serve as a backup should the primary server go down.