{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-11T17:52:53.561Z",
  "record_id": "VXI-EXT-OID-CAEP-SESSION-SCOPE-01-v1",
  "record_kind": "external_reference",
  "title": "CAEP revocation: Match the event's session scope",
  "system": "OpenID CAEP",
  "evidence_family": "security_event_subject_scope",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does a session-revocation event apply to every session belonging to a user?",
  "near_questions": [
    "How should session revocation scope be matched?",
    "Does a revocation event log out every device?",
    "How should a receiver match a complex event subject?",
    "Can I ignore the tenant in a revocation subject?",
    "Is a user identifier enough to match a security event?",
    "How does device identity limit a session event?",
    "Can one event identify several applicable sessions?",
    "Does receiving a revocation prove local access ended?",
    "What identifies the target of a CAEP event?",
    "Should combined subject claims be matched together?",
    "Does a session identifier imply user-wide revocation?",
    "What should be checked before applying a security event?"
  ],
  "supported_claims": [
    {
      "claim": "OpenID CAEP 1.0 identifies revoked sessions through the event's subject. That subject can specify a session or properties used to locate applicable sessions. For a complex subject, matching uses the claims together. A user, device and tenant combination must therefore not be reduced to a user-only match. This defines the event's scope; it does not prove that a receiver found the right local sessions or enforced revocation.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "all user sessions revoked regardless of subject scope",
    "correct local identity mapping from receipt alone",
    "receiver enforcement proven by an event definition"
  ],
  "public_summary": "OpenID CAEP 1.0 identifies revoked sessions through the event's subject. That subject can specify a session or properties used to locate applicable sessions. For a complex subject, matching uses the claims together. A user, device and tenant combination must therefore not be reduced to a user-only match. This defines the event's scope; it does not prove that a receiver found the right local sessions or enforced revocation.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "OpenID Continuous Access Evaluation Profile 1.0, section 3.1",
    "source_url": "https://openid.net/specs/openid-caep-1_0.html",
    "checked_on": "2026-10-11",
    "candidate_record_id": "VXI-EXT-OID-CAEP-SESSION-SCOPE-01-v1",
    "candidate_record_sha256": "72ee497f90e381849981ba755132876008801162ccbabc64907d5a209b066fab",
    "method": "Primary documentation reviewed for the published bounded statement.",
    "deployment_tested_by_varexis": false,
    "revalidation": "The delivered snapshot preserves the review date shown. Recheck current primary documentation and deployment context before relying on present applicability; payment does not trigger fresh research."
  },
  "answer_policy": {
    "classification": "DOCUMENTED_WITH_DEPLOYMENT_BOUNDARY",
    "bounded_answer": "OpenID CAEP 1.0 identifies revoked sessions through the event's subject. That subject can specify a session or properties used to locate applicable sessions. For a complex subject, matching uses the claims together. A user, device and tenant combination must therefore not be reduced to a user-only match. This defines the event's scope; it does not prove that a receiver found the right local sessions or enforced revocation.",
    "required_buyer_context": "Subject format, combined identifiers, local session mapping and receiver enforcement evidence.",
    "missing_evidence": "A broader claim needs evidence matching the intended use. Payment does not upgrade the evidence state."
  },
  "private_boundary": "Raw logs, thresholds, private paths, source code, protected mechanisms and reconstruction-level details are excluded from public and paid delivery.",
  "paid_access_note": "The full published answer and boundaries are free. Paid access saves the selected route and source versions, with an unsigned receipt when purchased. Preview coverage before paying. Fresh research, bespoke assessment and protected evidence are excluded.",
  "service_route": {
    "request_guide": "/varexis-index/request.html",
    "request_workflow": "/varexis-index/request-workflow.json",
    "service_id": "single_request",
    "service_routes_url": "/varexis-index/service-routes.json",
    "payment_required": true,
    "availability_endpoint": "/api/index/capabilities",
    "operational_status": "AUTOMATIC_SERVICE_CAPABILITIES_GATED",
    "checkout_url": "/index-access"
  },
  "authority_boundary": "VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.",
  "human_page": "/varexis-index/catalog.html#caep-revocation-session-scope",
  "machine_readable_record": "/varexis-index/records/caep-revocation-session-scope.json"
}
