integration of PAM into the Information Security Policy, Systems Architecture, IT Security Strategy and Risk Management Plan. The sensitivity of data and operations should be assessed by undertaking an impact assessment. 16.4.20. Underpinning any PAM is the principle of enforcement of least privilege. This is defined as the minimisation of access rights and permissions for users, accounts, applications, systems, devices and computing processes to the absolute minimum necessary in order to perform routine, authorised activities and maintain the safe and secure operation of agency or organisational systems. 16.4.21. Enforcing the principle of least privilege assists agencies in minimising their systems attack surface, supporting audit and compliance though improved visibility. This also can reduce risk, complexity, and costs for agencies. 16.4.22. Provision of unnecessary system privileges or data access rights will magnify the impact of misuse or compromise of that users account and can even be devastating. Account privileges should be established to provide a reasonable but minimal level of system privileges and rights needed in order to support the purpose and role. The granting of elevated or excessive system privileges should be carefully controlled and managed. 16.4.23. Risks associated with access to privileged accounts include: Misuse of privileges; Increased attacker capability; Circumventing established security and oversight controls; Severe system disruption or failure; and Significant data compromise and/or loss. 16.4.24. The principles of PAM controls are to: Establish and maintain an inventory of privileged accounts; Assess the risk(s) of each privileged access channel; Enforce the principle of least privilege; Use two-factor or Multi-Factor Authentication for access to Privileged Accounts; Minimise access to only essential activities; Minimise the number of privileged access channels; Ensure each channel and user can be uniquely identified (prevent or minimise sharing of credentials, particularly with accounts such as “root” or “admin”); Ensure operational systems have access to compiled code only; Ensure source code is created, managed and stored on non-operational systems only; Restrict access to source code (deny-by-default); Log all access to source code including the detection, evaluation, recording and termination of privileged access channels; Ensure all logs are periodically reviewed; Ensure strong and strict change control procedures are implemented; Ensure the authorisation, activation and deactivation of privileged access channels is strictly enforced; and Regularly audit and review PAM controls. 16.4.25. It is also important to define all privileged accounts used by an agency or by other organisations, particularly where outsource arrangements are in place. It is fundamental for robust security to identify and record the business functions, related data, systems and access privileges. This is particularly important for agencies that create, store and process classified data. 16.4.26. Without a comprehensive privileged accounts inventory, agencies and other organisations may overlook “backdoor” accounts which allow users to bypass proper controls and auditing. These may have been created during system development, by malicious insiders or by external attackers. Such unregistered accounts may be undetected for months or even years and can create a means of unauthorised and unmonitored access. Such accounts may also be used to erase activity logs to avoid detection. 16.4.27. A privileged access inventory should include a description of the IT system, information asset, privilege description, users and risk classification. This is essential information for assessing risk, the determining of controls and for identifying and managing use and misuse. Of note are: Local or Domain Server Admin accounts; Domain Admin accounts that typically control Active Directory users; System Admin accounts that manage databases; Root accounts that manage Unix/Linux platforms; Accounts that run and manage Windows applications, services, and scheduled tasks; IIS application pools (.NET applications); Networking equipment accounts that give access to firewalls, routers, switches, session border controllers, gateways and other similar devices, whether physical or virtual. 16.4.28. Privileged Access Management systems provide many of the capabilities and controls briefly described above and can facilitate PAM, as well as supporting strong IT Governance. References 16.4.29. Additional information relating to Privileged Account and access management, including some policy examples, can be found at: Reference ISO 27001 Title ISO 27001 – Annex A.9: Access Control 218 Publisher ISO/IEC/ Standards NZ Source https://www.iso.org/isoiec-27001information-security.html Version_3.5__January-2022

Select target paragraph3

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