Dashboards & Analytics
Use module dashboards and cross-module views to understand posture, deadlines, high exposure, assurance gaps and workload.
From summary metric to accountable action
PurpleWASP analytics surface the state of the underlying operational workspaces; they do not replace the source records or their decisions.
Start with the dashboard relevant to your role.
Confirm scope, period and status before interpreting a number.
Open the underlying records and relationships.
Focus on high, overdue, incomplete or deteriorating work.
Update the record in the workspace that owns the decision.
Read posture in context
Use the owning workspace when a metric needs explanation or action.
Risk analytics
Review active/high Risks, treatment and exception status.
AssetsAsset intelligence
Review Asset population, valuation, lifecycle and Risk coverage.
ControlsControl assurance
Review adoption, implementation and assurance activity in Control Management.
ComplianceCompliance posture
Review ISO 27001 ISMS progress, SOC 2 readiness, Cyber Essentials/Plus preparation, NIST CSF 2.0 Current/Target signals and CIS Controls v8.1 implementation readiness.
TPRMThird-party posture
Review tier distribution, due diligence, findings, reviews and monitoring.
PoliciesPolicy & document status
Review draft, approval, publication, review and awareness activity.
A dashboard should lead back to the source record
Use metrics as operational signals. The underlying workspace remains authoritative for applicability, Risk, Control effectiveness, tiering, certification evidence and other governed conclusions.
- Validate filters and reporting period before comparing values.
- Do not interpret totals without understanding scope and denominator.
- Use trends and overdue work to identify deterioration or stalled ownership.
- Follow scores back to the records, evidence and decisions that produced them; use Drivers / Improve Score where available instead of interpreting a percentage in isolation.
No guidance matches that search.