This before-and-after case belongs to the control-exception-to-remediation records guide. The identifiers that make the "after" version possible are mapped in the record chain.
Before: the case as the GRC export tells it
Illustrative. A fictional 260-person logistics software company moves its billing database to a new cloud region. A database administrator needs production write access that segregation-of-duties rules normally forbid. Risk approves a 14-day exception.
Here is everything the GRC export holds about it:
| Field | Value in the GRC export |
|---|---|
| Exception | EX-118, segregation of duties, billing database |
| Requested by | Head of platform engineering |
| Approved by | Chief financial officer |
| Rationale | Region migration; no second administrator available |
| Compensating control | Daily review of write queries by the data team lead |
| Start | Day 1 |
| End | Day 14 |
| Status | Expired |
| Fix status | Closed |
Read on its own, this is a model exception. It was approved by the right person, it carried a compensating control, it had a short end date, and it closed. A reviewer looking only at this record would conclude the control was out of compliance for 14 days and then restored.
After: the same case with identity and ticket history around it
Now add what the IdP and the service desk recorded about EX-118.
| Day | Identity provider | Ticketing | What it adds |
|---|---|---|---|
| Day 1 | Administrator added to the billing write group, no end date set | Access ticket fulfilled; cites EX-118 | The grant is real and tied to the exception |
| Day 14 | No change | No ticket | The exception expired; the access did not |
| Days 15 to 38 | Membership still active | None | 24 days of access with no approval behind it |
| Day 39 | Membership flagged in the quarterly access review | Revocation ticket opened, cites the review and EX-118 | Detection: how the gap was found |
| Day 41 | Membership revoked | Revocation ticket closed | Access really ends: 27 days after the exception |
| Day 44 | No change | Control re-checked, evidence attached | The fix is verified, not just marked closed |
The administrator held the access for 41 days, not 14. The control was out of compliance for 27 days after the record said it was restored. The compensating control, the daily review of write queries, was scheduled for the exception period; whether it kept running after day 14 is a question none of the three systems answers.
The "after" version is not a different story. It is the same exception with its consequences attached.
What the export lost, and where each piece lives
| Lost context | Where it lives | Who usually holds it | Survival risk |
|---|---|---|---|
| When access was granted | IdP audit log; access ticket | IT security; IT operations | Identity logs age out unless exported |
| Whether expiry was enforced | IdP group membership history | IT security | Same as above; current state alone shows nothing |
| Length of the gap | Calculated by joining the GRC end date to the revocation date | Nobody, until someone joins them | Lost if either date is lost |
| How the gap was found | Access review record; revocation ticket | Internal audit; IT operations | Usually kept with the review |
| Whether access was revoked | IdP log; revocation ticket | IT security; IT operations | Tickets usually survive longer than logs |
| Whether the fix worked | Re-check evidence | Risk or internal audit | Depends on whether evidence is attached |
| Whether the compensating control continued | Data team's review log, if any | Data team lead | Often not recorded past the end date |
The survival column is why timing matters. Microsoft Entra keeps audit logs for 7 days on Entra ID Free and 30 days on P1 and P2 unless they are routed to storage, and Okta does not return System Log data older than 90 days through its query interface. Some companies avoid the gap altogether by setting the end date on the grant: in Microsoft Entra entitlement management, an access package assignment can expire on a date or after a number of days, and its group and app access is then removed. Where that was in place, the identity provider records the enforcement itself.
Why the "after" version is the one worth describing
For AI training and evaluation, the before version is a form. The after version is a decision, its enforcement, the failure of that enforcement, its detection and its correction, each with a timestamp and an owner. Public text almost never shows that sequence, which is the pattern described in what data is missing from AI training and in exception handling data for AI agents. Whether a buyer wants a given company's history is judged only in SourceX's review.
For an introducer, the practical question is simple: "For your exceptions, can you put the GRC end date next to the date access was actually removed?" A yes for recent years and a "partly" for older ones is a useful answer. A company that has only the before version still has something to describe; it should just say so.
Who can open the conversation, and what stays unknown
Exception, access and ticket records sit with three owners: risk or internal audit, IT security and IT operations. A licensing discussion normally needs an officer above all three, such as the CFO, CIO, chief risk officer or general counsel. The auditor-facing side of remediation is covered in management letter comments and remediation; for issues that stall reviews, see deal killers in due diligence.
Confirm the company baseline: 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 before submitting.
Unknown until SourceX reviews it under the company's own agreement: whether audit and customer commitments permit any use, what security detail must be removed, how many exceptions have an after version, and whether any buyer wants them. You never see an exception rationale, a user name or a log line.
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 tell you, at the metadata level, for which years it can set exception end dates beside real removal dates, and an officer will take the call, register as a partner, check who qualifies, and read the terms before you submit.