The ThreatStryker Management Console (Self-Managed)
The ThreatStryker Management Console ("Console") is a standalone application, implemented as a fleet of containers. It should be deployed on either a single docker host, or (for larger deployments) a dedicated Kubernetes cluster.
Before You Begin
Review the architecture for the Management Console, as described in Architecture: Management Console.
Review the requirements for the Management Console, as described in System Requirements.
Installing the Management Console
📄️ Docker Installation
Neo4j version was upgraded to v5.x (from v4.4).
📄️ Kubernetes Installation
Neo4j version was upgraded to v5.x (from v4.4).
Post-Installation Tasks
📄️ System Requirements
The Management Console may be installed on a single Docker host or in a dedicated Kubernetes cluster:
📄️ Upgrade from v2.1
Upgrade Neo4j from 4.4 to 5.x
📄️ Managed Database
For production deployment of Deepfence Management Console, we recommend using cloud/vendor managed PostgreSQL and Neo4j services.
📄️ Initial Configuration
Once you have installed the Management Console, you need to register an admin user and obtain the API key needed by the ThreatStryker sensors. You can also configure the URL for the Management Console, and provide your own TLS certificates.
📄️ Managing Users
The first Management Console user is created through the Initial Registration process. This is a one-time process; further users must be invited to the Console by an existing Admin user.
📄️ Database Export and Import
Postgres DB Export and Import
Troubleshooting
📄️ Troubleshooting
Docker configuration in Amazon Linux / RHEL