Assess an account against CIS, fix the top risks, automate checks and report to management.
A fintech must show regulators a working cloud security programme with measurable progress.
The detailed steps, checklists and trainer review open in the SOTT student portal for enrolled students.
Startup: Public storage bucket. Customer files were exposed through a storage bucket set to public. Block-public-access settings, policy guardrails and continuous posture checks. Public buckets are now impossible to create in the company accounts.
Fintech: Too many admins. Half the engineers had full admin rights in production. Single sign-on, roles per job, just-in-time admin access and access reviews. Standing admin access dropped to a handful of break-glass accounts.
SaaS: Unnoticed crypto-mining. Stolen keys were used to start large instances for mining. GuardDuty or Defender alerts, budget alerts and automated response that stops the instances. A similar attempt was stopped within minutes.
Yes. Once your trainer approves it, list it under Projects with the tools you used, one line on the problem it solves and a link to your repository and demo video.
About 16 hours of hands-on work, and it fits best after week 6 of the Cybersecurity in Cloud course.
Enrolled students get every task with steps, "done when" checks, the submission form and a trainer review in the SOTT student portal.