Security Advisor checks server configuration and reports findings with suggested actions. Treat it as an evidence-based maintenance input, then assess each change against the server’s actual workloads and management responsibilities.
IN THIS ARTICLE
01 What you need before you begin
Confirm administrator privileges and keep a recent recovery plan. Record installed services, provider-managed components and any existing documented exceptions.
02 Turn WHM Security Advisor findings into an action plan
- Open Security Advisor and allow its scan to finish. Save the findings and scan time.
- Prioritise severe warnings, then investigate possible issues and informational improvements. Read each explanation rather than responding only to its colour.
- Follow the linked supported configuration screen for one finding at a time. Identify whether the proposed action requires a maintenance window, restart or provider involvement.
- Apply the approved correction and verify relevant services, such as login, websites or mail, still work.
- Choose Scan Again and record the new result. Document legitimate exceptions with an owner and review date.
03 Confirm the expected result
The finding should be resolved or have a clear, justified follow-up action. A change is complete only when the affected service still functions and the intended protection is effective.
04 Troubleshoot unexpected results
Virtualisation or managed-service boundaries can make some operating-system controls unavailable. Ask the provider to address those rather than forcing unsupported changes. If a warning persists, compare the active configuration and service state with the expected setting.
05 Example: turn a Security Advisor warning into a controlled change
Read the warning's explanation and determine its scope before applying a fix. A recommendation affecting a shared server can alter several customers' workloads, so review dependencies and the recovery plan first.
Keep a short change record: the warning, current setting, proposed correction, affected services and verification method. Apply one related change at a time where practical, then rerun the relevant check and test the services that depend on it.
Does clearing every warning prove the server is secure?
No single report proves that. Security Advisor is one source of administrative guidance alongside patching, access reviews, backups, monitoring and application maintenance. Some findings need context rather than a reflexive configuration change.
If a correction breaks an application, preserve the error and review the specific dependency instead of disabling a broad set of protections. For a server service managed by us, contact our team before changing a policy that affects all accounts. Provide the warning text and relevant configuration, with secrets removed. We can help assess the practical impact and choose a supported correction rather than treating the report as a cosmetic checklist.
Does a clean scan prove the server is secure?
No. The tool checks a defined set of conditions. Application vulnerabilities, stolen credentials, custom code and operational access still require updates, monitoring and periodic review.