{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-16T07:59:18.009Z",
  "record_id": "VXI-EXT-PROCUREMENT-REDSHIFT-RLS-01-v1",
  "record_kind": "external_reference",
  "title": "Redshift RLS: Cross-database and sharing exceptions",
  "system": "Amazon Redshift",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Can an agent assume a Redshift RLS policy follows every cross-database or shared-data access path?",
  "near_questions": [
    "Does Redshift RLS apply identically across databases?",
    "What does IGNORE RLS change?",
    "Can a protected relation be shared without configuration changes?",
    "Which consumer cluster runs the query?",
    "Is the caller privileged to bypass a restriction?",
    "Does a blocked query establish a missing row?",
    "What happens when sharing restrictions are changed?",
    "Which relation has the policy attached?",
    "Does a table flag prove consumer isolation?",
    "Which test should the buyer supply for its access path?",
    "When should an agent avoid claiming tenant separation?",
    "Can I save an RLS applicability review?"
  ],
  "supported_claims": [
    {
      "claim": "The reviewed limitations distinguish ordinary RLS access from cross-database queries and datasharing. Cross-database reads of protected relations are blocked for users without IGNORE RLS; sharing also has explicit restrictions and configuration. Inspect the caller privilege and access path instead of assuming one filter covers all consumers.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Verified buyer configuration or effective access rights",
    "Independent execution, completeness or security testing",
    "Vendor certification, legal compliance or guaranteed suitability"
  ],
  "public_summary": "The reviewed limitations distinguish ordinary RLS access from cross-database queries and datasharing. Cross-database reads of protected relations are blocked for users without IGNORE RLS; sharing also has explicit restrictions and configuration. Inspect the caller privilege and access path instead of assuming one filter covers all consumers.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Redshift RLS considerations and limitations",
    "source_url": "https://docs.aws.amazon.com/redshift/latest/dg/t_rls_usage.html",
    "checked_on": "2026-10-16",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-REDSHIFT-RLS-01-v1",
    "candidate_record_sha256": "092afdb4e3e54e7f27283e90da587d90795bb1521174b3785cf50dc3ac50dd4f",
    "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": "The reviewed limitations distinguish ordinary RLS access from cross-database queries and datasharing. Cross-database reads of protected relations are blocked for users without IGNORE RLS; sharing also has explicit restrictions and configuration. Inspect the caller privilege and access path instead of assuming one filter covers all consumers.",
    "required_buyer_context": "Relation settings, RLS exception privileges and sharing path. Effective buyer configuration and dated operational evidence are required.",
    "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-16",
    "claim_to_check": "One RLS policy proves identical filtering on every data access path.",
    "documented_statement": {
      "status": "documented",
      "statement": "The reviewed limitations distinguish ordinary RLS access from cross-database queries and datasharing. Cross-database reads of protected relations are blocked for users without IGNORE RLS; sharing also has explicit restrictions and configuration. Inspect the caller privilege and access path instead of assuming one filter covers all consumers.",
      "source_ids": [
        "redshift-rls"
      ]
    },
    "buyer_evidence_required": [
      "Relation RLS and sharing configuration.",
      "Caller privileges including IGNORE RLS.",
      "Cross-database or consumer query path."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Require path-specific evidence before claiming row isolation."
    },
    "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": "redshift-rls",
        "url": "https://docs.aws.amazon.com/redshift/latest/dg/t_rls_usage.html",
        "final_url": "https://docs.aws.amazon.com/redshift/latest/dg/t_rls_usage.html",
        "title": "Redshift RLS considerations and limitations",
        "checked_on": "2026-10-16",
        "sha256": "6bb54a5c115e4fe76716a27d745cdf35ac4de744fff34fd9398ea153f03ee376",
        "bytes": 24749
      }
    ],
    "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": "Retain the access-path exceptions that procurement must resolve for row-level isolation.",
      "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": "Relation settings, RLS exception privileges and sharing path"
    }
  },
  "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#redshift-rls-cross-database-exceptions",
  "machine_readable_record": "/varexis-index/records/redshift-rls-cross-database-exceptions.json"
}