Hacking Articles Tips Tricks Videos Tutorials

KitPloit - PenTest Tools!
ThreatMapper - Identify Vulnerabilities In Running Containers, Images, Hosts And Repositories

https://1.bp.blogspot.com/-fyASA-yB9kc/YGvW-uxGEHI/AAAAAAAAVyA/AF28Zfj0YGMRZOKl3BKILzCDA_nwz8BIACNcBGAsYHQ/w640-h360/DF_Vulnerability3.png The Deepfence Runtime Threat Mapper is a subset of the Deepfence cloud native workload protection platform, released as a community edition. This community edition empowers the users with following features:

1.
Visualization: Visualize kubernetes clusters, virtual machines, containers and images, running processes, and network connections in near real time.

2.
Runtime Vulnerability Management: Perform vulnerability scans on running containers & hosts as well as container images.

3.
Container Registry Scanning: Check for vulnerabilities in images stored on AWS ECR, Azure Container Registry, Google Container Registry, Docker Hub, Docker Self-Hosted Private Registry, Quay, Harbor, Gitlab and JFrog registries.

4.
CI/CD Scanning: Scan images as part of existing CI/CD Pipelines like CircleCI, Jenkins & GitLab.

5.
Integrations with SIEM, Notification Channels & Ticketing: Ready to use integrations with Slack, PagerDuty, HTTP endpoint, Jira, Splunk, ELK, Sumo Logic and Amazon S3. Live Demohttps://deepfence.io/community-demo-form/ ArchitectureA pictorial depiction of the Deepfence Architecture is below https://1.bp.blogspot.com/-SdrnhiIcUb0/YGvWBf3xMfI/AAAAAAAAVxk/RxNY1c7cYm0dqrY2c9FK6WBMG5u0AZcgwCNcBGAsYHQ/w640-h360/DF_Architecture.png Feature AvailabilityFeatures Runtime Threat mapper (Community Edition) Workload Protection Platform (Enterprise Edition) Discover & Visualize Running Pods, Containers and Hosts
✔️
(unlimited)
✔️
(unlimited) Runtime Vulnerability Management for hosts/VMs
✔️
(unlimited)
✔️
(unlimited) Runtime Vulnerability Management for containers
✔️
(unlimited)
✔️
(unlimited) Container Registry Scanning
✔️

✔️
CI/CD Integration
✔️

✔️
Multiple Clusters
✔️

✔️
Integrations with SIEMs, Slack and more
✔️

✔️
Compliance Automation
❌

✔️
Deep Packet Inspection of Encrypted & Plain Traffic
❌

✔️
API Inspection
❌

✔️
Runtime Integrity Monitoring
❌

✔️
Network Connection & Resource Access Anomaly Detection
❌

✔️
Workload Firewall for Containers, Pods and Hosts
❌

✔️
Quarantine & Network Protection Policies
❌

✔️
Alert Correlation
❌

✔️
Serverless Protection
❌

✔️
Windows Protection
❌

✔️
Highly Available & Multi-node Deployment
❌

✔️
Multi-tenancy & User Management
❌

✔️
Enterprise Support
❌

✔️ Getting StartedThe Deepfence Management Console is first installed on a separate system. The Deepfence agents are then installed onto bare-metal servers, Virtual Machines, or Kubernetes clusters where the application workloads are deployed, so that the host systems, or the application workloads, can be scanned for vulnerabilities.

A pictorial depiction of the Deepfence security platform is as follows: https://1.bp.blogspot.com/-pfIlgUgOn3M/YGvWW2AzGXI/AAAAAAAAVxs/hasGHDhcsW83HLh96-DGhW6eheNKi9MZgCNcBGAsYHQ/w640-h360/DF_DeploymentDiagram_New.png Deepfence Management ConsolePre-Requisites for Management ConsoleFeature Requirements CPU: No of cores 4 RAM 16 GB Disk space At-least 120 GB Port range to be opened for receiving data from Deepfence agents 8000 - 8010 Port to be opened for web browsers to be able to communicate with the Management console to view the UI 443 Docker binaries At-least version 18.03 Docker-compose binary Version 1.20.1
Following table gives the number of nodes that can be supported with different console machine configurations assuming a single node deployment of console. Memory optimised instances are shown to perform better.
CPU RAM Nodes supported 4 cores 16 GB RAM 250 nodes 8 co[...]

10 viewsFeed Reader Bot, 15:44

About

Blog

Apps

Platform