ISO 27002:2022, Control 8.2 – Privileged Access Rights

ISO 27002:2022 Revised Controls

Book a demo

casual,man,,freelance,working,on,laptop,computer,and,clicking,wireless

Purpose of Control 8.2

Malicious or incorrect use of elevated system administrator privileges is one of the major causes of ICT disruption across commercial networks all over the world.

Privileged access rights allows organisations to control access to their infrastructure, applications, assets and maintain the integrity of all stored data and systems.

Control 8.2 is a preventative control that maintains risk by establishing an authorisation process that handles all requests for access across an organisation’s ICT network and associated assets.

Attributes Table

Control Type Information Security PropertiesCybersecurity Concepts Operational Capabilities Security Domains
#Preventive #Confidentiality
#Integrity
#Availability
#Protect#Identity and Access Management#Protection

Ownership of Control 8.2

Control 8.6 deals with an organisation’s ability to control access to data via user accounts that enjoy enhanced access rights.

As such, ownership should reside with the Head of IT (or organisational equivalent), who holds responsibility for the organisation’s ability to administer and monitor privileged domain or application user accounts.

Get a Headstart on ISO 27001
  • All updated with the 2022 control set
  • Make 81% progress from the minute you log in
  • Simple and easy to use
Book your demo
img

General Guidance on Control 8.2

Control 8.2 outlines 12 main guidance points that organisations need to follow, in accordance with a “topic specific” policy on access control (see Control 5.15) that targets individual business functions.

Organisations should:

  1. Identify a list of users who require any degree of privileged access – either for an individual system – such as a database – application, or underlying OS.
  2. Maintain a policy that allocates privileged access rights to users on what is known as an “event by event basis” – users should be granted levels of access based on the bare minimum that is required for them to carry out their role.
  3. Outlining a clear authorisation process that deals with all requests for privileged access, including keeping a record of all access rights that have been implemented.
  4. Ensure that access rights are subject to relevant expiry dates.
  5. Take steps to ensure that users are explicitly aware of any period of time where they are operating with privileged access to a system.
  6. Where relevant, users are asked to re-authenticate prior to using privileged access rights, in order to affect greater information/data security.
  7. Carry out periodic audits of privileged access rights, especially following a period of organisational change. Users’ access rights should be reviewed based upon their “duties, roles, responsibilities and competence” (see Control 5.18).
  8. Consider operating with what’s known as a “break glass” procedure – i.e. ensuring that privileged access rights are granted within tightly-controlled time windows that meet the minimum requirements for an operation to be carried out (critical changes, system administration etc).
  9. Ensure that all privileged access activities are logged accordingly.
  10. Prevent the use of generic system login information (especially standardised usernames and passwords) (see Control 5.17).
  11. Keep to a policy of assigning users with a separate identity, that allows for tighter control of privileged access rights. Such identities can then be grouped together, with the associated group being provided differing levels of access rights.
  12. Ensure that privileged access rights are reserved for critical tasks only, that relate to the continued operation of a functioning ICT network – such as system administration and network maintenance.

Supporting Controls

  • 5.15

Are you ready for
the new ISO 27002

We’ll give you an 81% headstart
from the moment you log in
Book your demo

Updated for ISO 27001 2022
  • 81% of the work done for you
  • Assured Results Method for certification success
  • Save time, money and hassle
Book your demo
img

Changes and Differences from ISO 27002:2013

Control 27002:2022-8.2 replaces 27002:2013-9.2.3 (Management of privileged access rights).

27002:2022-8.2 contains 5 major guidance points that aren’t explicit in its 2013 counterpart:

  1. 27002:2022-8.2 doesn’t explicitly require a different user ID for privileged access rights.
  2. 27002:2022-8.2 stresses the need to re-authenticate prior to receiving privileged access rights.
  3. 27002:2022-8.2 advocates for a break glass approach when performing critical maintenance duties, based on tightly controlled time windows.
  4. 27002:2022-8.2 asks organisations to keep thorough privileged access logs, for auditing purposes.
  5. 27002:2022-8.2 asks organisations to limit the use of privileged access rights to administrative tasks.

How ISMS.online Helps

ISO 27002, Control 6.6, covers the need for organisations to prevent the leakage of confidential information by establishing confidentiality agreements with interested parties and personnel.

Our cloud-based platform provides a complete set of tools to assist organisations in setting up an information security management system (ISMS) according to ISO 27002.

These tools include:

  • A library of templates for common corporate documents.
  • A set of predefined policies and procedures.
  • An audit tool to support internal audits.
  • A configuration interface for customising ISMS policies and procedures.
  • An approval workflow for all changes made to policies and procedures.
  • A checklist for making sure that your policies and information security processes follow the approved international standards.

ISMS.Online also allows users to:

  • Manage all aspects of the ISMS life cycle with ease.
  • Get real-time insights into their security posture and compliance gaps.
  • Integrate with other systems like HR, finance and project management.
  • Demonstrate compliance of their ISMS with ISO 27001 standards.

The ISMS.Online tool also provides guidance on how best to implement your ISMS by providing tips on how to create policies and procedures related to aspects such as risk management, personnel security awareness training and incident response planning.

Get a Headstart
on ISO 27002

The only compliance
solution you need
Book your demo

New Controls

