[ Applies to ] StorageGuard 9.2 and later / All supported storage, backup, SAN and cloud systems / Windows and Linux deployments
The Baseline Configuration overview is where you start after each risk analysis. It shows how well your storage and backup systems follow the baseline policies you enabled, where the biggest gaps are, and whether things are getting better. Use it to decide what to fix first before you open the findings list.
In this article
Before you begin
- At least one risk analysis has completed. See Run and schedule a risk analysis.
Open the overview
Go to Baseline Configuration > Overview. This is also the page StorageGuard opens when you sign in. Hover over any chart to see the exact numbers.
Read the compliance score
| Widget | What it tells you |
|---|---|
| Baseline compliance score | One grade for your whole deployment, from the last analysis: the share of checks that passed. A is above 90, B is 80 to 90, C is 70 to 80, D is 50 to 70, and F is below 50. The ring around the grade shows the share of systems that are compliant (lighter), non-compliant (darker) and not scanned or unknown (lightest). |
| Score by Policy | A grade for each enabled policy, such as CIS Controls or NIST, calculated the same way for that policy's checks. The ring shows compliant checks (green), non-compliant (red) and unknown (gray), where there wasn't enough data to decide. |
Tip: Treat the score as a trend, not a target. A score drops when you enable a stricter policy or add new systems, even though nothing got worse. Compare it with last month's score for the same policies and scope.
Find where the problems are
| Widget | What it tells you | Use it to |
|---|---|---|
| Findings severity | Open findings by severity: critical, high, medium and low. | Size the work, and see how much is critical. |
| Findings by technology (table) | For each system type: how many systems, how many open findings, the average per system, and the type's score. | Spot the platform with the most findings per system, which is usually where one fix repeats across many systems. |
| Findings by technology (pie) | Open findings split by technology. | See which platforms dominate. |
| Findings by asset type (pie) | Open findings split by domain: storage, backup, cloud and so on. | Decide which team to involve. |
| Top non-compliant systems | The systems with the most open findings, each bar split by severity. | Pick the systems to remediate first. |
See whether you're improving
| Widget | What it tells you |
|---|---|
| Open/New risks over time | Open findings over time, and how many of them are new. A rising line means findings are appearing faster than they're fixed. |
| Risk findings solved | How many findings were resolved over time. |
| Risk aging | How long open findings have stayed open: last week, 1 to 4 weeks, 1 to 3 months, and longer. Old findings are either accepted risks that should be suppressed, or work nobody owns. |
See the overview as another user
If your account isn't limited to a scope, you can use View as at the top of the page to see the dashboards as a particular user profile would, for example to check what a team sees before you share the page with them.
[ Next step ]
Related articles
- Review and act on a configuration finding
- Run and schedule a risk analysis
- Choose and create baseline policies
[ Still need help? ]
Our support team can help with reviewing and remediating findings. Submit a request
Comments
0 comments
Please sign in to leave a comment.