• Home
  • BVSSH
  • Engineering Enablement
  • Playbooks
  • Frameworks
  • Good Reads
Search

What are you looking for?

Standard : Access design is reviewed whenever system boundaries change

Purpose and Strategic Importance

This standard ensures access control is reviewed whenever system boundaries change, maintaining secure-by-design principles as systems evolve. It helps teams proactively manage risk and uphold least-privilege access.

Aligned to our "Zero Trust Architecture" policy, this standard reduces the likelihood of unauthorised access and strengthens system resilience. Without it, access models drift, vulnerabilities grow, and trust is compromised.

Strategic Impact

  • Improved consistency and quality across teams
  • Reduced operational friction and delivery risks
  • Stronger ownership and autonomy in technical decision-making
  • More inclusive and sustainable engineering culture

Risks of Not Having This Standard

  • Slower time-to-value and increased rework
  • Accumulation of inconsistency and process debt
  • Reduced trust in engineering data, systems, or ownership
  • Loss of agility in the face of change or failure

CMMI Maturity Model

  • Level 1 – Initial: Access controls are rarely reviewed during system changes. Boundary shifts often result in overly broad or outdated permissions, introducing significant risk.

  • Level 2 – Managed: Some teams review access controls during major system changes, but it’s inconsistent and not part of formal change management or governance.

  • Level 3 – Defined: Access reviews are triggered as part of a defined process whenever system boundaries change. Teams apply least-privilege principles and document access decisions.

  • Level 4 – Quantitatively Managed: Reviews are audited and tracked for completion and coverage. Metrics on access scope, orphaned accounts, or permission drift inform remediation efforts.

  • Level 5 – Optimising: Access reviews are integrated into continuous compliance and architectural workflows. Automated tools surface violations, and feedback loops strengthen Zero Trust maturity across environments.


Key Measures

  • Adoption rates and coverage across teams
  • Impact on delivery metrics, quality, or team health
  • Evidence of ownership, governance, or learning loops
Associated Policies
  • Architect for Change
  • Secure by Design
Associated Practices
  • CQRS (Command Query Responsibility Segregation)
  • Contract Testing
  • End-to-End (E2E) Testing
Associated Measures
  • Compliance Coverage

Technical debt is like junk food - easy now, painful later.

Awesome Blogs
  • LinkedIn Engineering
  • Github Engineering
  • Uber Engineering
  • Code as Craft
  • Medium.engineering