Essential Eight RB-ML3.2 Privileged user accounts cannot access their own backups

This control is equivalent to ISM-1706.

E8-RB-ML3.2 requires that privileged accounts (other than backup administrator accounts) are unable to access their own backups. ISM-1706 states the same requirement: privileged user accounts (excluding backup administrator accounts) cannot access their own backups. Both controls align in intent (preventing self-access to backup data by privileged users), scope, and exception handling, making implementation of one largely satisfy the other.

This control partially meets ISM-1811.

E8-RB-ML3.2 mandates that privileged accounts (excluding backup administrator accounts) cannot access their own backups. ISM-1811 requires backup data to be retained securely and resiliently, including access restrictions and secure storage practices that reinforce the separation E8-RB-ML3.2 implies. Although ISM-1811 does not explicitly mandate this separation, it strengthens the backup security posture required to implement E8-RB-ML3.2 effectively.

This control partially meets ISM-1928.

E8-RB-ML3.2 requires privileged accounts (excluding backup administrator accounts) cannot access their own backups to reduce the risk of misuse and unauthorised disclosure. ISM-1928 restricts access to specific high-value backups so they are solely accessible to backup administrator accounts, inherently preventing most privileged accounts from accessing those backups. ISM-1928 is broader in technical safeguards but narrower in system scope, while E8-RB-ML3.2 generally applies across privileged users and their own backups.

This control partially overlaps ISM-1508.

ISM-1508 requires privileged access to be limited to only what is required for users to perform their duties. E8-RB-ML3.2 applies that least-privilege idea to a specific high-risk resource by preventing privileged users from accessing backups that could enable concealment or tampering. E8-RB-ML3.2 is narrower and backup-specific, while ISM-1508 is a general least-privilege requirement across systems and resources.

This control partially overlaps ISM-1708.

ISM-1708 requires that backup administrator accounts are prevented from modifying or deleting backups during their retention period. E8-RB-ML3.2 prevents privileged accounts (excluding backup administrators) from accessing their own backups, which reduces opportunities for privileged users to locate and influence backup content or processes. This is complementary to ISM-1708, but it does not address backup administrators' ability to modify/delete backups during retention.

This control partially overlaps ISM-1813.

ISM-1813 requires that unprivileged user accounts cannot access their own backup data. E8-RB-ML3.2 applies a similar principle to privileged accounts (excluding backup admins) by preventing them from accessing their own backups, addressing separation of duties and reducing insider risk. The overlap is the 'no self-access to backups' concept, but they differ by account class (unprivileged vs privileged).

This control depends on ISM-2152.

ISM-2152 requires segregated backup infrastructure and separate administrative authentication from production. This supports E8-RB-ML3.2 by helping prevent privileged accounts from using their normal production admin identities/paths to reach backup systems and access their own backups. E8-RB-ML3.2 is an explicit authorisation rule about who can access backups, while ISM-2152 is a segregation mechanism that helps enforce separation of duties and limits lateral movement.

This control partially overlaps IT.PRO-10.2.

IT.PRO-10.2 requires backup repositories to be isolated from user and production environments to prevent unauthorised access, modification or deletion; E8-RB-ML3.2 ensures privileged user accounts, except backup administrator accounts, cannot access their own backups, extending that separation to privileged users.