WikifitaGitHub live67e8de5
pesquisa · memorias/projetos/bairesdev_appsec_playbook/secure-sdlc

BairesDev AppSec — secure SDLC control plane

Phase-by-phase secure software lifecycle synthesized from BairesDev's public guidance.

Baixar raw

Secure SDLC control plane

The Secure Software Development Lifecycle for Distributed Teams is the most operationally specific source. Its thesis is that security failures in distributed delivery are operating-model failures caused by gaps in tooling, ownership and enforcement.

Phase controls

PhaseMinimum controlEvidenceFailure to prevent
Planningsecurity requirements, risk classification, asset/data inventoryapproved requirements and risk recordbuilding an insecure design into scope
Designthreat model, trust boundaries, abuse cases, architecture reviewmodel, decisions and accepted risksunexamined attack paths
Developmentsecure coding, peer review, SAST, SCA, secret scanningPR, scan results and remediationdefects and leaked credentials
Buildreproducible build, dependency validation, policy gatesbuild provenance and gate resulttampered or untraceable artifacts
TestDAST/IAST, API and authorization tests, regression teststest reports and triageruntime flaws escaping static checks
Deployapproval, IaC review, rollback plan, environment paritydeployment record and rollback owneruncontrolled production change
Operatemonitoring, vulnerability intake, incident response, patch SLAsalerts, tickets, postmortemspersistent exposure and slow recovery

Ownership model

Every finding needs an owner, severity, due date and escalation path. Every exception needs an approver, rationale, expiry and compensating control. Every rollback needs a named decision-maker. The blog's strongest insight is that an unowned finding is an architectural defect in the process.

Distributed-team design rules

  • Use shared CI/CD templates instead of team-specific security folklore.
  • Standardize minimum controls but allow risk-based extensions.
  • Put remediation and rollback ownership in the RACI.
  • Track control coverage and remediation time across teams.
  • Make the secure path the easiest path.

Cross-links

See Testing and verification stack for control capabilities and Governance and metrics for measurement and exception handling.