Policy Administration Point (PAP) dynamic policy profiling and proportionality

Research Question

How can a Policy Administration Point (PAP) dynamically map a governed asset's metadata, specifically its invariants and Confidentiality, Integrity, and Availability (CIA) ratings, to a proportional and lifecycle-aware set of Policy Enforcement Points (PEPs), such that the depth of governance applied scales with the asset's inherent risk profile rather than being applied uniformly?

Findings

(Populated from section 6 Synthesis above.)

Executive Summary

• A defensible PAP should compute a monotone function F(invariant set, CIA, lifecycle phase) -> PEP topology, where higher-risk metadata never maps to weaker control coverage and incomparable invariants combine by union rather than by averaging.

• Existing ABAC, XACML, and RAdAC material already supports dynamic authorization decisions, and the PAP-side lifecycle-topology derivation problem remains under-specified rather than directly named.

• For practical design, the minimal basis set is registration and classification, identity and delegation, development sandbox and connector boundary, delivery and promotion, runtime authorization, runtime rate-limit and exception routing, and evidence and stop-authority gates, with hard gates required at Getting Started and Operation for CIA-High, privileged, or write-capable agents.

• Proportionality is necessary because uniform gating both over-governs low-risk utilities and under-governs high-risk agents whose machine-speed execution amplifies permission misuse and removes human friction.

Key Findings

1. Existing ABAC and XACML models are already dynamic at authorization time because they evaluate subject, resource, action, and environment attributes through PAP, PDP, PEP, and PIP roles, and the reviewed material leaves lifecycle-topology selection as an implementor-side architectural inference rather than an explicit standards algorithm. Confidence: medium.
2. A defensible formalisation is a monotone partial order over invariant set and CIA label, because Denning-Sandhu style ordering and highest-triggered-tier logic fit this multi-dimensional risk problem better than either one linear risk score or a literal single-axis secrecy lattice. Confidence: medium.
3. Capability-based security supports deriving minimum PEP coverage from declared invariants because precise and minimal delegation is the right model for assets whose authority must stay bounded below both human and system maxima. Confidence: medium.
4. NIST SP 800-53 provides the component controls from which a proportional topology-selection rule can be built by combining attribute registration, dynamic privilege management, least privilege, dynamic attribute association, and per-request authorization. Confidence: medium.
5. The phase-distributed topology should reserve registration and identity gates for Getting Started, sandbox and connector gates for Development, promotion gates for Delivery, and authorization, rate, and stop-authority gates for Operation. Confidence: medium.
6. CIA-High, privileged, or write-capable agents require hard gates at Getting Started and Operation because identity scoping, rate controls, and runtime stop authority must exist before those agents can safely enter build or production states. Confidence: medium.
7. Uniform gate depth is economically and behaviorally unstable because it pushes low-risk utility demand toward workaround channels while failing to add the extra engineered safeguards that materially risky agents need. Confidence: medium.
8. A worked CIA-High agent that handles PII and executes financial transactions should never map below {G0,G1} at Getting Started, {G1,G2} in Development, {G1,G3} in Delivery, and {G1,G4,G5,G6} in Operation, because each phase exposes a distinct blast-radius mechanism. Confidence: medium.

Assumptions

• No standalone assumption entries are carried into Findings; the invariant taxonomy, gate basis set, and worked topology are explicitly labeled as inferences in this document rather than being presented as unsupported assumptions.

Analysis

• The strongest interpretive move in this item is separating decision dynamism from topology dynamism, because that avoids the false claim that modern access-control theory is static while still identifying an architectural gap worth solving.
• The lattice material was weighted as structural guidance rather than as a ready-made solution, because it directly supports ordering, joins, and monotonicity but does not decide which enterprise invariants matter operationally.
• Alternative formalisations were considered and rejected at a high level: a single linear score collapses incomparable hazards into one number, while a literal single-axis secrecy lattice does not fit mixed confidentiality, integrity, and operational-authority invariants as well as a partial-order with highest-triggered-tier logic.
• The capability literature was weighted as the derivation principle for invariant classes, because precise delegation and least authority explain why a PAP should read invariant declarations as claims about the minimum set of enforcement surfaces required.
• The repository's adjacent items were used to resolve the proportionality question, because they provide the operational consequence evidence missing from the formal models and explain why uniform gating is both behaviorally brittle and technically insufficient.
• The resulting mapping rule is therefore best read as an implementor's design specification built from standards-compatible control primitives rather than as a claim that one standards body already publishes this exact formula.

Risks, Gaps, and Uncertainties

