New Features

Compound Risk Metrics

We've introduced several new cross-domain compound risk metrics to track toxic combinations of security risks.

Compound risk metrics offer a way to detect and measure significant threats created by toxic combinations of security risks. A toxic combination is when multiple risks or control gaps from different areas of cybersecurity combine, creating a higher overall threat that attackers can exploit.

The following compound risk metrics are currently available in Panaseer.

• Device coverage and vulnerabilities with owner phishing tests: The number of devices with vulnerabilities whose owner has received a phishing test.
• Devices hosting applications with vulnerabilities: The number of devices in the Panaseer Inventory hosting applications.
• Devices with vulnerabilities hosting applications: The number of devices hosting applications with vulnerabilities.
• Unique Devices associated with people: The number of devices with relationships to people.
• Unique devices hosting applications: The number of devices in the Panaseer Inventory hosting applications.
• Unique Devices not hosting applications: The number of devices in the Panaseer Inventory not hosting applications.
• Unique people who have received phishing tests (includes accounts information): The number of people who have received phishing tests.
• Unique people with admin accounts to access devices (includes devices tool coverage information): The number of people with admin accounts to access devices.
• Vulnerability detections with device coverage information: The number of vulnerability detections on devices.

See Compound risk metrics for more information.

Isolated Connector testing

Panaseer now includes support for discreet environments so that you can test and verify Connectors in isolation before rolling them out for use in your production environment.

Testing Connectors in isolation reduces the risk of system failures or user disruption, ensuring a smoother and more reliable rollout to your stakeholders.

Weighting in the Dashboard score

We’ve introduced weighting in Dashboard scores so that you can assign different levels of importance to metrics. This calculates a score that is a more accurate representation of the overall health of the initiative that the dashboard covers.

Weighting is also available when calculating the overall score in the Controls Scorecard.

On a Dashboard, you can edit weighting under ... > Edit weighting.

Dashboard score weighting uses a three-level system in which you can assign one of three tiers of importance to a metric:

• 1: This is the default and is of medium importance.
• 0.5: The lowest level of importance with half the influence of level 1 metrics.
• 2: The highest level of importance with double the influence of level 1 metrics.

In the image below, ID.SC-2 has a weight of 2, ensuring that it has the most influence on the overall Dashboard score. Whereas ID.AM-1 has a weight of 0.5, giving it the least influence on the score.

All metrics are set to level 1 weight by default.

Metrics using three-level weighting to assign relative importance

See Weighting in the Dashboard score for more information.

Feature Enhancements

SDC v2.1.0 updates and improvements

SDC v2.1.0 includes several functionality and maintenance updates.

Your organization must update to SDC v2.1.0 to take advantage of the roadmap improvements to Panaseer’s data ingest pipeline in 2025.

• Multiple Connector instances: We’ve improved support for multiple instances of the same Connector deployed to an SDC.
  Data Management Center (DMC) data updates automatically to reflect changes on sibling Connector instances.
• Start-up resilience improvements: We’ve made the start-up of nonessential components more reliable, improving performance.
• Truststores on mounted volumes: Accessing a Truststore from a mounted volume, rather than the main operating system, can improve performance and security as well as simplify future updates.
• Connector upgrade improvements: Upgrading Connectors is now more reliable, saving you time.
• Improved logging and debug information: Component messages are now categorized for clarity so you can debug more effectively.
• Server command retrieval: We’ve improved command retrieval so that you cannot pull instructions from the server before they're ready for use.
• Isolated Collector testing: We’ve added support for discreet environments so that you can test and verify Connectors in isolation before rolling them out for use in your production environment.

Business Logic updates and improvements

We’ve improved the performance of the preview breakdown and table when you create or edit Business Logic rules. The new preview produces results faster, allowing you to create complex logic more quickly.