{ "schema": "varexis-index-free-publication-preview/1", "catalogue_version": "pub-2-tranche-52-v1", "route_id": "agentic_reviewed_spiffe_filesystem_single_read_rotation", "record_id": "VXI-EXT-PROCUREMENT-SPIFFE-FILESYSTEM-SINGLE-READ-ROTATION-01-v1", "question": "Can separate file reads load a mismatched SPIFFE private key and certificate despite atomic rotation?", "answer": "The pinned, incubating filesystem delivery specification recommends loading the credential bundle in one open/read/close cycle. Separate cycles for key and certificate can straddle a rotation and produce a mismatched pair, even when the provisioning system writes atomically. Applications must reload updated bundles promptly and must not assume the new key type or chain matches the old one.", "records": [ { "record_id": "VXI-EXT-PROCUREMENT-SPIFFE-FILESYSTEM-SINGLE-READ-ROTATION-01-v1", "url": "/varexis-index/records/spiffe-filesystem-single-read-rotation.json", "content_sha256": "ddebb07a6e87d759ecb412679fb37f594fd13b6ec3bb502302bc36b2461aad62", "evidence": { "schema": "varexis-public-evidence-record/0.3", "generated_at_utc": "2026-10-24T21:56:24.175Z", "record_id": "VXI-EXT-PROCUREMENT-SPIFFE-FILESYSTEM-SINGLE-READ-ROTATION-01-v1", "record_kind": "external_reference", "title": "SPIFFE filesystem key and certificate consistency", "system": "SPIFFE", "evidence_family": "vendor_evidence_review", "index_status": "PUBLIC_SAFE_SOURCE_REVIEW", "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY", "canonical_question": "Can separate file reads load a mismatched SPIFFE private key and certificate despite atomic rotation?", "near_questions": [ "Why can atomic SPIFFE file rotation still cause a key mismatch?", "Should a SPIFFE credential file be opened once for both key and chain?", "Can a workload assume rotated SPIFFE credentials use the same key type?", "What must a file-based SPIFFE client reload after rotation?" ], "supported_claims": [ { "claim": "The pinned, incubating filesystem delivery specification recommends loading the credential bundle in one open/read/close cycle. Separate cycles for key and certificate can straddle a rotation and produce a mismatched pair, even when the provisioning system writes atomically. Applications must reload updated bundles promptly and must not assume the new key type or chain matches the old one.", "reliance": "DOCUMENTED_CAPABILITY_ONLY" } ], "not_demonstrated_claims": [ "The buyer filesystem, file permissions and reload implementation are untested.", "Authentication or a policy result does not establish business approval, safe tool behaviour or completed execution.", "The filesystem delivery standard is incubating; stable support in a buyer implementation is not established.", "Buyer deployment testing, live runtime enforcement, certification or permission to act", "Expanded capabilities or licences for existing INDEX executables" ], "public_summary": "The pinned, incubating filesystem delivery specification recommends loading the credential bundle in one open/read/close cycle. Separate cycles for key and certificate can straddle a rotation and produce a mismatched pair, even when the provisioning system writes atomically. Applications must reload updated bundles promptly and must not assume the new key type or chain matches the old one.", "related_record_ids": [], "source_review": { "source_type": "official_external_documentation", "source_title": "The SPIFFE Filesystem Delivery Standard", "source_url": "https://raw.githubusercontent.com/spiffe/spiffe/49a9cbbc018c39ec6643ad3301632f9f4549258b/standards/SPIFFE_Filesystem_Delivery.md", "checked_on": "2026-10-24", "candidate_record_id": "VXI-EXT-PROCUREMENT-SPIFFE-FILESYSTEM-SINGLE-READ-ROTATION-01-v1", "candidate_record_sha256": "e9cc7efdd3b80c4f45c221e618629c07ed79f924c956698203bce589f6826f32", "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 pinned, incubating filesystem delivery specification recommends loading the credential bundle in one open/read/close cycle. Separate cycles for key and certificate can straddle a rotation and produce a mismatched pair, even when the provisioning system writes atomically. Applications must reload updated bundles promptly and must not assume the new key type or chain matches the old one.", "required_buyer_context": "Provisioner replacement method; Consumer file-read and reload sequence; Deployed filesystem-delivery standard revision and file permissions. 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": "Can separate file reads load a mismatched SPIFFE private key and certificate despite atomic rotation?", "documented_statement": { "status": "documented", "statement": "The pinned, incubating filesystem delivery specification recommends loading the credential bundle in one open/read/close cycle. Separate cycles for key and certificate can straddle a rotation and produce a mismatched pair, even when the provisioning system writes atomically. Applications must reload updated bundles promptly and must not assume the new key type or chain matches the old one.", "source_ids": [ "spiffe-filesystem" ] }, "review_inference": { "status": "review_inference", "statement": "Verify that credential reloads preserve the key-to-certificate pairing. This is a source-based review decision, not an observed deployment result.", "source_ids": [ "spiffe-filesystem" ] }, "buyer_evidence_required": [ "Provisioner replacement method", "Consumer file-read and reload sequence", "Deployed filesystem-delivery standard revision and file permissions" ], "review_condition": { "status": "varexis_review_policy", "statement": "Do not treat atomic file replacement as proof that multiple independent reads are consistent." }, "unknowns": "The buyer filesystem, file permissions and reload implementation are untested.", "unknown_finding": { "status": "unknown", "statement": "The buyer filesystem, file permissions and reload implementation are untested." }, "evidence_sources": [ { "source_id": "spiffe-filesystem", "url": "https://raw.githubusercontent.com/spiffe/spiffe/49a9cbbc018c39ec6643ad3301632f9f4549258b/standards/SPIFFE_Filesystem_Delivery.md", "final_url": "https://raw.githubusercontent.com/spiffe/spiffe/49a9cbbc018c39ec6643ad3301632f9f4549258b/standards/SPIFFE_Filesystem_Delivery.md", "status": 200, "captured_at_utc": "2026-10-24T21:45:01.171Z", "sha256": "261f6482ccbb3b1e7c3ea2af1ff21beb98fb3c71caf632653d2ffc4139578ae8", "bytes": 19393, "title": "The SPIFFE Filesystem Delivery Standard", "hash_basis": "Decoded HTTP response body bytes", "rights_review": "Original factual paraphrase and source metadata only; Apache-2.0 repository captures retained privately and not redistributed.", "checked_on": "2026-10-24", "capture_status": 200, "claim_review_completed": true, "reviewed_sections": [ "2.1 Credential Bundle", "3.1 Loading and Refreshing the Credential Bundle", "2.3 Redaction" ], "version_context": "Pinned spiffe/spiffe revision 49a9cbbc018c39ec6643ad3301632f9f4549258b captured 2026-10-24. Filesystem Delivery is labelled Incubating. Documentation review, not evidence that a buyer implementation conforms." } ], "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": "Verify that credential reloads preserve the key-to-certificate pairing.", "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 pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome." }, "buyer_relevance": "Verify that credential reloads preserve the key-to-certificate pairing.", "refusal_conditions": [ "Do not treat atomic file replacement as proof that multiple independent reads are consistent." ] }, "niche": { "niche_id": "agent-authority-action-evidence", "label": "Agent Authority & Action Evidence", "classification_id": "identity", "classification_label": "Agent Identity, Credentials & Delegation", "topic_id": "identity", "buyer_intent": "Verify that credential reloads preserve the key-to-certificate pairing.", "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#spiffe-filesystem-single-read-rotation", "machine_readable_record": "/varexis-index/records/spiffe-filesystem-single-read-rotation.json" } } ], "access": { "mode": "exact_http_only", "payment_required": false, "purchase_url": null, "mcp_preview_available": false, "paid_saved_retrieval_available": false, "natural_language_search_qualified": false }, "boundary": "Catalogue additions are available free through the exact HTTP JSON links below. Enhanced natural-language discovery is not yet qualified for these records. They are outside MCP search, MCP preview and paid saved retrieval. No search qualification, executable capability or entitlement is added.", "content_sha256": "be12d80c6e662c55480cbaab27729cc88a5c35262013c38e975914f818141c5c" }