Customer access review remediation records across systems: a map of identity, GRC, ticketing and HR keys

Short answer

Reconstructing customer access review remediation takes four joins: review item to GRC finding, finding to change ticket, ticket to the identity audit events that prove the change, and service account owner to the HR record that shows whether that person still works there. A tenant merger adds a fifth: old directory object to new one, which only exists if the company kept a crosswalk. The audit-event join is the most fragile, because identity logs expire in weeks unless they were streamed elsewhere.

Visual briefFull-size diagram
Five system nodes, identity provider review, GRC tool, ticketing, identity audit log and HR system, with linking keys, principal ID, ticket key, object ID and time window, and employee ID, traveling between them, plus a dashed crosswalk to a target tenant.
Illustrative system map for a fictional SaaS company; identifiers and keys are invented.

This map is part of the customer access review remediation guide. The exception examples page tells one case as a story; this page shows the keys that hold it together.

Five systems, five owners

Identity provider review. Holds review campaigns, each item reviewed, the decision and the justification. Owner: identity administration, under the security operations head.

GRC tool. Holds findings, owner responses and remediation status. Owner: the GRC or compliance lead.

Ticketing system. Holds change requests, approvals and implementation notes, in a tool such as Jira or ServiceNow. Jira, for example, keeps each issue's field changes with old and new values in its History tab, though it has no built-in report of when a field changed. Owner: IT service management.

Identity audit log. Holds the events proving an owner change or role removal happened. Identity providers keep these events for a limited time by default, depending on provider and license: Microsoft Entra, for example, keeps audit logs for 7 days on Free and 30 days on P1 and P2, and expired data cannot be recovered unless it was archived. Owner: security operations, often via a SIEM.

HR system. Holds employee IDs, managers and departure dates. Owner: HR systems.

System map: record, linking key and owner

SystemRecordLinking key it carriesJoins toOwner
Identity provider reviewReview item and decisionPrincipal ID plus review cycleGRC findingIdentity administration
GRC toolFinding and owner responseFinding ID; principal ID quoted; ticket keyReview item, change ticketGRC lead
Ticketing systemApproved changeTicket key; object ID in the requestFinding, audit eventsIT service management
Identity audit logOwner change, role removal eventsObject ID and timestampTicket by object and time windowSecurity operations
Identity directoryService account and owner attributeObject ID; owner's employee IDHR departure recordIdentity administration
HR systemEmployee and departure dateEmployee IDOwner attributeHR systems
Migration crosswalkOld object to new objectSource and target object IDsRecords before and after a mergerMerger program lead

Note the one join that is not a stored key: ticket to audit event. The ticket names the object; the audit log records events on that object; the match is made by object ID plus a time window around the change date. If the ticket never names the object ID, the match falls back to display names and guesswork.

One fully joined case (Illustrative)

This case differs from the one on the exception page. All identifiers are invented, for a fictional 900-person B2B software company.

  1. Review item, October cycle. A contractor account with an admin role in the customer support console, object ID ending 4f91, is marked "deny" by the reviewing manager: "contract ended in September".
  2. HR record. The account's sponsor attribute holds employee ID E-20733, the manager who engaged the contractor. The contractor's end date sits in the vendor-management list HR keeps, not in the core HR system, so this join runs through a second table.
  3. GRC finding GRC-305 quotes the principal and the October cycle, records the manager's confirmation and cites change 5120.
  4. Change 5120 names object 4f91 and the admin role, approved by the CISO's delegate on October 22.
  5. Audit events on object 4f91 on October 23: role removed, account disabled. Matched to change 5120 by object and date, and held in a log archive because the identity provider's own retention had passed.
  6. Next cycle. In January the account no longer appears, which is itself evidence the removal stuck.

Six records, five systems, one case. Now suppose the company merges tenants in December and recreates its remaining contractor accounts. A crosswalk is what lets a reviewer show that 4f91 was removed and not quietly rebuilt under a new ID; without one, the January absence proves nothing.

The merger join, and why partners only ask about it

Tenant consolidations often recreate accounts. Microsoft's cross-tenant synchronization, for instance, provisions B2B user accounts in the target tenant for source-tenant members, which are directory objects of their own. That documentation covers user accounts; how service accounts and app registrations were moved is a question for the company's administrators. Either way, the new tenant's reviews cannot see that an account was flagged last year without a mapping.

A partner does not build that mapping or look at it. It is enough to ask three things: does a crosswalk exist, who keeps it, and does it cover service accounts as well as people? The answers go into the introduction as metadata.

Joins to check, and the question that tests each

JoinTypical gapQuestion for the company
Review item to findingFindings typed by hand with no principal IDDo findings quote the principal ID and review cycle?
Finding to change"Resolved" with no ticket keyDo findings cite change ticket keys?
Change to audit eventEvents expired before exportAre identity logs streamed to storage or a SIEM, and since when?
Account to personOwner held as a display nameDoes the owner attribute hold an employee ID?
Old to new objectNo mapping kept during migrationWas a crosswalk kept, and does it include service accounts?

Access review records differ from audit-driven files: the management letter remediation page deals with points raised by an outside auditor, whose workpapers are not the company's to license, while access reviews are the company's own control. Who can see records during a licensing project is covered in who has access to data in a licensing deal; diligence-side context sits in cybersecurity due diligence and M&A contract review.

Qualification before the introduction

A good map shows how complete the chains are. It does not settle who can license them; the who-can-license page does. The introduced company needs 50+ full-time employees at peak (contractors excluded), a 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. Partners sign the Channel Partner Agreement before submitting introductions, and the first valid introduction within the 90-day window is credited when the company submits a verified application. Buyer interest, the rights result and any offer stay unknown until SourceX reviews the opportunity. More sectors sit under industries.

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 the security operations head confirms that findings cite tickets and identity events are kept beyond the default, register as a partner, check the company against who qualifies and read the program terms before you make the introduction.

  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

Does the partner build the crosswalk between old and new accounts?

No. A partner only asks whether one exists, who keeps it and since when. Building or handling identity mappings is the company's work under its own controls.

What if the owner attribute holds a display name instead of an employee ID?

Note it as a weak join. Names change and repeat, so matching owners to HR departure dates becomes less reliable, and SourceX should know before estimating how complete the chains are.

Are GRC findings enough without audit events?

They show decisions, not proof that the decisions were carried out. Many companies hold the first for years and the second for weeks, which is why the audit-event join is the one to ask about first.

Sources

  1. learn.microsoft.com/en-us/entra/identity/multi-tenant-organizati…
  2. refer.sourcex.si/terms
  3. support.atlassian.com/jira/kb/how-to-identify-and-list-when-a-fiel…
  4. learn.microsoft.com/en-us/entra/identity/monitoring-health/refer…

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