{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-18T13:45:35.999Z",
  "record_id": "VXI-EXT-PROCUREMENT-CLOUDTRAIL-SHARED-EVENT-01-v1",
  "record_kind": "external_reference",
  "title": "CloudTrail: Cross-account event IDs need a shared-action join",
  "system": "AWS CloudTrail",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Can different CloudTrail eventIDs in two accounts describe the same cross-account action?",
  "near_questions": [
    "How do we join CloudTrail evidence from caller and resource-owner accounts?",
    "Can one AWS action have more than one CloudTrail eventID?",
    "What does CloudTrail sharedEventID identify?",
    "Why do recipientAccountID values differ for the same action?",
    "Does a missing sharedEventID prove no cross-account access?",
    "Should cross-account logs be counted as two agent actions?",
    "Which identifiers distinguish account records from the shared action?",
    "How do we avoid overcounting a cross-account KMS operation?",
    "Can deduplication by eventID alone reconcile both accounts?",
    "What evidence remains unmatched after the shared-event join?",
    "When is sharedEventID absent from CloudTrail records?",
    "What account context belongs in an action reconciliation review?"
  ],
  "supported_claims": [
    {
      "claim": "CloudTrail documents sharedEventID for an AWS action delivered to multiple accounts. Those records share sharedEventID while retaining distinct eventID and recipientAccountID values. The shared field is absent when caller and resource owner are the same account. Counting different eventIDs alone can therefore overstate cross-account actions.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Verified buyer configuration, actual data erasure, effective access or completed business actions",
    "Legal advice, compliance determination, vendor certification or safety assurance",
    "Runtime enforcement, permission to act or expanded licensed-checker coverage"
  ],
  "public_summary": "CloudTrail documents sharedEventID for an AWS action delivered to multiple accounts. Those records share sharedEventID while retaining distinct eventID and recipientAccountID values. The shared field is absent when caller and resource owner are the same account. Counting different eventIDs alone can therefore overstate cross-account actions.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "AWS CloudTrail: Event record contents",
    "source_url": "https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudtrail-event-reference-record-contents.html",
    "checked_on": "2026-10-18",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-CLOUDTRAIL-SHARED-EVENT-01-v1",
    "candidate_record_sha256": "b9a3aabaad72fb2e7360cd7d08c224435421a82ebe00d5a2c2f55f431a7d94bc",
    "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": "CloudTrail documents sharedEventID for an AWS action delivered to multiple accounts. Those records share sharedEventID while retaining distinct eventID and recipientAccountID values. The shared field is absent when caller and resource owner are the same account. Counting different eventIDs alone can therefore overstate cross-account actions.",
    "required_buyer_context": "The account-specific event records and their provenance. The sharedEventID, eventID and recipientAccountID values where present. The actual action, account relationship and any unmatched evidence. Buyer deployment not inspected.",
    "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.",
  "decision_profile": {
    "schema": "varexis-vendor-evidence-review/1",
    "review_status": "documentation_review_only",
    "checked_on": "2026-10-18",
    "claim_to_check": "Can different CloudTrail eventIDs in two accounts describe the same cross-account action?",
    "documented_statement": {
      "status": "documented",
      "statement": "CloudTrail documents sharedEventID for an AWS action delivered to multiple accounts. Those records share sharedEventID while retaining distinct eventID and recipientAccountID values. The shared field is absent when caller and resource owner are the same account. Counting different eventIDs alone can therefore overstate cross-account actions.",
      "source_ids": [
        "cloudtrail-cross-account"
      ]
    },
    "buyer_evidence_required": [
      "The account-specific event records and their provenance.",
      "The sharedEventID, eventID and recipientAccountID values where present.",
      "The actual action, account relationship and any unmatched evidence."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not count account-specific records as separate actions solely because eventIDs differ, or treat missing sharedEventID as proof that no action occurred."
    },
    "unknowns": "The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.",
    "evidence_sources": [
      {
        "source_id": "cloudtrail-cross-account",
        "url": "https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudtrail-event-reference-record-contents.html",
        "final_url": "https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudtrail-event-reference-record-contents.html",
        "title": "AWS CloudTrail: Event record contents",
        "checked_on": "2026-10-18",
        "captured_at_utc": "2026-10-18T13:33:51.635Z",
        "version_context": "Rolling CloudTrail guide; sharedEventID introduced in event version 1.03",
        "sha256": "c46f758310a03b84af044700434d36cb22b608d399cf0ef913659f0aa00662e3",
        "bytes": 52436,
        "hash_basis": "Decoded HTTP response body bytes; identifies captured content, not truth or certification",
        "reviewed_sections": [
          "Can different CloudTrail eventIDs in two accounts describe the same cross-account action?"
        ]
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.",
    "paid_value": {
      "decision_context": "An audit team reconciling agent activity across account boundaries needs to distinguish account-specific records from separate business actions.",
      "free": "Complete review, practical questions, sources and limitations; may be saved locally.",
      "single_request": "Existing server-saved version-bound route snapshot for later authenticated retrieval.",
      "evidence_receipt": "The same snapshot plus the existing unsigned delivery receipt.",
      "excluded": [
        "Fresh vendor research",
        "Continuous monitoring or change alerts",
        "Testing the buyer configuration",
        "Private evidence or vendor certification"
      ],
      "integrity": "Hashes identify content versions; they do not prove truth or provide a signature."
    },
    "revalidation": {
      "trigger": "A saved purchase does not recheck the source or buyer configuration.",
      "specific_watch": "The account-specific event records and their provenance. The sharedEventID, eventID and recipientAccountID values where present. The actual action, account relationship and any unmatched evidence."
    },
    "buyer_relevance": "An audit team reconciling agent activity across account boundaries needs to distinguish account-specific records from separate business actions.",
    "refusal_conditions": [
      "Do not count account-specific records as separate actions solely because eventIDs differ, or treat missing sharedEventID as proof that no action occurred."
    ]
  },
  "niche": {
    "label": "Agent Authority & Action Evidence",
    "niche_id": "agent-authority-action-evidence",
    "topic_id": "action-evidence-reconciliation",
    "buyer_intent": "An audit team reconciling agent activity across account boundaries needs to distinguish account-specific records from separate business actions."
  },
  "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#cloudtrail-cross-account-shared-event-correlation",
  "machine_readable_record": "/varexis-index/records/cloudtrail-cross-account-shared-event-correlation.json"
}
