ThreatMapper 1.2.0 Release
ThreatMapper 1.2.0 is a feature release, with a number of enhancements and fixes:
New Features
- Attack Path visualization: using analysis of network traffic, the Attack Path visualisation identifies vulnerable workloads that are open to internet traffic, even when they are behind multiple layers of proxies.
- Support for AWS Fargate workloads: ThreatMapper sensor agents may be deployed as sidecars to AWS Fargate workloads.
- Integration with Google Chronicle: push events, alerts and scan results to Google Chronicle for archiving and analysis.
Major Enhancements
- Improved 'most exploitable vulnerability' calculation: applying more weight to proximity to the attack surface and to active network connections, to better prioritize workloads at greater risk.
- Broader support for Kubernetes and containerd: a number of updates addresses issues where manual and automated scans of Kubernetes/containerd-hosted containers would fail.
- Enhancements to registry scans: including support for AWS ECR target account role ARN, better feedback on progress, and support for tag-based filtering of artifacts.
- Multiple UI and user experience improvements: the ability to invite users to the Management Console without the need to configure an email relay, and more metadata reported against containers and other workloads so you can more easily identify them.
Full Changelog: https://github.com/deepfence/ThreatMapper/commits/v1.2.0