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
const prompt = `Analyze these software development commits and extract important decisions related to security, scalability, performance, compliance, architecture, and maintainability.
224
224
225
-
For each significant decision found, provide:
226
-
1. The decision made
227
-
2. The category (security/scalability/performance/compliance/architecture/maintainability)
# ThreatMapper - Runtime Threat Management and Attack Path Enumeration for Cloud Native
17
17
18
-
> [!IMPORTANT]
19
-
> [Upcoming Changes to ThreatMapper Threat Intel Feeds](https://www.deepfence.io/blog/upcoming-changes-to-threatmapper-threat-intel-feeds-what-you-need-to-know)
18
+
> [!NOTE]
19
+
> This project is maintained by https://threatmapper.org
20
20
21
21
Deepfence ThreatMapper hunts for threats in your production platforms, and ranks these threats based on their risk-of-exploit. It uncovers vulnerable software components, exposed secrets and deviations from good security practice. ThreatMapper uses a combination of agent-based inspection and agent-less monitoring to provide the widest possible coverage to detect threats.
22
22
23
23
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.
24
24
25
-
*[Learn more about ThreatMapper](https://community.deepfence.io/threatmapper/docs/v2.5/) in the product documentation.
25
+
*[Learn more about ThreatMapper](https://threatmapper.org/threatmapper/docs/v2.5/) in the product documentation.
26
26
27
-
*[See ThreatMapper running](https://community.deepfence.io/threatmapper/docs/v2.5/demo) in the live demo sandbox.
27
+
*[See ThreatMapper running](https://threatmapper.org/threatmapper/docs/v2.5/demo) in the live demo sandbox.
28
28
29
29
## When to use ThreatMapper
30
30
@@ -47,7 +47,7 @@ ThreatMapper consists of two components:
47
47
48
48
### The Management Console
49
49
50
-
You [deploy the Management Console first](https://community.deepfence.io/threatmapper/docs/v2.5/console/), on a suitable docker host or Kubernetes cluster. For example, on Docker:
50
+
You [deploy the Management Console first](https://threatmapper.org/threatmapper/docs/v2.5/console/), on a suitable docker host or Kubernetes cluster. For example, on Docker:
51
51
52
52
```shell script
53
53
# 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.5/console/initial-configuration).
59
+
Once the Management Console is up and running, you can [register an admin account and obtain an API key](https://threatmapper.org/threatmapper/docs/v2.5/console/initial-configuration).
60
60
61
61
### Cloud Scanner tasks
62
62
63
-
ThreatMapper [Cloud Scanner tasks](https://community.deepfence.io/threatmapper/docs/v2.5/cloudscanner/) are responsible for querying the cloud provider APIs to gather configuration and identify deviations from compliance benchmarks.
63
+
ThreatMapper [Cloud Scanner tasks](https://threatmapper.org/threatmapper/docs/v2.5/cloudscanner/) are responsible for querying the cloud provider APIs to gather configuration and identify deviations from compliance benchmarks.
64
64
65
-
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)).
65
+
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://threatmapper.org/threatmapper/docs/cloudscanner/aws), [Azure](https://threatmapper.org/threatmapper/docs/cloudscanner/azure), [GCP](https://threatmapper.org/threatmapper/docs/cloudscanner/gcp)).
66
66
67
67
### Sensor Agents
68
68
69
-
Install the [sensor agents](https://community.deepfence.io/threatmapper/docs/v2.5/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.
69
+
Install the [sensor agents](https://threatmapper.org/threatmapper/docs/v2.5/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.
70
70
71
71
The following production platforms are supported by ThreatMapper sensor agents:
72
72
73
-
*[Kubernetes](https://community.deepfence.io/threatmapper/docs/v2.5/sensors/kubernetes/): ThreatMapper sensors are deployed as a daemonset in the Kubernetes cluster, using a helm chart.
74
-
*[Docker](https://community.deepfence.io/threatmapper/docs/v2.5/sensors/docker/): ThreatMapper sensors are deployed as a lightweight container.
75
-
*[Amazon ECS](https://community.deepfence.io/threatmapper/docs/v2.5/sensors/aws-ecs): ThreatMapper sensors are deployed as a daemon service using a task definition.
76
-
*[AWS Fargate](https://community.deepfence.io/threatmapper/docs/v2.5/sensors/aws-fargate): ThreatMapper sensors are deployed as a sidecar container, using a task definition.
77
-
*[Bare-Metal or Virtual Machines](https://community.deepfence.io/threatmapper/docs/v2.5/sensors/linux-host/): ThreatMapper sensors are deployed within a lightweight Docker runtime.
73
+
*[Kubernetes](https://threatmapper.org/threatmapper/docs/v2.5/sensors/kubernetes/): ThreatMapper sensors are deployed as a daemonset in the Kubernetes cluster, using a helm chart.
74
+
*[Docker](https://threatmapper.org/threatmapper/docs/v2.5/sensors/docker/): ThreatMapper sensors are deployed as a lightweight container.
75
+
*[Amazon ECS](https://threatmapper.org/threatmapper/docs/v2.5/sensors/aws-ecs): ThreatMapper sensors are deployed as a daemon service using a task definition.
76
+
*[AWS Fargate](https://threatmapper.org/threatmapper/docs/v2.5/sensors/aws-fargate): ThreatMapper sensors are deployed as a sidecar container, using a task definition.
77
+
*[Bare-Metal or Virtual Machines](https://threatmapper.org/threatmapper/docs/v2.5/sensors/linux-host/): ThreatMapper sensors are deployed within a lightweight Docker runtime.
78
78
79
79
For example, run the following command to start the ThreatMapper sensor on a Docker host:
80
80
@@ -104,21 +104,21 @@ docker run -dit \
104
104
105
105
Note: Image tag `quay.io/deepfenceio/deepfence_agent_ce:2.5.7-multiarch` is supported in amd64 and arm64/v8 architectures.
106
106
107
-
On a Kubernetes platform, the sensors are installed using [helm chart](https://community.deepfence.io/threatmapper/docs/v2.5/sensors/kubernetes/)
107
+
On a Kubernetes platform, the sensors are installed using [helm chart](https://threatmapper.org/threatmapper/docs/v2.5/sensors/kubernetes/)
108
108
109
109
### Next Steps
110
110
111
-
Visit the [Deepfence ThreatMapper Documentation](https://community.deepfence.io/threatmapper/docs/v2.5/), to learn how to get started and how to use ThreatMapper.
111
+
Visit the [Deepfence ThreatMapper Documentation](https://threatmapper.org/threatmapper/docs/v2.5/), to learn how to get started and how to use ThreatMapper.
112
112
113
113
114
114
# Get in touch
115
115
116
116
Thank you for using ThreatMapper. Please feel welcome to participate in the [ThreatMapper Community](COMMUNITY.md).
117
117
118
-
*[Deepfence Community Website](https://community.deepfence.io)
118
+
*[ThreatMapper Community Website](https://threatmapper.org)
119
119
*[<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
120
120
*[](https://github.com/deepfence/ThreatMapper/issues) Got a feature request or found a bug? Raise an issue
121
-
*[](https://community.deepfence.io/threatmapper/docs/v2.5/) Read the documentation in the [Deepfence ThreatMapper Documentation](https://community.deepfence.io/threatmapper/docs/v2.5/)
121
+
*[](https://threatmapper.org/threatmapper/docs/v2.5/) Read the documentation in the [Deepfence ThreatMapper Documentation](https://threatmapper.org/threatmapper/docs/v2.5/)
122
122
*[productsecurity at deepfence dot io](SECURITY.md): Found a security issue? Share it in confidence
123
123
* Find out more at [deepfence.io](https://deepfence.io/)
0 commit comments