On-premise Deployment
This section covers DerSecur Control Panel (DCP) 1.0.17: installing, expanding, updating and administering DerScanner on your own servers. Examples use DerScanner 13.2.11 and upgrades of existing installations. Panel and product versions are separate values: check both before starting.
Choose your path
A new installation
- Start with Prepare the server, access and installation files, then First panel launch, country selection and server checks and Install on the current server from the internet.
- For an offline environment: Installation without internet.
- For a complete installation on another server: Install a complete DerScanner deployment on a remote server.
- First sign-in and licensing: Licence and first product sign-in.
More servers and modules
- Component distribution, additional SAST agents, Builder, expansion and node replacement: start with Core, SAST, DAST and SCA on separate servers (video walkthrough).
- Existing installations and upgrades, including adding a module during an upgrade: start with Bring an existing installation under DCP.
Daily administration
- Panel updates: Update DCP itself.
- Backup and recovery: start with Create a backup and keep a copy off the server.
- Maintenance, access and troubleshooting: start with Inspect, stop and start a component.
Check the selected server at the start of every procedure.
Terms to distinguish
| Term | Meaning |
|---|---|
| DCP | The installation and administration panel running on a server. Your browser displays its interface. |
| Core | The main DerScanner services: web interface, API, data and task queue. |
| Node / agent | A separate scanner server connected to an existing Core. |
| Builder | A separate component for preparing and building projects before analysis. |
| SAST concurrency | Concurrent tasks on a worker within resource and licence limits; not a count of servers. |
| Delivery folder | Prepared files for the chosen release and modules, used for installation or update, including offline environments. |
Diagrams show component placement. Interface screenshots illustrate the corresponding actions; names and addresses in your deployment will differ.