Control exception before and after: what a standalone GRC export loses without identity and ticket context

Short answer

A standalone GRC export keeps the exception itself: approver, rationale, compensating control, start and end dates, and a status that flips to expired. It loses whether access actually changed. The grant date, the date access was revoked, the days in between, the review that caught the gap and the re-check that closed it all live in the identity provider (IdP) and the ticketing system. Read alone, an export can present a 41-day access window as a tidy 14-day exception.

Visual briefFull-size diagram
A GRC exception record shows a 14-day exception marked expired, with four blank fields that fill in as pieces slide in from the identity provider and ticketing: access granted day 1, removed day 41, found by an access review, retested day 44.
Illustrative case for a fictional logistics software company. The export said 14 days; the access lasted 41.

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:

FieldValue in the GRC export
ExceptionEX-118, segregation of duties, billing database
Requested byHead of platform engineering
Approved byChief financial officer
RationaleRegion migration; no second administrator available
Compensating controlDaily review of write queries by the data team lead
StartDay 1
EndDay 14
StatusExpired
Fix statusClosed

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.

DayIdentity providerTicketingWhat it adds
Day 1Administrator added to the billing write group, no end date setAccess ticket fulfilled; cites EX-118The grant is real and tied to the exception
Day 14No changeNo ticketThe exception expired; the access did not
Days 15 to 38Membership still activeNone24 days of access with no approval behind it
Day 39Membership flagged in the quarterly access reviewRevocation ticket opened, cites the review and EX-118Detection: how the gap was found
Day 41Membership revokedRevocation ticket closedAccess really ends: 27 days after the exception
Day 44No changeControl re-checked, evidence attachedThe 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 contextWhere it livesWho usually holds itSurvival risk
When access was grantedIdP audit log; access ticketIT security; IT operationsIdentity logs age out unless exported
Whether expiry was enforcedIdP group membership historyIT securitySame as above; current state alone shows nothing
Length of the gapCalculated by joining the GRC end date to the revocation dateNobody, until someone joins themLost if either date is lost
How the gap was foundAccess review record; revocation ticketInternal audit; IT operationsUsually kept with the review
Whether access was revokedIdP log; revocation ticketIT security; IT operationsTickets usually survive longer than logs
Whether the fix workedRe-check evidenceRisk or internal auditDepends on whether evidence is attached
Whether the compensating control continuedData team's review log, if anyData team leadOften 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.

  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

Is the GRC export wrong in the before version?

No. Every field in it is accurate. It records the approval and the end date faithfully; it simply has no view of whether the access changed. That is why the case needs the other systems.

What if the company never exported its identity logs?

Then the after version may only be possible for recent months, or rebuilt partly from removal tickets and access reviews. Say so plainly in the description. A known gap is more useful to a reviewer than a guess.

Does the after version mean SourceX will receive user names and access logs?

Not necessarily. What, if anything, is shared is decided under the company's own agreement, and security records often need heavy redaction or exclusion. The partner only describes what exists.

Sources

  1. learn.microsoft.com/en-us/entra/identity/monitoring-health/refer…
  2. developer.okta.com/docs/reference/system-log-query
  3. learn.microsoft.com/en-us/entra/id-governance/entitlement-manage…
  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