Mapping Identity Controls to Compliance Evidence

Key Takeaways

  • Start from the applicable policy or obligation and its system, population, period, and owner.

  • Separate control design, operation, and review evidence.

  • Match approval, fulfillment, and source-side records to the same source account and access item.

  • Record tested exceptions, their owner, and evidence of remediation instead of relying on a completion status alone.

Last updated: November 2026

Start with the requirement and scope

Compliance in an identity program means showing how applicable requirements are implemented and met. Relevant requirements can come from an organization’s policies, contracts, standards, or regulation. Determine which obligation applies to the system and population before deciding how to test it. An access review schedule written in a hypothetical organization’s policy is part of that example. Do not generalize the schedule to every business or law. NIST Special Publication (SP) 800-53 provides control examples and SP 800-53A provides adaptable assessment methods. A business can use those methods to structure testing of its adopted controls.

Suppose company policy requires independent review of payroll administrators every quarter and verification that rejected privileges were removed. State the review period, included payroll systems and qualifying entitlements. Obtain the population from the scope definition and relevant source inventory. Decide who can review and how to handle an approved temporary exception. Agree on how the team will prove that a revocation was fulfilled, including cases that need manual work.

AssertionEvidence to collect
Design specifies who and what to reviewApproved policy, owner, entitlement identifiers, systems and schedule
Review included the expected populationRelevant aggregation/results, campaign filter and composition, reconciliation to the source roster
Independent reviewer acted for each sampled testReviewer, decision, comments where required and sign-off records
A rejected item was removedConfirmed task or provisioning operation and a target readback for the same account and entitlement
An accepted exception is actively governedApproved reason, owner, scope, expiration, and follow-up or verified removal

Use more than one assessment method when needed

NIST SP 800-53A describes three assessment methods: examine, interview, and test. Examine the policy, design and selected evidence. Interview the control owner to understand responsibility and exceptions. Test a case to observe the mechanism and compare its result with the criterion. For an identity control, a policy describes the required process. A configuration shows its implementation. A signed record and observed target membership show how it operated for a particular sample. These are different claims. Review the population and relevant dates before selecting examples.

Trace the payroll example through one removal. A reviewer signed off on a rejected grant for native account P-220 on the payroll source. The relevant task was reported complete. The native payroll group still contains P-220. Check whether the task referred to the same account and group and whether another authorized assignment still provides the membership. If the tested control requires actual removal and the access remains without an approved exception, record the failed observation and have its owner resolve it. Repeat the verification once remediation is complete. A signed decision, a task status, and native membership can all be recorded accurately while supporting different conclusions.

Preserve evidence a reviewer can reproduce

Use stable source and identity identifiers, record both observation and event times, and retain the criteria used to generate any report. Reconcile where different exports use different names for the same source account. Document why each sample is in scope and distinguish population counts from observed exceptions. When a report omits some identities due to an applied filter or missing correlation, resolve the scope issue or explicitly bound the conclusion. Protect exported access data according to its sensitivity and the applicable retention policy. If the review sampled 12 people from an expected roster of 40, report both counts and the sampling method. An assertion of 12 reviewed cases describes the evidence obtained. A conclusion about the population requires a defensible selection method and an explanation of the limits of the evidence.

SailPoint supplies campaign composition, decision, and remediation reporting where relevant. Access History can compare observed access across dates for supported tenants, and Audit Reports expose separate event records. These records can support a control assessment. The applicable policy and verified population determine what they prove. For example, a completed manager campaign may omit identities without a manager. The completion status can be correct for the actual campaign while leaving a coverage gap against a policy that included those people.

See NIST’s control catalog and control assessment methodology, and SailPoint’s audit reporting, campaign reports, and Access History.

Test Your Knowledge

An audit tests that one revoked payroll privilege was actually removed. The certification is signed off and the task says complete. Which additional evidence directly meets the removal criterion?

A

A current password reset event for the employee

B

The campaign title and an unrelated group list

C

A screenshot of the access request approval only

D

Native target evidence showing the specified account no longer holds the specified privilege

Test Your Knowledge

A finished manager review excludes several in-scope users without managers. What does the completion status establish?

A

The recorded campaign completed for its actual scope. The omitted users still need coverage evidence or a documented exception

B

All people on the policy roster were reviewed because the campaign is finished

C

All permissions in the native systems were automatically confirmed

D

The campaign’s report makes the original policy roster irrelevant

Sections you finish are checked off in the contents.