ExplorerComputer ScienceCybersecurity
Research PaperResearchia:202603.11014

The Bureaucracy of Speed: Structural Equivalence Between Memory Consistency Models and Multi-Agent Authorization Revocation

Vladyslav Parakhin

Abstract

The temporal assumptions underpinning conventional Identity and Access Management collapse under agentic execution regimes. A sixty-second revocation window permits on the order of $6 \times 10^3$ unauthorized API calls at 100 ops/tick; at AWS Lambda scale, the figure approaches $6 \times 10^5$. This is a coherence problem, not merely a latency problem. We define a Capability Coherence System (CCS) and construct a state-mapping $\varphi : Σ_{\rm MESI} \to Σ_{\rm auth}$ preserving transition stru...

Submitted: March 11, 2026Subjects: Cybersecurity; Computer Science

Description / Details

The temporal assumptions underpinning conventional Identity and Access Management collapse under agentic execution regimes. A sixty-second revocation window permits on the order of 6×1036 \times 10^3 unauthorized API calls at 100 ops/tick; at AWS Lambda scale, the figure approaches 6×1056 \times 10^5. This is a coherence problem, not merely a latency problem. We define a Capability Coherence System (CCS) and construct a state-mapping φ:ΣMESIΣauth\varphi : Σ_{\rm MESI} \to Σ_{\rm auth} preserving transition structure under bounded-staleness semantics. A safety theorem bounds unauthorized operations for the execution-count Release Consistency-directed Coherence (RCC) strategy at DrccnD_{\rm rcc} \leq n, independent of agent velocity vv -- a qualitative departure from the O(vTTL)O(v \cdot \mathrm{TTL}) scaling of time-bounded strategies. Tick-based discrete event simulation across three business-contextualised scenarios (four strategies, ten deterministic seeds each) confirms: RCC achieves a 120×120\times reduction versus TTL-based lease in the high-velocity scenario (50 vs. 6,000 unauthorized operations), and 184×184\times under anomaly-triggered revocation. Zero bound violations across all 120 runs confirm the per-capability safety guarantee. Simulation code: https://github.com/hipvlady/prizm


Source: arXiv:2603.09875v1 - http://arxiv.org/abs/2603.09875v1 PDF: https://arxiv.org/pdf/2603.09875v1 Original Link: http://arxiv.org/abs/2603.09875v1

Please sign in to join the discussion.

No comments yet. Be the first to share your thoughts!

Access Paper
View Source PDF
Submission Info
Date:
Mar 11, 2026
Topic:
Computer Science
Area:
Cybersecurity
Comments:
0
Bookmark