asked on
server health check scope
From a virtual server perspective (running a version of Windows Server likely >=2016 onwards), as an administrator if you were performing a quick across the estate health check of your server population (for arguments sake 50 servers), what is the critical information you would expect the health check to focus on. I don’t work in a support/admin role, but I was thinking the ‘big five’ should probably be things like:
- Is the server and data included in backup selections?
- Is the OS and all major applications supported by the vendor in terms of security updates?
- Have all the relevant latest security patches applied to the OS and all local applications.
- Are monitoring & alerting agents/applications installed where expected and actively reporting back on key health metrics (e.g. available disc space, memory, processing, critical error messages etc).
- Are all security applications and safeguards enabled and operating as expected (e.g. firewall, local anti-virus) etc.
Is there anything else that is not on my list that would be higher up your priority checks as an admin, and any other things that you would add to the checklist that aren't covered with my priority 5. I appreciate servers running specific roles may warrant additional/other checks, but I was thinking on the bare bones essentials that should be considered for every server.
N/B a 'health check' is what I have seen others refer to such a procedure with, but I'd also be interested to learn if you use any other terminology for such a check, as it may help me find other information and recommended checks online.
Changing passwords on a regular basis reduces the danger of live passwords falling into the hands of a hacker. Checking MFA for privileged accounts will be one of the item.
Remote console, remote reboot, and rescue mode are called the 3 essential tools for remote server management. You need to make sure that these will work in case you need them. And yes access with MFA too.
here is useful list
ASKER