ISO/IEC 27002:2022 Control IdentifierISO/IEC 27002:2013 Control IdentifierControl Name
5.7NewThreat intelligence
5.23NewInformation security for use of cloud services
5.30NewICT readiness for business continuity
7.4NewPhysical security monitoring
8.9NewConfiguration management
8.10NewInformation deletion
8.11NewData masking
8.12NewData leakage prevention
8.16NewMonitoring activities
8.23NewWeb filtering
8.28NewSecure coding

Organisational Controls

ISO/IEC 27002:2022 Control IdentifierISO/IEC 27002:2013 Control IdentifierControl Name
5.105.1.1, 05.1.2Policies for information security
5.206.1.1Information security roles and responsibilities
5.306.1.2Segregation of duties
5.407.2.1Management responsibilities
5.506.1.3Contact with authorities
5.606.1.4Contact with special interest groups
5.7NewThreat intelligence
5.806.1.5, 14.1.1Information security in project management
5.908.1.1, 08.1.2Inventory of information and other associated assets
5.1008.1.3, 08.2.3Acceptable use of information and other associated assets
5.1108.1.4Return of assets
5.12 08.2.1Classification of information
5.1308.2.2Labelling of information
5.1413.2.1, 13.2.2, 13.2.3Information transfer
5.1509.1.1, 09.1.2Access control
5.1609.2.1Identity management
5.17 09.2.4, 09.3.1, 09.4.3Authentication information
5.1809.2.2, 09.2.5, 09.2.6Access rights
5.1915.1.1Information security in supplier relationships
5.2015.1.2Addressing information security within supplier agreements
5.2115.1.3Managing information security in the ICT supply chain
5.2215.2.1, 15.2.2Monitoring, review and change management of supplier services
5.23NewInformation security for use of cloud services
5.2416.1.1Information security incident management planning and preparation
5.2516.1.4Assessment and decision on information security events
5.2616.1.5Response to information security incidents
5.2716.1.6Learning from information security incidents
5.2816.1.7Collection of evidence
5.2917.1.1, 17.1.2, 17.1.3Information security during disruption
5.30NewICT readiness for business continuity
5.3118.1.1, 18.1.5Legal, statutory, regulatory and contractual requirements
5.3218.1.2Intellectual property rights
5.3318.1.3Protection of records
5.3418.1.4Privacy and protection of PII
5.3518.2.1Independent review of information security
5.3618.2.2, 18.2.3Compliance with policies, rules and standards for information security
5.3712.1.1Documented operating procedures

People Controls

ISO/IEC 27002:2022 Control IdentifierISO/IEC 27002:2013 Control IdentifierControl Name
6.107.1.1Screening
6.207.1.2Terms and conditions of employment
6.307.2.2Information security awareness, education and training
6.407.2.3Disciplinary process
6.507.3.1Responsibilities after termination or change of employment
6.613.2.4Confidentiality or non-disclosure agreements
6.706.2.2Remote working
6.816.1.2, 16.1.3Information security event reporting

Physical Controls

ISO/IEC 27002:2022 Control IdentifierISO/IEC 27002:2013 Control IdentifierControl Name
7.111.1.1Physical security perimeters
7.211.1.2, 11.1.6Physical entry
7.311.1.3Securing offices, rooms and facilities
7.4NewPhysical security monitoring
7.511.1.4Protecting against physical and environmental threats
7.611.1.5Working in secure areas
7.711.2.9Clear desk and clear screen
7.811.2.1Equipment siting and protection
7.911.2.6Security of assets off-premises
7.1008.3.1, 08.3.2, 08.3.3, 11.2.5Storage media
7.1111.2.2Supporting utilities
7.1211.2.3Cabling security
7.1311.2.4Equipment maintenance
7.1411.2.7Secure disposal or re-use of equipment

Technological Controls

ISO/IEC 27002:2022 Control IdentifierISO/IEC 27002:2013 Control IdentifierControl Name
8.106.2.1, 11.2.8User endpoint devices
8.209.2.3Privileged access rights
8.309.4.1Information access restriction
8.409.4.5Access to source code
8.509.4.2Secure authentication
8.612.1.3Capacity management
8.712.2.1Protection against malware
8.812.6.1, 18.2.3Management of technical vulnerabilities
8.9NewConfiguration management
8.10NewInformation deletion
8.11NewData masking
8.12NewData leakage prevention
8.1312.3.1Information backup
8.1417.2.1Redundancy of information processing facilities
8.1512.4.1, 12.4.2, 12.4.3Logging
8.16NewMonitoring activities
8.1712.4.4Clock synchronization
8.1809.4.4Use of privileged utility programs
8.1912.5.1, 12.6.2Installation of software on operational systems
8.2013.1.1Networks security
8.2113.1.2Security of network services
8.2213.1.3Segregation of networks
8.23NewWeb filtering
8.2410.1.1, 10.1.2Use of cryptography
8.2514.2.1Secure development life cycle
8.2614.1.2, 14.1.3Application security requirements
8.2714.2.5Secure system architecture and engineering principles
8.28NewSecure coding
8.2914.2.8, 14.2.9Security testing in development and acceptance
8.3014.2.7Outsourced development
8.3112.1.4, 14.2.6Separation of development, test and production environments
8.3212.1.2, 14.2.2, 14.2.3, 14.2.4Change management
8.3314.3.1Test information
8.3412.7.1Protection of information systems during audit testing

We’re cost-effective and quick

Discover how that will boost your ROI
Get your quote

Explore ISMS.online's platform with a self-guided tour - Start Now