Platform

Platform overview How it works Authorization testing Evidence & reports Private scanning Integrations

Solutions

Security agencies Product teams Regulated industries Partner programme

Learn

Blog Knowledge hub Compare

Resources

Pricing Documentation Help centre FAQ Security & data What we haven’t proved

Company

About Contact Careers Sign in to the platform Start a $199 pilot →

Home / Help centre / Workspace settings

Workspace settings

How do I add a self-hosted scan agent?

Quick answer

Open Settings, choose Scan Agents, type a name and click Add agent. Copy the one-time enrollment token and run command at once, because they show only once. Run the command inside your network. Then set the agent as the Scan location on a profile.

Steps

An agent is a lightweight runner on your own network. It lets Cyberlop scan internal apps that the cloud cannot reach.

STEPS

Good to know

The agent connects out to Cyberlop over HTTPS only. You open no inbound ports. Your code and your target stay on your network.

The token is shown once and cannot be fetched again. If you lose it, the safe route is to add a fresh agent and revoke the old one. Read what to do about a lost token for the details.

The machine that runs the command needs Docker and outbound HTTPS. Pick one inside the network of the target. Where to run the container covers it.

After the agent starts, its status changes from pending to online. You can watch it in the table, which also shows Last seen. An online agent raises your concurrent scan limit as well.

Agents are part of some plans. The Plan & usage tab shows Internal scan agents as a feature chip when yours includes it. Ask us on the contact page if you want it.

Name agents after where they live, such as the data centre or the network zone. When you have several, the table gets crowded and a clear name tells you at a glance which one to check. Short names work best. Add one agent per network that Cyberlop cannot reach from the cloud, and give each its own name.

Plan for upkeep too. An agent is a container, so someone on your side owns its host, its updates and its uptime, and that owner should know the machine must keep outbound access to Cyberlop for as long as scans depend on it.

Full tutorial

Cyberlop self-hosted scan agents: scan private apps from inside your network

Step-by-step, with annotated screenshots.

Updated · Back to the help centre

Still stuck?

Tell us what you see on screen and an engineer will help you sort it out.