Explore the expanded editions. Read every sample free before choosing a book.

Practical preparation / 2 MIN READ

Find an incompatible permission pair without alleging misuse

A fictional role matrix distinguishes the ability to create and approve the same change from evidence that someone actually did so.

Server racks and network cabling inside a data center
Illustrative photograph by imgix on Unsplash.
On this page

An incompatible permission combination is a capability concern under a defined rule. It is not by itself proof of misuse. This original fictional exercise supplies a separation rule and a small permission matrix for interview practice.

Read the rule and permissions

The teaching rule says the person who creates a payment-detail change must not approve that same change. Ari has create permission, Bea has approve permission and Cam has both. No transaction history is included.

PersonCreateApproveInitial observation
AriYesNoNo conflicting pair shown
BeaNoYesNo conflicting pair shown
CamYesYesPotential incompatible capability

Cam's permissions warrant examination under the rule. The packet does not show whether the application prevents self-approval, whether an authorized exception exists or whether Cam used either permission.

Ask for the missing mechanism

Request the relevant workflow configuration and an authorized demonstration of whether a creator can approve their own change. If the system blocks self-approval, distinguish that preventive mechanism from the broad permission labels. If it does not, document the capability and the applicable response process.

Do not test a real financial system or create a transaction to prove the point. The exercise uses paper records only. Actual assessment actions require authorized procedures and safeguards.

Add a transaction record

A later fictional log shows Cam created change C7 and Bea approved it. That supports separation for C7. It does not remove Cam's broader capability or establish that every change followed the rule. Conversely, the permission pair does not invalidate C7's supplied approval record.

The NIST SP 800-53 catalog, including separation-of-duties context, is a primary reference. This invented workflow is not a universal implementation requirement.

Write a bounded note

Separate the rule, assigned permissions, enforcement behavior and observed transactions. State which are known and unknown. Your artifact should show that you can identify a potential issue without accusing a person or treating one compliant transaction as proof of complete control effectiveness.

For a resource decision after this exercise, compare segregation-of-duties preparation: permission matrix or interview workbook?.

PUT IT INTO PRACTICE

GRC Career Transition Guide

Turn this guidance into a focused role brief, experience inventory and application plan.

Choose another free evidence, application or portfolio task