Control-exception-to-remediation completeness scorecard: seven pass, partial or fail checks for an exception trail

Short answer

A control-exception-to-remediation trail breaks when each system keeps its own clock: the GRC record says the exception ended, while the identity provider still shows the access granted because the grant itself never carried an end date. Seven checks show whether a company's records are complete enough to discuss: coverage overlap, exception IDs in tickets, identity log retention, extension history, where expiry takes effect, removal records and retest evidence. Score each pass, partial or fail from a conversation, without opening a record.

Visual briefFull-size diagram
Seven check cards for an exception trail tick in turn as pass, partial or fail, while a semicircular gauge needle swings up to 8 of 14 points.
Illustrative scorecard for a fictional benefits administrator. Extension history is the check that fails.

This scorecard is part of the control-exception-to-remediation records guide. The identifiers it tests are laid out step by step in the record chain.

Scoring rules before you start

Each check scores 2 for pass, 1 for partial and 0 for fail, for a maximum of 14. A pass means a named owner says the condition holds across the years they describe. Partial means it holds for some years, some applications or some exception types, and they can say which. Fail means it does not hold or nobody knows; write "unknown" beside the zero.

Ask for descriptions and estimates, never for examples. "Roughly what share of access tickets cite the exception ID?" is a good question. "Could you show me one?" is not. Your notes record systems, years, shares and owners only: no exception rationales, user names, group names or log extracts.

Seven checks for an exception trail

CheckAsk at metadata levelPassPartialFail
1. Coverage overlap"Since when has each system held exceptions, access changes and tickets?"Three or more years held in GRC, identity provider and ticketing at onceOverlap under three years, or one system migrated with partial historyOne of the three has no history before last year
2. Exception ID in tickets"Do access request tickets carry the exception or risk ID?"Required field on every access ticketTyped in by habit; common but not enforcedNot recorded; grants cannot be tied to approvals
3. Identity log retention"How far back do identity audit events go, and are they exported?"Exported to storage for the whole exception periodExported from a recent year onlyNative retention only
4. Extension history"When an exception is extended, is the extension a new entry or an edit to the end date?"Each extension recorded separately with approverExtensions tracked for some exception typesEnd date edited in place; original terms lost
5. Where expiry takes effect"When an exception ends, does anything remove the access automatically?"End date set on the grant itself for in-scope systemsAutomatic for some applications, manual elsewhereExpiry exists only in the GRC tool
6. Removal record"Is each removal recorded with a ticket that cites the exception or the review that found it?"Removal ticket with a reference every timeRemoval recorded, reference often missingRemovals not recorded separately
7. Retest evidence"When a control is retested after remediation, is the evidence attached?"Evidence attached to the exception or ticketAttached for key controls onlyRetest marked effective with nothing attached

Check 3 needs care because the defaults are short. 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. A company can pass check 1 on GRC history and still fail check 3, which means its older exceptions have approvals but no proof of what happened to the access.

The expiry test: does an expired exception stay active somewhere else?

Check 5 is the one to spend time on, because it predicts how often the records disagree. NIST SP 800-53 control enhancement AC-2(2) calls for temporary and emergency accounts to be removed or disabled automatically after a defined period, rather than when an administrator gets to it. Some identity platforms can hold that date: in Microsoft Entra entitlement management, an access package assignment can be set to expire on a date or after a number of days, and its group and app access is then removed unless another assignment grants it.

When the date lives only in the GRC tool, nothing acts on it. The exception flips to expired on schedule, the access stays, and the mismatch lasts until a periodic access review or an alert catches it. Ask: "For an exception that ended last quarter, which system would have removed the access, and when would anyone have noticed if it had not?" Score pass if the answer names an automatic expiry, partial if it names a review cycle with a known frequency, fail if the answer is "we would hope someone remembered."

A company that fails check 5 is not a worse introduction. Its mismatches, and the reviews that found them, can be the most instructive part of its history. What matters is that the mismatch can be measured, which needs checks 3 and 6 to pass at least partly.

Illustrative: a benefits administrator scores 8 of 14

Illustrative. A fictional 380-person benefits administrator answered the seven checks across two short calls, one with internal audit and one with IT security.

CheckMarkPointsWhat they said
1. Coverage overlapPass2GRC since 2020, identity provider since 2018, ticketing since 2015
2. Exception ID in ticketsPartial1Common since 2022, not a required field
3. Identity log retentionPartial1Exported to storage since 2023 only
4. Extension historyFail0Extensions overwrite the end date
5. Where expiry takes effectPartial1Automatic for two finance apps; quarterly review elsewhere
6. Removal recordPass2Removal tickets cite the review or exception
7. Retest evidencePartial1Attached for key financial controls
Total8 of 148Strong removals; weak extension history

Summarized for the sponsor: from 2023 the company can show approval, grant, removal and retest for most exceptions; extended exceptions lose their original end date; before 2023 the access side relies on tickets because identity events are gone. That is a fair, metadata-only description. The internal control narrative example shows how the controls themselves are documented, and exception handling data for AI agents explains why exception records matter more broadly.

Who answers which check, and who signs off

Risk or internal audit answers checks 1, 4 and 7. IT security answers 3 and 5. IT operations answers 2 and 6. None of them authorizes a licensing discussion; that is the CEO, who may bring in the CFO, CIO, chief risk officer or general counsel as advisers. If the company has had a security incident, read whether a company with a data breach can license data before raising it, and use the data quality due diligence resource for questions a reviewer may add.

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 you submit.

The score does not tell you whether audit or customer commitments allow any use, how much security detail must be removed, or whether a buyer wants the history. Those stay unknown until SourceX reviews the company under its own agreement.

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 has scored all seven checks honestly and the CEO will discuss its exception history, register as a partner, confirm the company against 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

Should a low score stop the introduction?

Not by itself. The scorecard shows where the trail is thin, which is useful to a reviewer. A company with honest partial marks is a better introduction than one whose answers were guessed to look complete.

Can the IT team answer all seven checks?

Rarely. Coverage, extension history and retest evidence usually sit with risk or internal audit, while retention and expiry sit with IT security. Plan for two short conversations if one is not possible.

Does a past security incident change the scoring?

No. Score the records as they are. Whether an incident affects licensing is a separate question that SourceX reviews with the company.

Sources

  1. csrc.nist.gov/CSRC/media/Projects/risk-management/800-53 D…
  2. learn.microsoft.com/en-us/entra/identity/monitoring-health/refer…
  3. developer.okta.com/docs/reference/system-log-query
  4. learn.microsoft.com/en-us/entra/id-governance/entitlement-manage…
  5. 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