security-permissiveness-spans-policy-and-data-boundaries

Status: OUT

Security permissiveness is systematic across two independent dimensions: policy enforcement (default-allow access control, trusted internal callers, no input validation) and data isolation (BCC recipients stored alongside visible recipients, presigned URL secrets shared across instances), creating a consistent availability-over-security bias that compounds — permissive policies let requests through, and weak data isolation lets those requests see more than intended.

Justifications

Access control gaps and data isolation gaps are parallel manifestations of the same permissive default

Depends on (SL): data-isolation-gaps-parallel-access-control-gaps, default-to-permissive-across-security-dimensions

JSON