ESProfiler Handbook
Models

Platform Framework Matrix V2

Backend design for the Platform Framework Matrix view.

The framework matrix should present 4 main statistical information:

  • Coverage (and a break down by relationship)
  • Product Cost
  • Product Count
  • Priority (with regards to threats)

The matrix was designed as an instance of the CentralFramework object utilized by MFS and CPS. The CentralFramework also has a list of nodes which are an object of type CentralFrameworkNode.

Implementation status (as of the current main branches). There is no PlatformFrameworkMatrix or CentralFrameworkMatrix class, and CPS has no matrix endpoint. The view was built in platform-api as the Framework Collider: FrameworkCollider, FrameworkColliderNode and FrameworkColliderAnalytics in com.esprofiler.platform.capability.collider, served from GET /api/v1/collider/{frameworkRoot}. In the platform UI it is the Frameworks page under Security stack (route /portfolio/frameworks/:framework), with an Overview tab (products, vendors, annualized cost and coverage) and a Framework tab (the node canvas with coverage, priority and product filters). The sections below keep the original design. JSON samples and the field-by-field build notes are in the dropdowns.

CentralFramework and CentralFrameworkNode do exist, in MFS (com.esprofiler.mfs.centralframeworks.fdm.dto.output) and in platform-api (com.esprofiler.platform.frameworks.fdm.dto.output). Both extend the shared Framework and FrameworkNode models. A CentralFramework serializes with its id, root, name, version, type, privacy and nodes. Null fields are omitted.

The version defaults to the latest version of the framework when the root is given with no version or as root~ (for example NIST-CSF~). This is resolved in CentralFrameworkModalService.frameworkModelGet using PathParser.ParsedPath.isLatestVersion(). The collider controller appends ~ to a root that has none.

This object however was to be overloaded to include the mapping information when retrieved as a matrix. Hence the node object would have a list field called mappings which can be empty to indicate there is no mapping on it and an rdm object indicating what RDM the matrix is loaded with. In addition to this field would be the statistical information mentioned above. The dropdown has the original PlatformFrameworkMatrix sample (some fields from CentralFramework and CentralFrameworkNode are omitted). It is the original design. The shape the API returns is in the build notes below it.

In this example:

  • rdm holds the RDM information the matrix is loaded with.
  • path holds the node's Path object.
  • analytics.priority is a percentage value of the aggregated priority on nodes.
  • analytics.sourceCount is the count of unique sources.
  • Under analytics.coverage, each relation has:
    • count: the integer count of mappings with this relation
    • coverage: a percentage value of the aggregated coverage on nodes
    • sources: the ids of the sources mapped with this relation
    • cost: the cost information

As built, analytics.coverage is a single float, the breakdown by relationship is relationshipDistribution, cost is one total, and nodes have no mappings list. FrameworkColliderService in platform-api builds the response itself. Field names, the original CPS request, and the endpoint steps are in the dropdowns.

Subsequently, more product information such as utilization from assertion and deep research can be paired with this to show even greater insights. The collider already includes the reality* fields (derived from assessed mapping claims) and product utilization and sentiment in the index.

Copyright © 2026