Skip to main content

Security

Vulnerability Operator holds a complete list of the software on your systems, which is useful to an attacker too. Protect the server like any other system that has credentials for your infrastructure.

Transport​

  • Serve HTTPS. Set TLS_CERT_FILE and TLS_KEY_FILE for the server, or terminate TLS at an ingress or reverse proxy in front of it. Agents and browsers should only ever talk HTTPS.
  • Set PUBLIC_URL to the https:// address people use. Single sign-on needs it, and the links in the install commands are built from it.
  • Keep insecureSkipVerify off in the agent configuration and in the Kubernetes chart. Turning it on lets anyone on the path impersonate the server.

Browser headers​

Every response from the server carries these headers, so a browser runs the web UI under a strict policy:

HeaderValue
Content-Security-PolicyOnly the app's own scripts, styles, images and fonts. No inline scripts, no frames. The Swagger UI page gets a looser policy, because it needs inline script.
X-Frame-OptionsDENY. The app cannot be embedded in another site.
X-Content-Type-Optionsnosniff
Referrer-Policystrict-origin-when-cross-origin
Permissions-PolicyCamera, microphone, geolocation, payment and USB are off.
Cross-Origin-Opener-Policysame-origin
Strict-Transport-SecurityOnly on HTTPS requests. max-age is one year.

The frontend nginx image sets the same headers on the pages it serves itself. If a reverse proxy in front also adds them, remove the duplicates there.

Credentials​

There are four kinds of credential. Each can be revoked on its own.

CredentialWho holds itWhere it is managedNotes
Password or single sign-onPeopleUsers page, or the identity providerSet AUTH_PASSWORD_LOGIN=false to use only the provider.
Personal API token (vopt_)Scripts and AI assistantsEach user, on the Account pageActs with the roles and scope of its user.
Agent key (vopa_)One agentAgents page: rotate or disableStored only as a hash on the server. Shown once.
Cluster registration token (vopk_)The installer of a clusterAgents page: Cluster tokensRegisters agents of one cluster. Revoke it after installation if you do not need to add nodes.

Sign-in is throttled on the server: repeated failed attempts for one account are slowed down, and the throttle is kept in Redis, so every replica sees it.

Sessions last SESSION_TTL, twelve hours by default. Lower it for shared workstations.

Secrets​

  • Keep INITIAL_ADMIN_PASSWORD, the S3 keys, the database and Redis passwords and the OIDC or SAML client secrets out of images and version control. Use a Kubernetes secret (secrets.existingSecret) or your platform's secret store.
  • The JWT signing secret is created on the first start and kept in the database, so back up the database and keep the backups protected.
  • The alert channels and the AI backend keep their secrets in the database. The UI masks them after they are saved.

Least privilege​

  • Give people the smallest set of roles they need. The built-in viewer role reads everything in scope and changes nothing.
  • Use scopes for teams that should see only their clusters or nodes. A scoped user cannot register new hosts or clusters.
  • Create personal tokens for scripts instead of sharing a password.
  • Review the administrators once a quarter.

See Users, roles and scopes.

Network​

Allow these connections:

FromToPortPurpose
Browsers, MCP clientsServer or frontend443 (or 8080 without TLS)The UI, the API and /mcp.
Host and node agentsServer443Heartbeats and inventories.
Host agents on first installServer443Download of the installer and the agent release.
ServerRedis6379Locks, cache and job queue.
Server and workersS3 endpoint443 or 9000SBOMs, reports and agent releases.
Server and workersDatabaseper driverThe inventory.
Server and workersRelease bucket443Managed updates of the agents. Not needed when they are off.
Server and workersGrype database source443Vulnerability data. Not needed with GRYPE_DB_UPDATE=false.

Keep Redis, the database and the S3 store off the internet. Agents only need outbound HTTPS to the server.

Containers​

The server and frontend images run as a non-root user, the root file system is read-only, and privilege escalation is off, as set in the server chart. The Kubernetes node agent needs host paths and containerd access to read images. Grant it only on the nodes you want to scan, and review its RBAC rules before you install it.