Control who can administer the server

Keep an accurate list of administrator accounts and access methods. Remove unused access and use strong credentials with available additional security controls. Ensure there is a safe recovery method before restricting normal management access.

Maintain the software that is exposed

Track the operating system, panel, PHP versions and customer applications. Apply supported updates using the relevant documentation. A security product or kernel live-patching tool covers only part of the maintenance work.

Make monitoring useful

Decide who investigates unusual login attempts, file detections and outbound mail activity. Keep enough relevant logs to understand an event without sharing unnecessary customer data. Review overlapping scanners and rules before adding more tools.

Keep recovery independent

Maintain recoverable backups and test a restore. Security and backup software have different jobs. Choose compatible tools and use the LicenseCage installation guides for their activation, alongside the administrator procedures needed for configuration.

A practical example

Security work becomes easier to manage when it is tied to specific responsibilities. Identify who patches the server, reviews alerts, handles credentials and tests recovery. A customer-facing hosting panel, the provider account and the server operating system can each have separate access controls, so securing only one of them leaves gaps.

Checks to make

  • Review administrator access and remove accounts that no longer need it.
  • Maintain the operating system, panel and hosted applications through supported update paths.
  • Scope firewall access to the services and management routes the server actually needs.
  • Test backups and keep an incident recovery route outside the affected server.

Making the decision

A security license can support this process but does not replace ownership of it. Investigate alerts with preserved evidence and avoid broad changes made only to silence a warning. Revisit the checklist after adding a new panel, backup destination, integration or customer-access workflow.