{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-24T17:09:18.442Z",
  "record_id": "VXI-EXT-PROCUREMENT-SERVICENOW-REST-ENDPOINT-TABLE-FIELD-ACLS-01-v1",
  "record_kind": "external_reference",
  "title": "ServiceNow REST endpoint and data ACLs",
  "system": "ServiceNow",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does access to a ServiceNow REST endpoint establish permission to every table and field it exposes?",
  "near_questions": [
    "Can a ServiceNow REST response omit fields because of ACLs?",
    "Do application Can read flags control ServiceNow web-service calls?",
    "What separates endpoint access from table access in ServiceNow?",
    "Does an API role prove complete field visibility?"
  ],
  "supported_claims": [
    {
      "claim": "The Brazil REST guide separates endpoint role and ACL requirements from table and field access. Fields denied by ACLs are omitted from REST query responses. Direct table web-service access also has a dedicated enablement setting; application CRUD flags such as Can read or Can create do not apply to web-service requests.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Universal table restriction or bypass from a single role or scope",
    "The buyer instance’s ACLs, policies and returned-field completeness are unknown.",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "The Brazil REST guide separates endpoint role and ACL requirements from table and field access. Fields denied by ACLs are omitted from REST query responses. Direct table web-service access also has a dedicated enablement setting; application CRUD flags such as Can read or Can create do not apply to web-service requests.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "REST APIs — Brazil",
    "source_url": "https://www.servicenow.com/docs/r/api-reference/rest-api-explorer/c_RESTAPI.html",
    "checked_on": "2026-10-24",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-SERVICENOW-REST-ENDPOINT-TABLE-FIELD-ACLS-01-v1",
    "candidate_record_sha256": "f2eb014431d3b57e541db610bc597dd5068b00bc7f6421ba25642813c67b94e5",
    "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 Brazil REST guide separates endpoint role and ACL requirements from table and field access. Fields denied by ACLs are omitted from REST query responses. Direct table web-service access also has a dedicated enablement setting; application CRUD flags such as Can read or Can create do not apply to web-service requests.",
    "required_buyer_context": "Endpoint and applicable REST access policy; Calling user’s table and field ACL evidence; Table web-service setting and required result fields. 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-24",
    "claim_to_check": "Does access to a ServiceNow REST endpoint establish permission to every table and field it exposes?",
    "documented_statement": {
      "status": "documented",
      "statement": "The Brazil REST guide separates endpoint role and ACL requirements from table and field access. Fields denied by ACLs are omitted from REST query responses. Direct table web-service access also has a dedicated enablement setting; application CRUD flags such as Can read or Can create do not apply to web-service requests.",
      "source_ids": [
        "servicenow-rest-extract"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Evaluate endpoint admission and actual data ACLs separately instead of treating a role or OAuth scope as the complete table boundary.",
      "source_ids": [
        "servicenow-rest-extract"
      ]
    },
    "buyer_evidence_required": [
      "Endpoint and applicable REST access policy",
      "Calling user’s table and field ACL evidence",
      "Table web-service setting and required result fields"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Refuse an all-fields or all-tables claim from endpoint access alone."
    },
    "unknowns": "The buyer instance’s ACLs, policies and returned-field completeness are unknown.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "The buyer instance’s ACLs, policies and returned-field completeness are unknown."
    },
    "evidence_sources": [
      {
        "source_id": "servicenow-rest-extract",
        "url": "https://www.servicenow.com/docs/r/api-reference/rest-api-explorer/c_RESTAPI.html",
        "final_url": "https://www.servicenow.com/docs/r/api-reference/rest-api-explorer/c_RESTAPI.html",
        "status": 200,
        "captured_at_utc": "2026-10-24T17:09:18.308Z",
        "sha256": "f37f81c5dbee32707e79523e790db22a288d4ee9b25b3130575c251cd4fd9107",
        "bytes": 9822,
        "title": "REST APIs — Brazil",
        "hash_basis": "SHA-256 of exact extracted section text UTF-8 bytes in the private .body file, not a publisher HTML hash.",
        "rights_review": "Factual paraphrase and source metadata only; raw source retained privately and not redistributed.",
        "capture_method": "Inspected web-tool extraction of the primary documentation section; raw browser HTML contained an unpopulated application shell.",
        "checked_on": "2026-10-24",
        "capture_status": 200,
        "claim_review_completed": true,
        "reviewed_sections": [
          "REST API roles",
          "REST API ACLs",
          "REST API table access"
        ],
        "version_context": "Brazil documentation; page updated 10 September 2026, inspected 24 October 2026. Hash identifies the extracted section, not the full HTML."
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.",
    "paid_value": {
      "decision_context": "Avoid treating an admitted API request as unrestricted or complete data access.",
      "free": "Complete review, sources, practical questions 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": "Recheck the documented behavior, product version and buyer evidence before relying on a current outcome."
    },
    "buyer_relevance": "Avoid treating an admitted API request as unrestricted or complete data access.",
    "refusal_conditions": [
      "Refuse an all-fields or all-tables claim from endpoint access alone."
    ]
  },
  "niche": {
    "niche_id": "agent-authority-action-evidence",
    "label": "Agent Authority & Action Evidence",
    "classification_id": "governance",
    "classification_label": "Agent Governance & Policy Boundaries",
    "topic_id": "governance",
    "buyer_intent": "Avoid treating an admitted API request as unrestricted or complete data access.",
    "comparison_role": "supplementary_discovery"
  },
  "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#servicenow-rest-endpoint-table-field-acls",
  "machine_readable_record": "/varexis-index/records/servicenow-rest-endpoint-table-field-acls.json"
}
