Building Secure and Reliable Systems

book work id

book-work-BATCH-2026-002-005

title

Building Secure and Reliable Systems

subtitle

Best Practices for Designing, Implementing, and Maintaining Systems

alternate titles

authors

person-BATCH-2026-002-019, person-BATCH-2026-002-020, person-BATCH-2026-002-021, person-BATCH-2026-002-022, person-BATCH-2026-002-023, person-BATCH-2026-002-024

contributors

original language

lang-en

first publication date

2020-04-08

work type

collaborative_technical_book

topics

governed-agent-identities, identity-and-access-management

central subjects

least privilege, secure and reliable system design, authorization policy, audit and incident response

inclusion rationale

Official complete text covers least privilege, policy, access, audit, and responsibility; these are directly useful foundations for governed agents.

analysis depth

deeply_analyzed

analysis basis

Complete official Google-hosted first-edition HTML reviewed across all 35 front-matter, part, chapter, appendix, and back-matter files

central thesis

Security and reliability are mutually reinforcing, emergent properties that must be designed, implemented, tested, operated, and governed together across the system lifecycle rather than added by a specialist team at the end.

principal propositions

proposition-candidate-BATCH-2026-003-009, proposition-candidate-BATCH-2026-003-010, proposition-candidate-BATCH-2026-003-011, proposition-candidate-BATCH-2026-003-012, proposition-candidate-BATCH-2026-003-013, proposition-candidate-BATCH-2026-003-014, proposition-candidate-BATCH-2026-003-015, proposition-candidate-BATCH-2026-003-016

frameworks

[object Object], [object Object], [object Object], [object Object], [object Object]

evidence base

Multi-author practitioner synthesis grounded in Google and industry operating experience, technical examples, case studies, incident narratives, analogies, and recommendations. It is not a controlled study and largely reflects large-technology-company conditions.

executive role implications

{"CISO":"Translate adversary models into contextual authorization, multi-party controls, audit evidence, and incident practice.","CIO":"Integrate security and reliability into platform standards, change systems, procurement, staffing, and disaster exercises.","CTO":"Design understandable interfaces, bounded failure domains, provenance gates, safe defaults, and recovery paths.","General Counsel":"Set privacy-aware logging, retention, investigation, disclosure, and evidence-handling requirements.","CEO":"Shape incentives and sustainable resourcing so production pressure does not externalize security and reliability risk.","Board Director":"Treat systemic access, supply-chain, recovery, and cultural risk as governance matters, not just technical metrics."}

strongest documented arguments

Least privilege becomes operational when access is classified by impact and exposed through narrow, auditable functions., Deployment confidence depends on verified artifacts and provenance, not merely trusted people or code-review events., Recovery capability is a designed and rehearsed property, not a document presumed to work during a crisis.

limitations

Many recommendations reflect Google's scale, staffing, engineering maturity, and ability to build custom control planes., The chapter evidence is primarily practitioner experience rather than externally replicated causal analysis., The book predates modern general-purpose AI agents and does not define sponsor, delegation, session, model, tool-purpose, or decision-provenance identity fields., Privacy, legal process, and geography are acknowledged but not developed into jurisdiction-specific operating models.

counterpoints

Smaller organizations may need managed services and fewer control layers because the full operating model can exceed their resources., Immutable logging can conflict with data minimization, correction, deletion, and cross-border obligations unless governance is designed with counsel., Identity and provenance controls still require trustworthy verification, policy, and runtime enforcement; attestations alone do not prove safe behavior.

later author interview source ids

later-author-source-BATCH-2026-003-004, later-author-source-BATCH-2026-003-005, later-author-source-BATCH-2026-003-006

related book work ids

related report ids

counter-source-BATCH-2026-003-004, counter-source-BATCH-2026-003-005, counter-source-BATCH-2026-003-006

changes in later statements

