DevSecOps

Gated DevSecOps Pipeline

Commit to production on one gated path: static checks, scanned images, GitOps deploys, an approval gate and watched runtime.

A pull request starts the pipeline. Code quality, SAST and dependency checks run first, then the image is scanned, signed and stored. Argo CD deploys each environment from its config repo; DAST runs on staging, a person approves production, and runtime is watched from day one.

webhookfindings in the PRsigned imagenew tagsynclogs · metricsfindingsCommitBuild · static checksPackage · scanDeploy · GitOpsAWS CloudOperate · observe and protectDeveloperIDE plug-insPre-commit hookssecrets · unsafe codeGit repositorypull requestAWS CodePipelineor GitLab CI · JenkinsHashiCorp Vaultpipeline secretsSonarQubequality · SASTSnykopen source (SCA)Trivyimage scan · SBOMAmazon ECRsigned imagesAmazon Inspectorre-scans stored imagesConfig repoone folder per envArgo CDGitOps syncAWS Config & SCPscompliance as codeAmazon EKSdev · stagingOWASP ZAPDASTApproval gaterelease ownerAmazon EKSproductionAWS Secrets Managerapp secretsAWS Security Hubfindings per teamPrometheuscluster metricsGrafanadashboardsAmazon CloudWatchlogs · alarmsAmazon GuardDutyruntime threats

Point at a component to light its links; select it for what it does here and the practice that makes it right on AWS.

When to use it

  • Teams ship through hand-built pipelines and security checks come at the end
  • An audit needs evidence of every check, approval and deployment
  • Several teams should share one standard path instead of each building their own

How NGT delivers it

Built from code, reviewed at a gate by an NGT architect, and handed over with runbooks your team can run.

DevSecOps