Compliance, vulnerability management and the bigger picture
Vulnerability management lifecycle
Discover (scanners across code, images, hosts, cloud) → prioritise (severity, exploitability, exposure, asset criticality) → remediate (patch, upgrade, rebuild, mitigate with config/WAF) → verify (re-scan) → report (SLA compliance, trends). Running workloads must be re-scanned continuously — an image clean at build time can have new CVEs next week.
Example: Log4Shell-style response
- Identify exposure fast: query SBOMs / image scans for the vulnerable library across all running images.
- Mitigate immediately where possible: WAF rules, configuration flags, network egress restrictions.
- Patch: bump the dependency, rebuild, redeploy via the normal pipeline (fast because builds are automated).
- Verify with scans; hunt for exploitation in logs (GuardDuty, WAF, app logs).
- Postmortem: how fast could we answer "where are we vulnerable?" — improve SBOM coverage.
Compliance as code
Frameworks you'll hear in India-based product companies and BFSI: ISO 27001, SOC 2, PCI DSS (payments), RBI guidelines for regulated entities, India's DPDP Act for personal data. DevOps contributes evidence automatically: IaC with policy checks, CloudTrail/Config history, access reviews, change approvals in Git, vulnerability SLAs, encryption everywhere, audit logs retained immutably.
Threat modelling (lightweight)
For a new service: draw the data flow, list trust boundaries, use STRIDE (Spoofing, Tampering, Repudiation, Information disclosure, Denial of service, Elevation of privilege) to find threats, and map mitigations (authN/Z, TLS/mTLS, input validation, rate limits, logging, least privilege).