Dashboard Essentials
Dashboard Essentials
Understanding the Dashboard
What This Covers
This guide explains the Steel Security dashboard and how to interpret the information it provides.
The dashboard gives you a high-level view of your site's security posture and helps you prioritize next steps.
What the Dashboard Shows
The dashboard provides a summary of your site’s current security state.
It is designed to answer three key questions:
- What risks exist on this site?
- How severe are those risks?
- What should I do next?
Key Sections
Scan Summary
The Scan Summary reflects the results of your most recent scan.
It includes:
- total findings detected
- breakdown by severity (if applicable)
- overall Scan Risk Score
This gives you a quick understanding of your current risk level.
Scan Risk Score
The Scan Risk Score represents the overall risk level of your site based on detected findings.
- Higher scores indicate greater risk
- Lower scores indicate a more secure configuration
The score is intended as a guideline, not a perfect measurement.
Focus on the underlying findings rather than the number alone.
Recent Findings
This section highlights the most relevant issues detected during the last scan.
Each finding includes:
- a description of the issue
- why it matters
- recommended next steps
Use this section to quickly identify what needs attention.
Hardening Overview
The dashboard also summarizes available hardening opportunities.
This may include:
- protections that can be applied
- current hardening status
- areas where improvements can be made
Hardening actions are optional and should be applied thoughtfully.
How to Use the Dashboard
A typical workflow:
- Review your Scan Risk Score
- Identify high-risk findings
- Open the Scan page for detailed results
- Apply hardening where appropriate
- Re-scan to confirm improvements
The dashboard helps you decide where to focus, not perform the work itself.
What the Dashboard Does Not Do
The dashboard does not:
- run scans automatically
- make changes to your site
- apply hardening actions
It is a summary and navigation layer, not an action layer.
When to Check the Dashboard
Use the dashboard:
- after running a scan
- after applying hardening
- after updates, migrations, or restores
- as part of routine maintenance
Common Questions
Why does the dashboard not update automatically?
The dashboard reflects the most recent scan results.
To refresh the data, return to the Scan page to trigger a new scan.
What should I focus on first?
Start with:
- high-risk findings
- exposed files
- configuration issues
These typically represent the most immediate concerns.
Is a low score “secure”?
A low score indicates fewer detected risks, but no system is ever completely risk-free.
Use the score as a guide, not a guarantee.
Tips
- Use the dashboard to prioritize, not diagnose
- Always review the full Scan results before making changes
- Apply hardening incrementally and verify results
What to Do Next
After reviewing the dashboard:
- Open the Scan page for detailed findings
- Review individual issues
- Begin applying hardening controls
Related
Reviewing Findings
What This Covers
This guide explains how to review and interpret the findings from a Steel Security scan.
Understanding your findings is the key step before applying any hardening changes.
Where to View Findings
Findings are available on the Scan page.
To access them:
Each finding represents a potential security risk or configuration issue.
What a Finding Represents
A finding indicates something on your site that may:
- expose sensitive information
- weaken security
- reflect an unsafe or outdated configuration
- indicate leftover or unnecessary files
Not all findings require immediate action, but all should be understood.
Information Provided for Each Finding
Each finding includes:
- What was detected
- Why it matters
- Recommended next steps
This context is designed to help you make informed decisions, not just react to alerts.
How to Prioritize Findings
Start by focusing on:
High-Risk Findings
These typically include:
- exposed backup or database files
- configuration leaks
- publicly accessible sensitive data
These should be addressed as soon as possible.
Configuration Issues
Examples include:
- debug mode enabled
- unnecessary exposure of system information
These may not be immediately critical but should be corrected.
Informational Findings
Some findings may be:
- informational
- intentional based on your setup
Review these carefully before taking action.
When to Take Action
You should consider taking action when:
- the finding exposes sensitive data
- the risk is publicly accessible
- the issue is not required for your workflow
If a finding is intentional, you may choose to leave it as-is.
Applying Fixes
Some findings can be addressed using Steel Security hardening features.
Others may require:
- manual file removal
- configuration updates
- hosting-level changes
Always review the recommendation before applying changes.
Safe Approach to Fixing Issues
Follow this workflow:
- Review the finding and understand the risk
- Confirm whether the issue is intentional
- Apply the recommended fix or hardening
- Re-run the scan to verify resolution
Avoid applying multiple changes at once without verification.
What Not to Do
- Do not blindly apply all fixes
- Do not remove files without understanding their purpose
- Do not assume all findings are critical
Steel Security is designed to inform, not automate decisions.
Common Questions
Why am I seeing findings on a new site?
Many WordPress installations include:
- default files
- leftover artifacts
- development configurations
These are common and should be reviewed and cleaned up.
Can I ignore a finding?
Yes, if:
- the behavior is intentional
- the risk is understood and accepted
However, you should document or remember why it was ignored.
Why does a finding still appear after fixing it?
- Ensure the change was applied correctly
- Return to the Scan page to trigger a new scan
- Confirm the issue is fully resolved
Tips
- Focus on quality, not quantity of fixes
- Address high-risk issues first
- Make changes incrementally
- Re-scan after each set of changes
What to Do Next
After reviewing your findings:
- Identify the most important issues
- Begin applying hardening controls
- Re-scan to confirm improvements