Restricting Administrative Privileges
Download ACSC Protect Notice, Restricting Administrative Privileges (PDF), March 2016
First published 2012; updated March 2016
- Restricting administrative privileges is one of the Top 4 strategies in the Australian Signals Directorate’s (ASD) Strategies to Mitigate Cyber Security Incidents. This document has been developed by ASD to provide high-level guidance on how to effectively restrict administrative privileges.
Why should administrative privileges be restricted?
- Users with administrative privileges for operating systems and applications are able to make significant changes to their configuration and operation, bypass critical security settings and access sensitive information. Domain administrators have similar abilities for an entire network domain, which usually includes all of the workstations and servers on the network.
- Adversaries often use malicious code to attempt to exploit vulnerabilities in workstations and servers. Restricting administrative privileges makes it more difficult for an adversary’s malicious code to elevate its privileges, spread to other hosts, hide its existence, persist after reboot, obtain sensitive information or resist removal efforts.
- An environment where administrative privileges are restricted is more stable, predictable, and easier to administer and support, as fewer users can make significant changes to their operating environment, either intentionally or unintentionally.
Approaches which do not restrict administrative privileges
- There are a number of approaches which, while they may appear to provide many of the benefits of restricting administrative privileges, do not meet the intent of this strategy, and in some cases may actually increase the risk to an organisation's network. These approaches include:
- simply minimising the total number of privileged accounts
- implementing shared non-attributable privileged accounts
- temporarily allocating administrative privileges to user accounts
- placing standard user accounts in user groups with administrative privileges.
How to restrict administrative privileges
- The correct approach to restricting administrative privileges is to:
- identify tasks which require administrative privileges to be performed
- validate which staff members are required and authorised to carry out those tasks as part of their duties
- create separate attributable accounts for staff members with administrative privileges, ensuring that their accounts have the least amount of privileges needed to undertake their duties
- revalidate staff members' requirements to have a privileged account on a frequent and regular basis, or when they change duties, leave the organisation or are involved in a cyber security incident.
- To reduce the risks of using privileged accounts, organisations should ensure that:
- technical controls prevent privileged accounts from undertaking risky activities such as reading emails and opening attachments or browsing the web
- system administration is undertaken in a secure manner by implementing the guidance in the ASD Secure Administration publication.
- The Australian Government Information Security Manual assists in the protection of official government information that is processed, stored or communicated by Australian Government systems.
- ASD’s Strategies to Mitigate Cyber Security Incidents complements the advice in the ISM.
- ASD’s Secure Administration publication provides guidance on how to implement a secure and resilient enterprise administration environment.
Australian government customers with questions regarding this advice can contact ASD Advice and Assistance.
Australian businesses and other private sector organisations seeking further information should contact CERT Australia.