Set up identity, policy and data controls the way a security engineer would on day one.
A fintech is starting on Google Cloud and wants security built in from the start.
The detailed steps, checklists and trainer review open in the SOTT student portal for enrolled students.
Banking: Stopping account takeover. Attackers used stolen passwords to sign in. MFA, Conditional Access and alerts on risky sign-ins. Takeovers stopped.
Hospital: Catching ransomware early. Ransomware spread before anyone noticed. Endpoint detection, SIEM rules and isolation playbooks. A drill showed attacks contained early.
Retail: Protecting customer data. Card and personal data sat in unknown places. Data discovery, labels, encryption and loss prevention. Sensitive data is known and protected.
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 12 hours of hands-on work, and it fits best after week 4 of the Google Cloud Security Operations Engineer (Google SecOps) course.
Enrolled students get every task with steps, "done when" checks, the submission form and a trainer review in the SOTT student portal.