Dashboard Overview

Purpose

This article explains what the CMSSPM Overview Dashboard is, what it is intended to show, and how to use it as the starting point for understanding the site’s security posture. The dashboard is designed to give administrators a quick, organized view of overall status, scoring, and the areas that need attention first.

Where to find it

You can access the dashboard from the Posture Management menu in wp-admin after the plugin is installed and activated. For most users, this is the main landing page of the plugin and the first place to review results after running a scan.

What the dashboard shows

The Overview Dashboard is meant to present a high-level summary rather than every technical detail at once. In general, it brings together the most important posture information in one place, such as:

• the overall security posture score,
• section or category status,
• counts of findings by type or severity,
• recent scan-related information,
• high-priority items that may need review first.

This allows you to understand the general condition of the site before drilling into any one security area.

How to use it

The dashboard is best used as a starting point for prioritization. Rather than reading every individual finding first, you can begin by looking at the overall score, identifying weaker categories, and then moving into the related sections for more detail.

A practical workflow usually looks like this:

1. Open the Overview Dashboard.
2. Review the current overall posture score.
3. Look for categories with weaker results or more open findings.
4. Open those sections to review the underlying findings.
5. Make changes, rescan, and use the dashboard to measure improvement over time.

This makes the dashboard useful not just as a status page, but as the main control point for ongoing posture improvement.

How it relates to scans and scoring

The dashboard depends on scan data to be meaningful. If a site has not been scanned yet, the dashboard may show limited information, baseline values, placeholders, or prompts encouraging the first scan.

Once scan results exist, the dashboard uses them to summarize the current posture and reflect how findings affect scoring across different areas. Findings that are open, unresolved, or higher-weighted may lower what you see on the dashboard, while findings marked as mitigated can be treated as passing for scoring purposes.

Because of that, the dashboard should be understood as a current operational summary of stored scan data, not just a static page.

What it does not replace

The Overview Dashboard is not meant to replace the detailed section pages or the technical logic behind individual checks. It helps you see where to focus, but it is not the complete explanation for why every finding exists or exactly how every score was calculated.

For deeper review, you should move from the dashboard into the relevant category pages, finding details, and supporting documentation.

Notes and scope

This article is a plain-English introduction to the dashboard experience. It does not document every widget, field, chart, or layout element that may appear in a specific version of the plugin.

As CMSSPM develops, the dashboard may expand to include additional summaries, history views, trends, or workflow shortcuts. This article should remain focused on the dashboard’s purpose as the high-level entry point into the plugin.