We had an internal debate on fulfilling auditor's requirement for a batch of critical PCs
(that are used for critical processing) : audit requires that login activities to the built-in local
administrator (which we had renamed) need to be reviewed regularly by another team
(it's used by End User support team on rare occasions only when a PC lost network
connectivity to central management tool like SCCM) :
as security person, I find it unsustainable to regularly review each time the local admin
is used to login & Audit agrees that if we disables it, then review is not needed.
Somehow, there's a way to tweak it (by replacing a binary with cmd.exe) to boot up the
PC in Safe mode so that we can get to command prompt to re-enable it back for recovery
only (I deem just simply for recovery of a 'disconnected PC' don't need review).
There's debates raised internally:
a) is disabling local admin a more secure practice than reviewing the activities (which I
felt no organizations have the resource to have a compliance person to follow
when login to the local admin is used). Which of the two is more practical?
b) another proposal is to install these critical PCs with SPlunk agents to pipe its
events to Splunk so the events of using local admins is sort of 'monitored' by
c) Is disabling local admin considered a bad / unsustainable practice? Any articles
to support disabling or against it is appreciated