RWS Architecture article

Least Privilege

Access is granted only to the minimum scope required for a task and is reviewed regularly.

  1. Typeprinciple
  2. Statusactive
  3. Domain60-principles
On this page
  1. Principle – Least Privilege
  2. Summary
  3. Intent
  4. Scope and Applicability
  5. Principles
  6. Per-Domain Implementation
  7. OpenShift
  8. Networking
  9. Storage
  10. Security
  11. Platform
  12. AI

Principle – Least Privilege

Summary

Access is granted only to the minimum scope required for a task and is reviewed regularly.

Intent

Reduce blast radius and prevent privilege escalation across shared services and workloads.

Scope and Applicability

Applies to user access, service accounts, automation roles, and administrative tooling.

Principles

  • Default to deny and grant access explicitly.
  • Prefer role-based access tied to identity and audit requirements.
  • Review and revoke elevated access on a scheduled cadence.

Per-Domain Implementation

OpenShift

  • Use scoped RBAC roles and avoid cluster-admin access outside controlled workflows.

Networking

  • Restrict configuration privileges and automate access approval paths.

Storage

  • Limit administrative access to storage backends and enforce separation of duties.

Security

  • Maintain clear entitlement boundaries and audit trails for privilege changes.

Platform

  • Provide standardized access patterns via IAM and service request workflows.

AI

  • Restrict access to training data, model artifacts, and inference endpoints; separate builder/deployer roles and minimize service account permissions.

Exceptions

Temporary access elevation must be time-bound, documented, and audited.