Skip to content

Releases: deepfence/ThreatMapper

v1.4.2

12 Jan 14:01
Compare
Choose a tag to compare

What's Changed

New Contributors

  • @j771 made their first contribution in #765

Full Changelog: v1.4.1...v1.4.2

v1.4.1

03 Oct 17:43
7589a5f
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v1.4.0...v1.4.1

v1.4.0

10 Aug 08:11
ca0f5b1
Compare
Choose a tag to compare

What's Changed

Full Changelog: v1.3.1...v1.4.0

v1.3.1

29 Jul 10:43
1835df3
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v1.3.0...v1.3.1

v1.3.0

15 Mar 19:07
c1ba8a3
Compare
Choose a tag to compare

ThreatMapper 1.3.0 Release

ThreatMapper 1.3.0 is a feature release, with a number of enhancements and fixes:

New Features

  • Secret Scanning: Scan containers and host filesystems, looking for possible unprotected secrets such as access tokens, keys and passwords.
  • SBOM Generation: Generate and export runtime SBOMs (Software Bill of Materials) from running workloads and hosts.
  • Updated Vulnerability Scanning: using Anchore syft and grype.
  • Attack Path Visualization: improved visualization identifes and classifies more attack path types

Upgrading to ThreatMapper 1.3

Please note that versions of the sensor agent prior to the 1.3 release will not interoperate with the ThreatMapper 1.3 management console, due to the architectural changes in SBOM generation and vulnerability scanning. To upgrade from an earlier ThreatMapper release:

  • Update the Management Console to version 1.3.0
  • Update sensor deployments to version 1.3.0

Please see the documentation for more information.

Full Changelog: https://github.com/deepfence/ThreatMapper/commits/v1.3.0

v1.2.0

08 Mar 09:20
Compare
Choose a tag to compare

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