Security best practices for administrator accounts
Follow these best practices to improve the security of your administrator accounts and by extension, of your business as a whole.
If someone manages to get the admin password, 2-Step Verification (2SV) helps protect the account from unauthorized access. It’s especially important for super admins to use 2SV because their accounts control access to all business and employee data in the organization.
There are several 2SV methods, including security keys, Google prompt, Google Authenticator, and backup codes. Security keys are small hardware devices that are used for second factor authentication. They help to resist phishing threats and are the most secure form of 2SV.
Super admins can manage all aspects of your company’s account and can reset another’s password.
Super admins should use a separate user account for day-to-day activities. They should only sign in to their super admin account when they need to perform specific super admin duties, such as configuring 2SV or helping another admin recover their account.
Staying signed in to a super admin account when you aren’t doing specific administrative tasks can increase exposure to phishing attacks. Super admins should sign in as needed to do specific tasks and then sign out.
A business should have more than one super admin account, each managed by a separate individual. If one account is lost or compromised, another super admin can perform critical tasks while the other account is recovered.
If there are multiple super admins and each uses firstname.lastname@example.org to sign in, you can’t see which super admin is responsible for activities in the audit log. Each super admin should have an identifiable admin account.
For example, if Maria and James are super admins, they should have per-user super admin role accounts and user accounts:
- email@example.com, firstname.lastname@example.org
- email@example.com, firstname.lastname@example.org
To encourage using a super admin account only when needed, delegate normal day-to-day administrative operations to user accounts. For example, you could delegate a frequent activity such as resetting passwords to a user account but allow only super admins to delete an account.
When delegating admin privileges, use the model of least privilege. In a model of least privilege each admin has access only to the resources and tools they need for their typical tasks in the day-to-day account.
Monitor admin activity and track potential security risks by setting up admin email alerts for certain events, such as suspicious sign-in attempts, compromised mobile devices, or changes by another admin.
When you turn on an alert for an activity, you receive an email each time that activity happens.
The Admin audit log is another tool to monitor admin activity. The Admin audit log shows a history of every task performed in the Google Admin console, which admin performed the task, the date, and the IP address where the admin signed in.
Activity from the super admin appears in the Event Description column as _SEED_ADMIN_ROLE, followed by the username.
Admins should add recovery options to their admin account.
If an admin forgets their password, they can click the Need help? link on the sign-in page and Google will send a new password via phone, text, or email. To do that, Google needs a recovery phone number and email address for the account.
If a super admin can’t reset their password using email or phone recovery options, and another super admin isn’t available to reset the password, they can contact Google Support.
To verify identity, Google asks questions about the organization’s account:
- The date the account was created.
- Original secondary email address associated with the account (email used to sign up).
- Google order number associated with the account (if applicable).
- Number of user accounts created.
- Billing address linked to the account.
- Type of credit card used and its last 4 digits.
Google also asks the admin to verify the DNS ownership of the domain, so the admin needs to have the credentials to edit the domain DNS settings with their registrar.
Admins should enroll more than one security key for their admin account and store it in a safe place. If their primary security key is lost or stolen, they can still sign in to their account.
If an admin loses their security key or phone (where they receive a 2SV verification code or Google prompt), they can use a backup code to sign in.
Admins should generate and print backup codes in case they’re needed. Keep backup codes in a secure location.