Is the S in SRE for "Security"?#

John Benninghoff, Security Differently — Adjacent

• Why: A structured argument for the operational and organizational overlap between SRE and security practice (patching/attack-surface management, observability, incident response, postmortems) — useful framing for anyone trying to align SRE and security teams.
• What: An argument that SRE and Security teams share enough operational DNA (attack-surface management, observability, incident response, testing) that organizations most effectively reduce cybersecurity risk by improving general technology/operational performance rather than treating security as a separate discipline. (from abstract only)
• How: Draws on safety-science and DevOps research linking organizational performance across development, operations, SRE, and security; proposes Security Level Objectives as an SLO-style mechanism for prioritizing security work. (from abstract only)
• Where applicable: General organizational-design question for any org with separate SRE and security functions.