The ThreatMapper Management Console

The ThreatMapper 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

The quickest and easiest way to install the ThreatMapper Management Console is to use the pre-built images. These instructions use pre-built ThreatMapper containers from DockerHub.

📄️ Kubernetes Installation

You can install the Management Console on a single Docker host or in a dedicated Kubernetes cluster.

Post-Installation Tasks

📄️ System Requirements

The Management Console may be installed on a single Docker host or in a dedicated Kubernetes cluster:

📄️ 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 ThreatMapper 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