Access management · ISO 27001
The role has changed.
Have the access rights changed too?
A practical example to help you decide what to retain, adjust or remove, and verify that the decision has been implemented.
Estimated reading time: 6 minutes
In brief
When someone changes roles, access management should involve reassessing existing permissions, not just granting new ones. The review identifies what to retain, adjust or remove, who authorises the decision and how its implementation is verified. The UK’s NCSC includes role changes in its good practice guidance on identity and access management.
In this article
Without this review, previous access rights may remain active after new permissions have been granted. When this happens repeatedly, the person accumulates privileges that no longer match their responsibilities: this is known as privilege accumulation (privilege creep).
Marta’s example
Consider this illustrative example: Marta moves from updating suppliers’ bank details to approving payments. She is assigned the new access profile but retains the previous one “to help during the transition”.
The organisation has determined that these tasks must be performed by different people: the person who changes a supplier’s IBAN must not be the person who approves the transfer. With both access profiles active, Marta can do both.
Access management: what should a role-change review include?
The review compares the requirements of the new role with the person’s effective permissions, also checking whether these match the authorised access profile.
Two principles guide the decision: least privilege, which limits access to what is necessary for authorised work, and segregation of duties, which separates responsibilities where combining them could create risk. As a supporting technical reference, NIST SP 800-171 Rev. 3
(requirement 03.09.02) provides for reviewing the need for access when someone changes position.
In Marta’s case, the combination of permissions conflicts with the defined segregation of duties. The transition tasks need to be clarified and a solution found that does not retain this conflict.
On smaller screens, scroll horizontally to view the table.
| Situation | Decision requiring justification |
|---|---|
| Access needed for the new role | Retain or grant access in line with the defined criteria and authorisations. |
| Access linked solely to the previous role | Remove or adjust access in line with the effective date of the new role. |
| Access needed for a transition task | Define the purpose, duration and conditions of use. |
| Access that creates a segregation-of-duties conflict | Avoid the combination. Where an exception is permissible, document the justification, approval, compensating measures and review. |
The review should cover, where applicable, the person’s access to external services and SaaS, as well as local accounts, shared mailboxes and delegated permissions. It should also consider technical credentials, such as API tokens, where these are linked to the person or their responsibilities.
Who communicates, validates and implements the change?
Communicating the role change, authorising permissions and implementing access changes are separate responsibilities.
The following table provides an example of how these responsibilities can be allocated, to be adapted to the organisation and the criticality of the access involved.
On smaller screens, scroll horizontally to view the table.
| Stakeholder | Role in the change process (example) |
|---|---|
| Human Resources | Communicate the role change and its effective date. Trigger the review, but do not define technical permissions. |
| Line management and information asset owners | Validate the requirements: tasks associated with the new role, transition work and combinations of permissions to avoid. |
| Technical team | Implement the authorised changes and record what has been done. |
| Information security | Support the definition of criteria, assess exceptions and help verify the outcome. |
The organisation should define who verifies the outcome and in which situations this verification requires someone other than the person who implemented the change.
Access management during the transition: can previous permissions remain?
A temporary need should have a specific purpose and an end date.
The ICO recommends assigning end dates to permissions, particularly for temporary role changes or where access is not required permanently.
Does Marta need to view records, correct information or continue changing bank details? If the handover only requires viewing records, read-only access to the necessary records may meet that need, subject to assessment and authorisation.
Temporary authorisation does not, by itself, resolve a segregation-of-duties conflict. In this scenario, a suitable solution would be to assign the transition task to someone else in the previous team.
The decision should record the reason, the permissions covered, who authorises the access and who monitors its expiry. “Temporary” should not mean “until someone remembers”.
When is an access review complete?
The review is complete once the appropriateness of the access has been assessed and recorded and, where changes are required, their implementation has been verified.
A request submitted to the service desk does not, on its own, demonstrate that the change has been implemented. The ICO recommends retaining records of reviews and adjustments.
Verification goes beyond checking the procedural record: it also confirms the outcome. If a permission has been removed from the profile but remains available through a group, the change has been implemented without achieving the intended effect. The question to answer is: can Marta carry out her authorised tasks, and have the access rights that should have been removed actually been withdrawn?
Periodic reviews of access rights complement this process by detecting anything that was not addressed at the time of the change.
What if the platform is unavailable?
Suppose that, on the date of the role change, the administration console of a cloud service is unavailable and the team cannot implement or confirm the removal of the previous permissions.
The console being unavailable does not mean that access has been revoked. The change should be marked as pending, with someone responsible for following it up, and the organisation should assess the risk and the need for authorised temporary measures. Once possible, the actual state of the permissions should be checked, any outstanding changes implemented and the outcome verified.
“Request submitted”, “change implemented” and “outcome verified” are different statuses. Distinguishing between them prevents an administrative task from being closed while the security requirement remains unresolved.
How does access management relate to ISO 27001 and other obligations?
ISO/IEC 27001 establishes the requirements for an Information Security Management System (ISMS). Four controls in Annex A, for which guidance is provided in ISO/IEC 27002:2022, relate directly to this example:
On smaller screens, scroll horizontally to view the table.
| Control (ISO/IEC 27001:2022, Annex A) | Relevance to the example |
|---|---|
| 5.3 Segregation of duties | Identify and separate conflicting duties, such as changing supplier details and approving payments. |
| 5.15 Access control | Define access rules based on business and information security requirements. |
| 5.16 Identity management | Manage the identity lifecycle, including changes. |
| 5.18 Access rights | Grant, review, modify and remove access rights. |
Controls 5.23 (information security for use of cloud services), 6.5 (responsibilities after termination or change of employment) and 8.2 (privileged access rights) may also be relevant. The selection and implementation of necessary controls depend on the organisation’s context, risks and applicable requirements.
This topic may also fall within legal obligations applicable to the organisation. The
Portuguese cybersecurity legal framework covers human resources security and access control policies, subject to its scope of application and the provisions governing when its requirements take effect. Where personal data are processed,
Article 32 of the GDPR also requires a level of security appropriate to the risk.
To place this work in the context of the management system, see also
“How can you prepare your organisation for ISO 27001?”.
A role change should not simply mean adding permissions. It should prompt a review of which permissions are still needed and verification that the decision has been implemented.
Related training
ISO 27001 Lead Implementer
Behaviour’s course explores how context, risks, processes, controls and evidence fit together when implementing an ISMS.
Next confirmed course dates: 23–26 November 2026, Live Online.