Audit workforce identity access evidence integrity

What it's for

Turns workforce identity and privileged access assurance into a reproducible evidence-chain audit while preserving human review, lawful basis and correction rights.

What you give it

Inputs split into evidence read from your connected systems, calibration your team owns, and numerical controls that affect precision but never the result's meaning.

{
  "access_events": [
    {
      "account_id": "account-1",
      "authorization_grant_id": "grant-1",
      "evidence_verified": true,
      "id": "event-1",
      "mfa_passed": true,
      "occurred_at_ms": 9500,
      "privilege_level": "admin",
      "resource_id": "production",
      "trusted_device_passed": true
    }
  ],
  "access_grants": [
    {
      "account_id": "account-1",
      "approval_id": "approval-1",
      "evidence_verified": true,
      "granted_at_ms": 3000,
      "id": "grant-1",
      "least_privilege_reviewed": true,
      "privilege_level": "admin",
      "resource_id": "production",
      "revoked_at_ms": null
    }
  ],
  "as_of_ms": 10000,
  "identity_accounts": [
    {
      "created_at_ms": 2000,
      "disabled_at_ms": null,
      "evidence_verified": true,
      "id": "account-1",
      "identity_provider_id": "idp-core",
      "mfa_enforced": true,
      "privilege_level": "admin",
      "subject_id": "subject-opaque-1",
      "trusted_device_required": true
    }
  ],
  "identity_evidence": [
    {
      "account_id": null,

What you get back

This is the actual output of running the example above — computed by the same function the platform calls, not an illustration.

{
  "assumptions": [
    "Identity subjects are opaque authorized references; engagement, account, grant, evidence and access-event ledgers are complete, immutable, legally obtained and point-in-time.",
    "Concurrent work is relevant only through an explicit applicable disclosure policy and verified conflicting commitments; work hours, geography, language, nationality and protected traits are not identity-risk evidence."
  ],
  "decision": "identity_access_evidence_ready_for_authorized_human_review",
  "event_diagnostics": [
    {
      "account_id": "account-1",
      "event_id": "event-1",
      "failed_gates": [],
      "integrity_pass": true
    }
  ],
  "failed_gates": [],
  "grant_diagnostics": [
    {
      "account_id": "account-1",
      "active_at_as_of": true,
      "failed_gates": [],
      "grant_id": "grant-1",
      "integrity_pass": true,
      "resource_id": "production"
    }
  ],
  "identity_access_integrity_ready": true,
  "limitations": [
    "Passing establishes evidence and authorization-chain integrity, not real-world identity, employee intent, guilt, nationality, espionage, policy breach or suitability for employment.",
    "Failed gates require authorized human security review, correction rights and due process; the function takes no access, investigation, disclosure or employment action."
  ],
  "method": "point_in_time_workforce_identity_access_provenance_audit_v1",
  "subject_diagnostics": [
    {
      "active_accounts": 1,
      "authorized_accounts": 1,
      "engagement_active": true,
      "failed_gates": [],
      "integrity_pass": true,
      "subject_id": "subject-opaque-1"
    }
  ],
  "summary": {
    "access_events": 1,
    "accounts": 1,

How it works

Statistical audit & measurement — Check whether a number is fit to decide on: coverage, timing, reconciliation, and the gaps a dashboard hides.

1. 1 Freeze the authorized subject/account perimeter and engagement, account, grant, evidence-validity and access-event intervals at the requested as-of time.
2. 2 Require each declared evidence type to have enough distinct source/artifact pairs that are current, independently verified, legally obtained and evidence-verified.
3. 3 Reconcile every access event to the same subject, account, active grant, resource and privilege boundary, then return repair gates without inferring identity or intent.

Before you trust it

Every tool in the catalog ships with the conditions under which its answer is meaningful — and the conditions under which it should abstain instead of guessing.

Calibrating it to your org

Calibration workflow

1. 1 Define the management decision, target outcome, aggregate unit, privacy boundary, cadence, and prediction/intervention horizon for this organization.
2. 2 Build a tenant-scoped historical cohort using only information available before each prediction or decision; preserve zero periods, censoring, assignment probabilities, and unresolved outcomes when the method requires them.
3. 3 Estimate statistical parameters on training history, but obtain costs, utilities, risk tolerance, practical-effect thresholds, capacity, and policy constraints from accountable decision owners.
4. 4 Validate on later time windows or held-out aggregate units at the deployment grain, against a simple baseline and the function-specific validation strategy.
5. 5 Deploy only if the returned decision clears evidence, overlap, calibration, robustness, and guardrail checks; warning, unsupported, schema-gap, and fallback decisions are abstentions.
6. 6 Monitor realized outcomes, data drift, coverage, and decision regret; recalibrate at a governed cadence or after a detected regime/definition change, never merely because a stakeholder dislikes the result.

Call it from your AI

You don't wire up 388 tools in your MCP client. The GitRevio MCP server exposes 18 tools, three of which let an agent search the catalog, read a tool's schema, and run it — so the assistant finds this one on its own.

gitrevio_capabilities_search
  { "q": "audit the pointintime chain from an" }
  → finds "audit_workforce_identity_access_evidence_integrity"

gitrevio_capability_describe
  { "capability_id": "audit_workforce_identity_access_evidence_integrity" }
  → returns the input schema and agent guidance shown on this page

gitrevio_capability_run
  { "capability_id": "audit_workforce_identity_access_evidence_integrity", "arguments": { ... } }
  → returns the result shown above

Works in Claude Desktop, Claude Code, Cursor, Cline, Continue.dev, Goose and Aider. See the MCP server.

Related tools

See every tool in Security, access & compliance →