Dealing with a Compliance Alert in ControlUp

A user received a compliance alert about the "built-in" local Windows administrator account being in the local administrators group, which is a default and mandatory setting. There was discussion about how to deal with this issue and suggestions were made to check and exclude items in the scanning template. One user suggested that the setting could be more useful if it could identify other accounts and ignore the built-in "administrator" account. The issue was passed on to the secure DX PM.

Read the entire ‘Dealing with a Compliance Alert in ControlUp’ thread below:

Receiving a compliance alert regarding the "built-in" local Windows administrator account being in the local administrators group (which is default and mandatory on a windows machine). secureDX is flagging this as an "issue" yet it is by design and cannot be corrected? how to deal with this? any ideas?

@member check ur template u using to scan. U can exclude items u don’t want

Thanks Luke! will check this out! much apprecaited.

found it!! this setting would actually be more useful if it could identify other accounts and ignore the built in "administrator" account. If a user creates a backdoor account "root" or some other local or domain accounts are in local administrators group – would be helpful to identify these ones.

Thanks James I have passed on to the secure DX PM

Continue reading and comment on the thread ‘Dealing with a Compliance Alert in ControlUp’.  Not a member? Join Here!