Test the review, not just the existence of a spreadsheet
User access reviews help organizations assess whether access remains appropriate for relevant systems. For SOX testing, the question is whether the documented control operated as designed. A signed spreadsheet may show that someone responded, but it may not establish that the population was complete, the reviewer was appropriate or identified access issues were addressed.
walktru brings control information, evidence classification and testing results with reasoning into one platform. The user access review procedures below illustrate how to evaluate this type of control; they do not specify a particular automated procedure or identity-system integration. Keep the review objective, evidence and criteria connected when assessing an automation workflow.
Build a connected review-testing record
Start with the application, review period and documented population requirements. Identify whether privileged, service, shared or inactive accounts fall within the review scope. Retain the source account listing and any extraction parameters needed to establish its reliability. An access review cannot provide assurance about accounts that were unintentionally excluded before the reviewer saw the file.
Then connect review evidence to the relevant account population. Consider the reviewer’s responsibility, the timing of completion and the documentation of decisions. If the review identified access that should be changed, retain evidence of the required follow-up and evaluate whether it occurred under the organization’s policy. Deterministic testing is useful for consistently applying defined attributes, while judgment remains important for evaluating whether particular access is appropriate.
Testing checklist
- Identify the system, period and account types in scope.
- Validate the account population used in the review.
- Inspect reviewer, completion and decision evidence.
- Evaluate required follow-up for identified access issues.
Example: quarterly review of a financial application
Suppose a control requires a quarterly review of users in a financial application. The team retains an account export, documented review responses and evidence resolving requested access changes. A practical test might assess whether the export covers the relevant system and date, whether the designated reviewer completed the review and whether decisions were documented for the intended population.
If a reviewer requested removal of an account, an annotation in the review file may not establish that removal occurred. The test needs the follow-up evidence required by the control. If the deadline or review responsibility is unclear, the control design may need clarification before an automated timing check is meaningful. These examples illustrate testing considerations, not a claimed customer outcome or an integration with an unnamed identity system.
Keep access decisions accountable
Automation should make discrepancies and missing support easier to inspect, not make sensitive access judgments invisible. A reviewer may need context about a person’s responsibilities, compensating controls or an approved exception. Keep that assessment connected to the evidence and conclusion so another professional can understand why an item was resolved or remained open.
walktru’s SOX TRAIL® supports a traceable connection between testing work and the result. Evaluate the workflow with a representative control, an appropriately shareable account listing and your existing testing requirements. Access review testing should also be considered alongside broader ITGC procedures and IPE validation, since both the control environment and the reliability of the account information affect the test.