• No reviewed primary source explicitly publishes a PAP function from invariant metadata to lifecycle PEP topology, so the exact formula remains a synthesis rather than a directly sourced standard pattern.
• The lattice evidence is structurally strong, but the source used here is a concise teaching summary rather than the original Denning or Bell-LaPadula papers, so the formalism claim is high-confidence for ordering logic and medium-confidence for any stronger historical reading.
• The capability source is strong on least-authority delegation, but it does not discuss lifecycle phase design, so the jump from delegation theory to phase-distributed topology remains inferential.
• The empirical case is strongest for why uniform control patterns fail and weaker for any exact threshold where a soft gate should become a hard gate.

Open Questions

• How should the PAP encode joins between incomparable invariants when one asset spans regulated data, financial transactions, and privileged configuration change in the same workflow?
• What evidentiary thresholds should automatically reclassify an asset from soft-gated to hard-gated operation after deployment drift, connector growth, or new data exposure?
• Which downstream runtime patterns, transaction signing, supervisory approval, or anomaly-triggered suspension, best implement the G4-G6 operational topology for the highest-risk assets?

Output

• Type: knowledge.
• Description: a standards-compatible formal mapping from invariant metadata and CIA rating to lifecycle-aware enforcement topology, plus a worked high-risk example and PAP design criteria.
• Links: National Institute of Standards and Technology (NIST) Special Publication (SP) 800-162, Guide to Attribute Based Access Control (ABAC) ; OASIS eXtensible Access Control Markup Language (XACML) 3.0 core specification ; NIST SP 800-53 control extracts, AC-2

sources

• [x] National Institute of Standards and Technology (NIST) Special Publication (SP) 800-162, Guide to Attribute Based Access Control (ABAC) — - primary ABAC definition and current baseline for dynamic authorization logic
• [x] NIST SP 800-53 Rev. 5, Security and Privacy Controls for Information Systems and Organizations — - primary control catalog page for proportional-control context
• [x] NIST SP 800-53 control extracts, AC-2 — - primary account-attribute, dynamic privilege, and dynamic account-management text
• [x] NIST SP 800-53 control extracts, AC-3 — - primary access-enforcement and ABAC text
• [x] NIST SP 800-53 control extracts, AC-6 — - primary least-privilege text for users and processes acting on behalf of users
• [x] NIST SP 800-53 control extracts, AC-16 — - primary attribute-association and dynamic-attribute text
• [x] NIST SP 800-53 control extracts, AC-24 — - primary per-request authorization-decision text
• [x] NIST SP 800-207, Zero Trust Architecture (ZTA) — - primary dynamic authorization and per-session least-privilege context
• [x] NIST glossary entry, Risk-Adaptive Access Control (RAdAC) — - primary definition of risk-adaptive access control
• [x] OASIS eXtensible Access Control Markup Language (XACML) 3.0 core specification — - primary definition of PAP, PDP, PEP, PIP, attributes, obligations, and decision context
• [x] Ravi Sandhu, Lattice-Based Access Control Models — - secondary but technically direct summary of Denning axioms, partial orders, least upper bound, Bell-LaPadula, Biba, and dynamic labels
• [x] Miller, Yee, and Shapiro, Capability Myths Demolished — - secondary but technically direct source on least-privilege delegation, confused deputy avoidance, and capability precision
• [x] Aligned Decision-Making: Context Architecture for AI Agents in Organisations — - prior completed item defining the eight-layer organisational context model
• [x] Adaptive Policy-Based Authorization (APBA): compliance alignment with NIST SP 800-53 and ISO/IEC 27001 — - prior completed item closest to current adaptive-policy analogue
• [x] Access control amplification under agentic operations — - prior completed item on worst-case permission inheritance
• [x] Implicit rate-limiting controls removed by agentic AI — - prior completed item on the loss of human friction
• [x] Regulatory and standards preconditions for deployment of AI systems that can take multi-step actions — - prior completed item on when foundational weaknesses become control failures
• [x] Systems capability debt as the root cause of citizen development: empirical evidence and effective governance architectures — - prior completed empirical grounding for workaround demand and uniform-control failure
• [x] What identity and access management model is required for AI agents and low-code artefacts operating within enterprise systems? — - prior completed item on machine identity and bounded delegation
• [x] Deployment pipeline as the only enforceable control gate for citizen-developed agents — - prior completed item on the Delivery-phase enforcement surface
• [x] How should Artificial Intelligence (AI) and low-code use cases be classified into risk tiers, and how should governance controls vary across those tiers? — - prior completed item on highest-triggered-tier logic and proportional control depth