Later author commentary expands zero-trust practice toward data-layer controls, activity metadata, peer review, and justified access., Post-SolarWinds author commentary strengthens the book's artifact-provenance argument into an ecosystem supply-chain priority., Later SRE commentary describes the field as evolving and points readers to a continuing compendium rather than treating the 2020 text as final.

edition ids

book-edition-BATCH-2026-002-007, book-edition-BATCH-2026-002-008, book-edition-BATCH-2026-002-009

related source ids

source-BATCH-2026-003-002

related statement ids

statement-BATCH-2026-003-019, statement-BATCH-2026-003-020, statement-BATCH-2026-003-021, statement-BATCH-2026-003-022, statement-BATCH-2026-003-023, statement-BATCH-2026-003-024, statement-BATCH-2026-003-025, statement-BATCH-2026-003-026, statement-BATCH-2026-003-027, statement-BATCH-2026-003-028, statement-BATCH-2026-003-029, statement-BATCH-2026-003-030, statement-BATCH-2026-003-031, statement-BATCH-2026-003-032, statement-BATCH-2026-003-033, statement-BATCH-2026-003-034, statement-BATCH-2026-003-035, statement-BATCH-2026-003-036

related proposition ids

proposition-candidate-BATCH-2026-003-009, proposition-candidate-BATCH-2026-003-010, proposition-candidate-BATCH-2026-003-011, proposition-candidate-BATCH-2026-003-012, proposition-candidate-BATCH-2026-003-013, proposition-candidate-BATCH-2026-003-014, proposition-candidate-BATCH-2026-003-015, proposition-candidate-BATCH-2026-003-016

related dossier ids

rights notes

Official complete HTML was lawfully accessible for research. No open republication license was identified; this batch stores metadata, links, original analysis, and no direct quotations.

review status

deep_analysis_complete_machine_reviewed

publication status

published

workflow status

published

machine review status

ready_for_human_review

human review status

approved

reviewed by

Murray Newlands

reviewed at

2026-08-16T23:17:22Z

{
  "provenance": [
    {
      "source_url": "https://google.github.io/building-secure-and-reliable-systems/",
      "accessed_at": "2026-08-15",
      "retrieval_method": "Official publisher, project, or author-hosted bibliographic page inspected through public web access",
      "exact_locator": "Official work page and bibliographic metadata",
      "content_hash": null,
      "batch_id": "BATCH-2026-002",
      "prompt_id": "OEII-BOOK-METADATA",
      "prompt_version": "2.0",
      "notes": "Accepted discovery candidate candidate-BATCH-2026-001-099."
    },
    {
      "source_url": "https://google.github.io/building-secure-and-reliable-systems/",
      "accessed_at": "2026-08-15",
      "retrieval_method": "Complete exact edition retrieved from an official public source and reviewed in full",
      "exact_locator": "All 35 official HTML content files; stable chapter and section anchors",
      "content_hash": "6bf5050c08be0bced81767ac14bd9b3303e34b3efb667806b3c9e9d6b0ed8cf1",
      "batch_id": "BATCH-2026-003",
      "prompt_id": "OEII-BOOK-DEEP-ANALYSIS",
      "prompt_version": "2.0",
      "notes": "Manifest hash ae702b4e64364217f179317b4a46de6a5e7c51045a79efa67522245d76667e16; whole-edition analysis; no human approval granted"
    }
  ],
  "revision_history": [
    {
      "changed_at": "2026-08-15T00:00:00Z",
      "changed_by": "OEII analysis agent",
      "summary": "Advanced from catalogued metadata to complete-edition deep analysis.",
      "batch_id": "BATCH-2026-003"
    },
    {
      "changed_at": "2026-08-16T23:17:22Z",
      "changed_by": "Murray Newlands",
      "summary": "Approved for the governed-identities pilot release under the exact scope, exclusions, rights treatment, and limitations recorded in issue #18.",
      "batch_id": "BATCH-2026-003"
    }
  ]
}