RWS Architecture article

Security by Design

Security controls are embedded into architecture, automation, and operations from the start.

  1. Typeprinciple
  2. Statusactive
  3. Domain60-principles
On this page
  1. Principle – Security by Design
  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 – Security by Design

Summary

Security controls are embedded into architecture, automation, and operations from the start.

Intent

Reduce systemic risk and avoid retrofitting security controls late in delivery cycles.

Scope and Applicability

Applies to identity, access control, network boundaries, data handling, and platform services.

Principles

  • Shift security controls left into design and automation pipelines.
  • Use policy-as-code and enforce security baselines by default.
  • Make security posture visible and auditable.

Per-Domain Implementation

OpenShift

  • Enforce cluster security baselines and admission policies by default.

Networking

  • Apply segmentation, encryption, and boundary controls as standard patterns.

Storage

  • Protect data at rest and in transit with validated policies.

Security

  • Provide consistent IAM, certificate, and policy management services.

Platform

  • Integrate security validation into platform delivery workflows.

AI

  • Apply security controls to AI workloads and data (datasets, model artifacts, and inference endpoints) as part of the standard platform baseline.

Exceptions

Exceptions require explicit risk acceptance and a remediation timeline.