Security Architecture Review Checklist
A practical checklist for reviewing solution designs across identity, data, network, application, operations and supply chain, with Spring Boot and cloud implementation pointers.
Identity and access
- Users authenticate via the corporate IdP or CIAM (OIDC/SAML); MFA enforced for privileged and sensitive actions.
- Services use workload identity; no static keys.
- Authorization enforced server-side per object and function; tested.
- Least privilege for humans and services; admin access is just-in-time.
Data
- Data classified; PII inventory and retention defined.
- Encryption in transit (TLS 1.2+) and at rest (KMS); field-level encryption for restricted data.
- Secrets in a vault; rotation automated.
- Backups encrypted, immutable, restore-tested.
Network
- Private subnets for compute and data; no public databases.
- WAF and DDoS protection on public endpoints.
- Egress restricted; private endpoints to cloud services.
- Segmentation between environments and sensitivity zones.
Application
- Threat model done; OWASP Top 10 and API Top 10 controls addressed.
- Input validation, output encoding, parameterized queries.
- Rate limits and abuse protection on sensitive business flows.
- Security headers (CSP, HSTS, X-Content-Type-Options) for web apps.
Supply chain and pipeline
- SCA, SAST, secret scanning, container and IaC scanning in CI.
- Artifacts signed; SBOM produced; base images patched regularly.
- Protected branches, reviews, least-privilege CI credentials (OIDC federation to cloud).
Operations
- Security events logged and forwarded to SIEM; alerts for key detections.
- Incident response runbook and contacts; tested.
- Vulnerability patching SLAs by severity.
- Pen test before go-live for Tier 0/1 systems.
Spring Boot quick wins
server:
error:
include-stacktrace: never
include-message: never
management:
endpoints.web.exposure.include: health,prometheus # do not expose env, heapdump, etc.
endpoint.health.show-details: neverAdd security headers via Spring Security defaults (enabled), configure CORS with explicit origins, and keep dependencies current with Dependabot/Renovate.