Dashboards
Dashboards summarise what the rest of the CyberOptix CTEM Platform holds. They answer "how are we doing?" rather than "what do I fix?" - the second question belongs in Findings.
Executive Risk Overview
The default dashboard, and the one to send to someone who does not log in daily.
It holds the modeled figures, under the names an executive reader expects: five figures, five sections, and a link from each to the page where the work behind its figure is done. The Risk Posture page holds what you state and what the figures rest on, and the Remediation page holds the remediation options and the scenarios. The model version, the horizon, the coverage and the assessment confidence stand in the header beside the figures. A period selector at the top chooses the window the changes and the activity are read over: the last 30 days, 90 days or 12 months.
SCREENSHOT: the Executive Risk Overview dashboard.
The five figures
The strip at the top carries five figures, each its own and none a composite:
- Breach probability. The modeled 12-month breach probability: the likelihood that at least one entry path succeeds within the horizon, every exposure reachable from the internet whose reachability was observed being a path of its own, combined as the model combines materially distinct paths, with its change over the period you chose. The change is shown only when the earliest and the latest snapshot in the period are under one model version and were calculated by one method; otherwise the two figures are named and no difference between them is read as an improvement. Where no exposure meets the entry rule the card shows insufficient data, never zero, and the panel says what was left out and why.
- Expected annual loss. The modeled financial consequence over the horizon, or insufficient data where no business asset carries financial inputs. It is never zero for want of numbers.
- Material risk drivers. How many exposures stand on an attack path with a projected change, and how many of them require immediate action.
- Controls at risk. Distinct controls of the frameworks you adopted that an open finding is relevant to. Evidence an auditor will want to look at, not a conclusion about compliance.
- Verified risk reduction. The latest verified remediation's observed drop in breach probability, as a share of where it stood before, with the number of remediations verified in the period. It is shown only when the two observations are comparable.
The sections
Breach probability shows the modeled 12-month breach probability, what it is modeled over and what it leaves out (the entry paths and the internet-facing assets they stand on, and the externally reachable exposures not modeled as entries, by reason), what the figure can be under any dependence between the paths (no lower than the strongest single path, no higher than the paths added and capped at one, stated apart from confidence and coverage and never as a range of actual exposure), its change over the period, lateral movement, the validated attack paths and the business assets they reach, the assessment confidence, the trend over the period as one line per model version, and the figure by domain. The domain with the largest share is named as the primary driver; the shares of different domains overlap and do not add up to the overall figure.
Business & financial risk shows the expected annualized loss by business asset, the largest concentration as a share of the combined figure, and the single remediation projected to reduce it the most. A projection is a projection.
Compliance mapping shows, for each adopted framework that counts toward a compliance figure, how many of its controls are at risk and how many carry a critical gap, and which controls are most affected, by the identifier its publisher uses.
What is driving risk? ranks exposures by their breach contribution, the projected change when each alone is remediated, with the domain, the business assets reached, the financial exposure, the priority, and the status of the scenario that names the exposure. The contributions of two rows are never added together.
Risk reduction activity counts open exposures, exploitable paths (the attack paths validated end to end), exposures remediated in the period and remediations verified, and closes with an executive takeaway composed from the figures above.
Every figure here is modeled, not measured: the names are the ones an executive reader expects, the figures behind them are the model's own, and the model version, horizon, coverage and confidence beside them say how far to trust each. Modeled risk explains how to read them, and every section links to the page where the work that moves its figure is done.
Reading it
It is a trend instrument, not a work queue. A single snapshot tells you very little; what matters is direction, and the page says when a direction can be read: a change over the period is shown only when the two snapshots are comparable, and a change that crosses a model correction is named as one. A step at a version change is a model change, not a change in your posture; compare within a version. The work itself belongs in Findings and on Remediation, where a remediation is weighed before it is done and checked after.
Scope
The figures are computed per business unit and per zone when the attack paths are built, and are never added across units. With no selection the page shows the organization's figures. Select one business unit or one zone in the view filter to see its own: every attack path that reaches one of its assets, the drivers whose exposure is on one of them, and the scenarios, the activity and the compliance impact narrowed to it. A selection that names more than one unit is answered in words rather than with organization-wide figures under a unit's name. See Organizations, business units, and zones.
Reporting rather than watching
For anything that needs to leave the platform - a board pack, an auditor, a client - use Reports. A scheduled report delivers the same view on a cadence, which is what makes a trend legible over months.
API
The endpoints behind this section are in the API reference.
Next
- Findings and triage - acting on what a dashboard summarises
- Reports - sending it to someone who does not log in