You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -20,9 +20,9 @@ Deepfence ThreatMapper hunts for threats in your production platforms, and ranks
20
20
21
21
With ThreatMapper's **ThreatGraph** visualization, you can then identify the issues that present the greatest risk to the security of your applications, and prioritize these for planned protection or remediation.
22
22
23
-
*[Learn more about ThreatMapper](https://community.deepfence.io/threatmapper/docs/v2.3/) in the product documentation.
23
+
*[Learn more about ThreatMapper](https://community.deepfence.io/threatmapper/docs/v2.4/) in the product documentation.
24
24
25
-
*[See ThreatMapper running](https://community.deepfence.io/threatmapper/docs/v2.3/demo) in the live demo sandbox.
25
+
*[See ThreatMapper running](https://community.deepfence.io/threatmapper/docs/v2.4/demo) in the live demo sandbox.
26
26
27
27
## When to use ThreatMapper
28
28
@@ -45,7 +45,7 @@ ThreatMapper consists of two components:
45
45
46
46
### The Management Console
47
47
48
-
You [deploy the Management Console first](https://community.deepfence.io/threatmapper/docs/v2.3/console/), on a suitable docker host or Kubernetes cluster. For example, on Docker:
48
+
You [deploy the Management Console first](https://community.deepfence.io/threatmapper/docs/v2.4/console/), on a suitable docker host or Kubernetes cluster. For example, on Docker:
49
49
50
50
```shell script
51
51
# Docker installation process for ThreatMapper Management Console
Once the Management Console is up and running, you can [register an admin account and obtain an API key](https://community.deepfence.io/threatmapper/docs/v2.3/console/initial-configuration).
57
+
Once the Management Console is up and running, you can [register an admin account and obtain an API key](https://community.deepfence.io/threatmapper/docs/v2.4/console/initial-configuration).
58
58
59
59
### Cloud Scanner tasks
60
60
61
-
ThreatMapper [Cloud Scanner tasks](https://community.deepfence.io/threatmapper/docs/v2.3/cloudscanner/) are responsible for querying the cloud provider APIs to gather configuration and identify deviations from compliance benchmarks.
61
+
ThreatMapper [Cloud Scanner tasks](https://community.deepfence.io/threatmapper/docs/v2.4/cloudscanner/) are responsible for querying the cloud provider APIs to gather configuration and identify deviations from compliance benchmarks.
62
62
63
63
The task is deployed using a Terraform module. The ThreatMapper Management Console will present a basic configuration that may be deployed with Terraform, or you can refer to the expert configurations to fine-tune the deployment ([AWS](https://community.deepfence.io/threatmapper/docs/cloudscanner/aws), [Azure](https://community.deepfence.io/threatmapper/docs/cloudscanner/azure), [GCP](https://community.deepfence.io/threatmapper/docs/cloudscanner/gcp)).
64
64
65
65
### Sensor Agents
66
66
67
-
Install the [sensor agents](https://community.deepfence.io/threatmapper/docs/v2.3/sensors/) on your production or development platforms. The sensors report to the Management Console; they tell it what services they discover, provide telemetry and generate manifests of software dependencies.
67
+
Install the [sensor agents](https://community.deepfence.io/threatmapper/docs/v2.4/sensors/) on your production or development platforms. The sensors report to the Management Console; they tell it what services they discover, provide telemetry and generate manifests of software dependencies.
68
68
69
69
The following production platforms are supported by ThreatMapper sensor agents:
70
70
71
-
*[Kubernetes](https://community.deepfence.io/threatmapper/docs/v2.3/sensors/kubernetes/): ThreatMapper sensors are deployed as a daemonset in the Kubernetes cluster, using a helm chart.
72
-
*[Docker](https://community.deepfence.io/threatmapper/docs/v2.3/sensors/docker/): ThreatMapper sensors are deployed as a lightweight container.
73
-
*[Amazon ECS](https://community.deepfence.io/threatmapper/docs/v2.3/sensors/aws-ecs): ThreatMapper sensors are deployed as a daemon service using a task definition.
74
-
*[AWS Fargate](https://community.deepfence.io/threatmapper/docs/v2.3/sensors/aws-fargate): ThreatMapper sensors are deployed as a sidecar container, using a task definition.
75
-
*[Bare-Metal or Virtual Machines](https://community.deepfence.io/threatmapper/docs/v2.3/sensors/linux-host/): ThreatMapper sensors are deployed within a lightweight Docker runtime.
71
+
*[Kubernetes](https://community.deepfence.io/threatmapper/docs/v2.4/sensors/kubernetes/): ThreatMapper sensors are deployed as a daemonset in the Kubernetes cluster, using a helm chart.
72
+
*[Docker](https://community.deepfence.io/threatmapper/docs/v2.4/sensors/docker/): ThreatMapper sensors are deployed as a lightweight container.
73
+
*[Amazon ECS](https://community.deepfence.io/threatmapper/docs/v2.4/sensors/aws-ecs): ThreatMapper sensors are deployed as a daemon service using a task definition.
74
+
*[AWS Fargate](https://community.deepfence.io/threatmapper/docs/v2.4/sensors/aws-fargate): ThreatMapper sensors are deployed as a sidecar container, using a task definition.
75
+
*[Bare-Metal or Virtual Machines](https://community.deepfence.io/threatmapper/docs/v2.4/sensors/linux-host/): ThreatMapper sensors are deployed within a lightweight Docker runtime.
76
76
77
77
For example, run the following command to start the ThreatMapper sensor on a Docker host:
78
78
@@ -99,11 +99,11 @@ docker run -dit \
99
99
100
100
Note: Image tag `quay.io/deepfenceio/deepfence_agent_ce:2.4.0-multiarch` is supported in amd64 and arm64/v8 architectures.
101
101
102
-
On a Kubernetes platform, the sensors are installed using [helm chart](https://community.deepfence.io/threatmapper/docs/v2.3/sensors/kubernetes/)
102
+
On a Kubernetes platform, the sensors are installed using [helm chart](https://community.deepfence.io/threatmapper/docs/v2.4/sensors/kubernetes/)
103
103
104
104
### Next Steps
105
105
106
-
Visit the [Deepfence ThreatMapper Documentation](https://community.deepfence.io/threatmapper/docs/v2.3/), to learn how to get started and how to use ThreatMapper.
106
+
Visit the [Deepfence ThreatMapper Documentation](https://community.deepfence.io/threatmapper/docs/v2.4/), to learn how to get started and how to use ThreatMapper.
107
107
108
108
109
109
# Get in touch
@@ -113,7 +113,7 @@ Thank you for using ThreatMapper. Please feel welcome to participate in the [Th
113
113
*[Deepfence Community Website](https://community.deepfence.io)
114
114
*[<imgsrc="https://img.shields.io/badge/slack-@deepfence-brightgreen.svg?logo=slack">](https://join.slack.com/t/deepfence-community/shared_invite/zt-podmzle9-5X~qYx8wMaLt9bGWwkSdgQ) Got a question, need some help? Find the Deepfence team on Slack
115
115
*[](https://github.com/deepfence/ThreatMapper/issues) Got a feature request or found a bug? Raise an issue
116
-
*[](https://community.deepfence.io/threatmapper/docs/v2.3/) Read the documentation in the [Deepfence ThreatMapper Documentation](https://community.deepfence.io/threatmapper/docs/v2.3/)
116
+
*[](https://community.deepfence.io/threatmapper/docs/v2.4/) Read the documentation in the [Deepfence ThreatMapper Documentation](https://community.deepfence.io/threatmapper/docs/v2.4/)
117
117
*[productsecurity at deepfence dot io](SECURITY.md): Found a security issue? Share it in confidence
118
118
* Find out more at [deepfence.io](https://deepfence.io/)
0 commit comments