principle of least privilege

The. (1975). principle of least privilege.

Retired. This entry was not a citation. Our extractor stored an inline prose definition from the article as though it were a bibliographic record, so its title is the name of a concept rather than of a published work. The page is kept because links to it still resolve, but it is withdrawn from the reference list. This entry is kept so the citations that pointed at it still resolve, and so the correction is visible rather than silent.

Type

Unclassified

Intellectual base

Unclassified

Year

1975

Link

no authoritative link yet

Cited by

7 citations across 7 artifacts.

Each citation links to the sentence it supports in the citing article.

Mechanisms

• Access Control or Permissioning
  • This keeps the blast radius of any one compromised or mistaken actor small.
• Permission Scope or Capability Token
  • Its strength is a hard, enforced cap on blast radius: an unauthorized surface stays untouched even when the acting code is buggy, compromised, or an over-eager automated agent.
• Permission-Scoped Default
  • This is the principle of least privilege
• Privilege Scope Restriction
  • The principle behind it is least privilege — during impairment, no actor should retain more power than the immediate, defensible need.
• Sandbox or Adapter Wrapper
  • The SDK runs with least privilege; its network calls go through an adapter that strips identifiers before anything leaves the device; its callbacks are validated at the boundary rather than trusted.
• Service Account or Bot Delegate
  • Least-privilege scoping is the animating safeguard, but privilege creep and secret sprawl erode it silently.

    This sourceService accounts are where the principle is most often violated in practice — through privilege creep and unrotated secrets — which is why their design is dominated by scoping and lifecycle rather than by interface or negotiation.

• Template or Policy Origin Audit
  • The mismatch jumps out: a wildcard `Action: "*"` grant that was a reasonable convenience in a throwaway sandbox is now sweeping over-privilege on roles that touch production.

    This sourceIt is used here as the criterion the probe measures a permissive default against, not as a citation for any specific finding.

Verification

This reference passed the adversarial substantiation pipeline: it was checked to exist and to support the claim it is attached to. See how references were verified.

Registry ID ref:36e0775c9925 · see in the full table