Cloud security and DevSecOps
AWS, GCP or Azure reviewed, put in Terraform, and security checks added to your pipeline. Four to eight weeks, delivered as pull requests.
What you get
- A written threat model, with findings ordered by attack chain rather than by severity label
- Your cloud in Terraform, console changes stopped except a documented break-glass path
- Access cut down to what each workload and person uses, with a review that keeps it that way
- Code, dependency, secret and infrastructure scanning as required checks in your pipeline, with the old findings baselined so nothing blocks the next merge
- Logging that answers an incident and an auditor: who did what, where, when
- Code fixes merged in your repositories
- A recorded session with your engineers on what changed
How it runs
Week one is read-only: inventory, threat model, the list. From week two the work arrives as pull requests your engineers review. The last week is handover.
If a buyer later asks for SOC 2 or ISO 27001, this is the engineering half of the implementation already done.
Send the questionnaire that asked for the diagram, or the scanner output that got switched off.
marius@keibisoft.com · Telegram · LinkedIn
Reply within 24 hours. All services · Lean Terraform · DevSecOps in CI/CD