• Irreversible Decisions
    • Constraints First
    • Coupling and Cohesion in Practice
    • Trade-off Sliders
    • The Boring Baseline
    • Monolith First, Split on Evidence
    • Service Boundaries That Survive Reorgs
    • Synchronous vs Asynchronous Integration
    • API Contracts and Versioning
    • Idempotency and Retries
    • Choosing a Datastore Without Regret
    • Schema Migrations Without Downtime
    • Consistency Models You Actually Need
    • Caching: The Four Questions
    • Event Sourcing and CDC: When It Pays
    • Trunk-Based Development and Branch Reality
    • Pipeline Design: Fast Feedback, Slow Gates
    • Progressive Delivery
    • Build Reproducibility and Artifact Promotion
    • Rollback Is a Feature
    • Kubernetes: What You Sign Up For
    • Infrastructure as Code That Doesn't Drift
    • Environments, Config, and Secrets
    • Multi-Tenancy and Cost Boundaries
    • The Internal Platform as a Product
    • SLOs, Error Budgets, and Saying No
    • Observability: What to Actually Wire
    • Capacity, Load Shedding, and Backpressure
    • Failure Modes: Timeouts, Breakers, Bulkheads
    • Incident Response and Blameless Postmortems
    • Threat Modeling in One Hour
    • Identity, Authentication, Authorisation
    • Secrets and Key Management
    • Supply Chain: Dependencies, SBOM, Signing
    • Least Privilege and Auditability
    • Architecture Decision Records That Get Read
    • Diagrams That Age Well
    • Runbooks and On-Call Docs
    • Design Reviews and RFCs
    • Building a Team Architecture Memory
    • GitHub
  • to navigate
  • to select
  • to close
    • Home
    • Security by Design
    On this page
    shield

    Security by Design

    The parts you cannot bolt on afterwards: threat models, identity boundaries, secrets, supply chain, and least privilege.

    policy

    Threat Modeling in One Hour

    Four questions, a whiteboard, and the people who built it. Skip the formal methodology; keep the habit.

    fingerprint

    Identity, Authentication, Authorisation

    Authentication is who you are. Authorisation is what you may do. Most breaches are failures of the second one.

    vpn_key

    Secrets and Key Management

    The best secret is the one that does not exist. Failing that, make it short-lived and rotatable without a deploy.

    inventory

    Supply Chain: Dependencies, SBOM, Signing

    Most of your code was written by strangers. The question is what you know about it and what it can reach.

    admin_panel_settings

    Least Privilege and Auditability

    Design so that a compromised component reaches almost nothing, and so that you can prove what happened.


    © 2026 Architecture Field Notes. Built with Lotus Docs