16.7 Multi-Factor Authentication. Background 16.4.4. Privileged Access Management (PAM) – sometimes also described as Privileged Account Management, refers to a set of processes and tools for granting, controlling, monitoring, and auditing privileged access. 16.4.5. A Privileged Account is a user account with high levels of access to systems, devices and data. Privileged accounts may, for example, be able to install or remove software, delete data, upgrade operating systems, or modify system or application configurations. They may also have access to data that is not normally accessible to standard users. 16.4.6. Privileged Accounts invariably have direct or indirect access to most or all IT assets of an agency or organisation. When used improperly or maliciously, privileged accounts represent a significant security threat to operations, often exposing sensitive data, impeding operations or damaging IT systems. Any compromise of these accounts is, therefore, a significant business, operational and reputational risk. 16.4.7. Risks associated with privileged accounts have increased in recent years with the expansion of endpoints and use of new technologies including Cloud, Internet of Things (IoT) and the rapid and significant increase in remote and work from home following the onset of the COVID-19 pandemic. 16.4.8. Managing, controlling, monitoring and reviewing privileged access is fundamental to mitigating the risks posed by insider and external threats, privilege escalation threats, preventing unauthorised data access and data breaches, and meeting compliance requirements. 16.4.9. There are many types of privileged access including: Root, Domain and other Administrator accounts are typically used for installing, updating and removing software, changing configurations and administering system passwords. Service Accounts, which may include local or domain accounts, are typically used for running processes, such as web servers, database servers, and application servers. These may also include the ability to change passwords. Emergency Accounts, sometimes referred to as “DRP”, “firecall” or “breakglass” accounts. While access to emergency accounts normally requires managerial approval as a security measure, they are typically an inefficient manual process with limited auditability. System or Application Accounts are characteristically used by devices and systems for running operating system components and owning related files. 16.4.10. Traditional administrative or management solutions are typically based on strong password management. Modern systems, especially in a cloud environment, require a more structured and robust means of access control and management. This should include the use of Multi-Factor Authentication (See Section 16.7 - Multi-factor Authentication) to provide access to Privileged Accounts. 16.4.11. In secure environments, privileged accounts should be reserved for network and system administrators to manage the access to and oversight of sensitive information and resources in support of normal agency or organisational operations. 16.4.12. The characteristics and capability of privileged accounts are described at 16.3.3. It is important to note that systems themselves, as well as human users, may have privileged account access. As such it is important to clearly and individually identify all real persons, systems and devices with privileged account access. 16.4.13. Access accounts or channels may have the following characteristics: Regular access channels—protected channels that are subject to standard IT controls; Privileged access channels (PACs)— channels that might circumvent regular controls but are deemed necessary and legitimate operational channels for reasons of practicality or cost; Unintended channels not demanded by any technical or business requirement and represent a vulnerability. Attacks on Privileged Accounts 16.4.14. Privileged accounts frequently allow unrestricted access the IT infrastructure, often including data residing on those systems. The very high level of access and capability associated with privileged accounts makes them a prime target for external attackers and malicious insiders. A compromise of a privileged account can be extremely damaging and may even cripple systems, such as in ransomware attacks. 16.4.15. Compromised privileged accounts represent one of the largest security vulnerabilities an organisation can face today. A compromise will allow attackers to take full control of an organisation’s IT infrastructure, disable security controls, steal confidential information, commit financial fraud and disrupt operations. Stolen, abused or misused privileged credentials are identified in a very high proportion of successful breaches. 16.4.16. Common attack methods may include: Probes and scans; endpoint targeting; System and design vulnerability exploitation; Social engineering (including phishing, email spoofing, etc); and Malware implants. Governance and Control 16.4.17. Privileged Accounts are frequently used to deploy and maintain IT systems and necessarily exist in nearly every connected device, server, database, and application. Privileged Accounts may extend beyond an agency-controlled IT infrastructure to include, for example, employee-managed corporate social media accounts. Most agencies and other organisations can typically have many more privileged accounts than employees, sometimes as many as two or three times the number of employees. It is not unusual for some privileged accounts to be unidentified, overlooked, unmanaged, and therefore unprotected. 16.4.18. Governance ensures that privileged accounts are properly approved, controlled, monitored and decommissioned throughout their entire lifecycle. A PAM Policy defines the roles, policies and mechanisms for access requests, as well as the workflow for privileged access approvals and delivery. Monitoring and auditing ensure that account permissions and usage remain appropriate over time. PAM governance is a fundamental part of IT Governance as it can influence other IT security systems, such as identity and access management systems. 16.4.19. In order to support strong IT Governance, it is vital that security efforts are coordinated and technology investment managed. This includes the 217 Version_3.5__January-2022

Select target paragraph3

Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents