Connecting and Upgrading Agents
To start monitoring your application, connect it to an Agent.
The Seeker Agents are installed on the application servers alongside the web applications that they monitor, and communicate with the central Seeker Enterprise Server. Each Agent must match the corresponding application's technology.
Connecting an Agent to your application means installing and activating it on the web server on which the application runs. The Agent should match the application’s platform and technology.
The following diagram illustrates possible Seeker installation models:
- Standard web application installation: An Agent is installed alongside an application on the same server.
- Docker-based installation: An application, its components or microservices along with their Agents are installed each in a separate Docker container on a host.
Prerequisites
To ensure network connectivity between the Agent and the Seeker server:
- Configure the firewall to allow incoming TCP/IP and WebSocket connections to the server (default ports HTTP 8080/HTTPS 8443).
- Configure the antivirus software on the server to trust Seeker.
Installation and Upgrade Options
| Options | Information |
|---|---|
| If you are an experienced user, you can connect Agents by directly downloading and installing the Agent binaries, and then configuring the Agents. | Connect Agents Directly |
| If you are new to Seeker, or prefer an assisted installation, or need to customize your installation scripts, use the Connect Agent wizard. | Connect Agents Using Wizard |
| If you want to enable the authentication of Agents to the Seeker server. | Configure Agent Authentication |
| If your application is running in a Docker environment. | Deploying Seeker Agents with Docker |
| If your application is running on Kubernetes. | Deploying Agents on Kubernetes |
| If your application is running in Microsoft Azure App Service. | Deploying .NET Agent in Azure App Service |
| Automate your Agent installation and administration. | Agent Administration APIs |
| Make sure your Agents are upgraded to the server version. | Upgrade Agents |
To help identify the testing environments in which vulnerabilities are detected
by Agents, you can define custom tags for the Agents running in these
environments using the variable SEEKER_AGENT_CUSTOM_TAGS or JVM
property seeker.agent.custom.tags. For example:
env_qa or env_dev.
Then these custom tags will be automatically assigned to the vulnerabilities detected by these Agents, which comes in handy for their subsequent filtering and triaging.