Control-exception-to-remediation record chain: the five keys from approval to verified control

Short answer

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.

Visual briefFull-size diagram
Five chain links, from GRC exception to access ticket, group grant, removal and retest, click together left to right; the link for expiry is shown weak in orange and then repaired in green once the end date sits on the grant itself.
The record chain in five links. The expiry link is weakest when the end date lives only in the GRC tool.

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

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.

LinkRecord createdSystemKey it carriesKey handed to the next link
1. Exception approvedApproval record with approver and end dateGRC platformException IDException ID, typed or passed into the access request
2. Access requestedAccess request ticket, fulfilledTicketingTicket number and, ideally, exception IDGroup or role name and the requested user
3. Access grantedGroup or role assigned to the userIdentity providerGroup name, user, timestamp, and an end date if one was setEnd date, held either on the grant or only on the approval
4. Access withdrawnAssignment ended, by expiry or by a personDirectory and ticketingWithdrawal timestamp; ticket number if one was openedThat ticket number
5. Control retestedTest result with evidence attachedApproval platform or ticketingTest ID or exception IDCloses 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.

HandoffHolds by design whenDepends on people whenWhat a snap looks like
1 to 2A workflow integration opens the access ticket from the exceptionSomeone types the exception ID into the ticketGrant exists with no approval that can be found
2 to 3Provisioning automation applies the ticket to the identity providerAn administrator adds the group by handGroup added on a different date, or to a different group
3 to 4The grant carries its own end date and lapsesSomeone remembers to open a withdrawal ticketApproval lapsed, access still active
4 to 5Testing is a required step in the withdrawal workflowA tester attaches evidence if askedControl 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.

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:

LinkKey presentSinceStrength
1 to 2: exception ID in ticketYes, required field2021Strong
2 to 3: provisioning from ticketFor cloud apps only2020Strong for cloud, weak on premises
3 to 4: end date on grantExpiring access packages for finance apps2022Strong for finance apps, weak elsewhere
4 to 5: retest attachedInconsistentUnknownWeak
Identity events exportedTo storage2023Earlier 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 shows how a control is described in writing, and management letter comments and remediation covers the auditor-facing side of the same fixes. Joiner, mover and leaver chains follow similar keys; see 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 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, check who qualifies, and read the terms before you submit.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Which key matters most if a company only has one?

The exception ID written into the access ticket. With it, the approval can be tied to the grant and usually to the removal. Without it, every join depends on matching group names and dates by hand.

Does the company need a GRC platform for this chain to exist?

No. Some companies track exceptions in a spreadsheet or a ticket queue. The chain still exists if the exception has a stable ID and later records cite it.

Should I ask to see a sample ticket to confirm the key is there?

No. Ask the IT operations manager roughly what share of access tickets carry the exception ID and since when. The answer is enough for an introduction.

Sources

  1. learn.microsoft.com/en-us/entra/id-governance/entitlement-manage…
  2. csrc.nist.gov/CSRC/media/Projects/risk-management/800-53 D…
  3. developer.okta.com/docs/reference/system-log-query
  4. refer.sourcex.si/terms

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment