# Control exception record chain: GRC to IdP | SourceX

Canonical: https://refer.sourcex.si/guides/control-exception-to-remediation-record-linkage
Last updated: 2026-11-04

A company connects control-exception-to-remediation records through five links: the approval logged in a GRC platform, the access request ticket that quotes the exception ID, the group or role grant in the identity provider, the withdrawal of that grant, and the retest that confirms the control works again. Each link must carry a key the next one recognizes. The weakest link is expiry: when the end date is held only by the approval platform, nothing in the directory withdraws the access on time.

This record chain is part of the [control-exception-to-remediation records guide](/guides/chain-control-exception-to-remediation). It maps the identifiers. For what one system's export loses on its own, see the [before-and-after case](/guides/control-exception-to-remediation-missing-context); to score how complete a company's records are, use the [completeness scorecard](/resources/control-exception-to-remediation-completeness-checklist).

## The chain, link by link

Read the table left to right as one exception travels through the company. The last column is the identifier the next record must carry for the chain to hold.

| Link | Record created | System | Key it carries | Key handed to the next link |
|---|---|---|---|---|
| 1. Exception approved | Approval record with approver and end date | GRC platform | Exception ID | Exception ID, typed or passed into the access request |
| 2. Access requested | Access request ticket, fulfilled | Ticketing | Ticket number and, ideally, exception ID | Group or role name and the requested user |
| 3. Access granted | Group or role assigned to the user | Identity provider | Group name, user, timestamp, and an end date if one was set | End date, held either on the grant or only on the approval |
| 4. Access withdrawn | Assignment ended, by expiry or by a person | Directory and ticketing | Withdrawal timestamp; ticket number if one was opened | That ticket number |
| 5. Control retested | Test result with evidence attached | Approval platform or ticketing | Test ID or exception ID | Closes the chain |

Two systems can each be right and still disagree. The approval platform marks the exception lapsed at link 1's end date. The directory shows the assignment from link 3 as active until link 4 happens. The distance between those two dates is the thing the chain exists to measure.

## Where the chain snaps, and why

Each handoff has a design version and a human version. The design version survives turnover; the human version survives only as long as people keep the habit.

| Handoff | Holds by design when | Depends on people when | What a snap looks like |
|---|---|---|---|
| 1 to 2 | A workflow integration opens the access ticket from the exception | Someone types the exception ID into the ticket | Grant exists with no approval that can be found |
| 2 to 3 | Provisioning automation applies the ticket to the identity provider | An administrator adds the group by hand | Group added on a different date, or to a different group |
| 3 to 4 | The grant carries its own end date and lapses | Someone remembers to open a withdrawal ticket | Approval lapsed, access still active |
| 4 to 5 | Testing is a required step in the withdrawal workflow | A tester attaches evidence if asked | Control marked effective with nothing attached |

Handoff 3 to 4 is where the record of an approval and the reality of access drift apart. NIST SP 800-53 control enhancement AC-2(2) asks for temporary and emergency accounts to be removed or disabled automatically after a defined period, rather than when an administrator gets to it. That expectation is met when the identity system itself acts on the date. When only the approval platform knows the date, the expectation is met by memory.

Logs add a second kind of snap: the record of link 3 or link 4 can simply age out. Okta does not return System Log data older than 90 days through its query interface. A company that never exported identity events may have years of approvals and only a few months of the access events that show what happened to them.

## Repairing the weak link

The repair is to put the end date on the grant, not just on the approval. Microsoft Entra entitlement management shows what that looks like: an access package assignment can be set to expire on a date or after a number of days or hours, and when it expires the group and app access from that package is removed unless another assignment still grants it. Microsoft also notes that changes can take up to 24 hours to reach Entra ID, and that editing a policy does not change expiration dates already set on approved requests.

For an introducer, this matters as history, not as advice. A company that moved some apps to expiring grants in, say, 2022 has two eras of records: before, where link 3 to 4 depended on removal tickets; after, where the identity provider closed the link itself. Both eras are worth describing. Ask when the change happened and for which systems.

Illustrative. A fictional 300-person payments processor described its chain like this:

| Link | Key present | Since | Strength |
|---|---|---|---|
| 1 to 2: exception ID in ticket | Yes, required field | 2021 | Strong |
| 2 to 3: provisioning from ticket | For cloud apps only | 2020 | Strong for cloud, weak on premises |
| 3 to 4: end date on grant | Expiring access packages for finance apps | 2022 | Strong for finance apps, weak elsewhere |
| 4 to 5: retest attached | Inconsistent | Unknown | Weak |
| Identity events exported | To storage | 2023 | Earlier events likely gone |

That table is a complete description for an introduction. It names the keys, the years and the gaps without one exception rationale, user name or log line.

## Who owns each key, and who can authorize

The exception ID belongs to the risk, compliance or internal audit team. The ticket number and the removal ticket belong to IT operations. Group names, end dates on grants and the identity logs belong to IT security. A partner can collect the description above from those three people, but a licensing discussion usually needs the CFO, CIO, chief risk officer or general counsel, because the records touch employee access, security configuration and audit work. The [internal control narrative example](/data-types/internal-control-narrative-example) shows how a control is described in writing, and [management letter comments and remediation](/data-types/management-letter-comments-remediation) covers the auditor-facing side of the same fixes. Joiner, mover and leaver chains follow similar keys; see [role change to access](/guides/chain-role-change-to-access).

Confirm the company baseline before introducing: 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license, and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English. Sign the Channel Partner Agreement first.

What stays unknown until SourceX reviews it under the company's own agreement: whether audit and customer commitments allow any use, how much security detail must be removed, and whether a buyer wants the result. SourceX does not claim a connector for any GRC tool, identity provider or ticketing system. The [data quality due diligence resource](/resources/data-quality-due-diligence) lists further questions a reviewer may ask.

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If a client can name the key at each of the five links, and an officer is willing to discuss its exception and access history, [register as a partner](/register), check [who qualifies](/who-qualifies), and read the [terms](/terms) before you submit.

## Sources

- https://learn.microsoft.com/en-us/entra/id-governance/entitlement-management-access-package-lifecycle-policy
- https://csrc.nist.gov/CSRC/media/Projects/risk-management/800-53%20Downloads/800-53r5/SP_800-53_v5_1-derived-OSCAL.pdf
- https://developer.okta.com/docs/reference/system-log-query/
- https://refer.sourcex.si/terms
