IntermediateGoogle Cloud Security Operations Engineer project · about 12 hours

Foundation security controls for Google Security Operations

Set up identity, policy and data controls the way a security engineer would on day one.

The real-world brief

A fintech is starting on Google Cloud and wants security built in from the start.

What you will build

  • Least-privilege access
  • Guardrail policies
  • Protected sensitive data
  • A controls document

Skills you will practise

Identity and accessPolicy guardrailsData protectionDocumentation

Tools

Google SecOps SIEMYARA-L rulesUDM searchLog ingestion

Project tasks

The detailed steps, checklists and trainer review open in the SOTT student portal for enrolled students.

1Access Steps in portal
2Guardrails Steps in portal
3Data Steps in portal
4Document Steps in portal

How companies use Google Cloud Security Operations Engineer

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.

Questions

Can I add the Foundation security controls for Google Security Operations project to my resume?

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.

How long does this project take?

About 12 hours of hands-on work, and it fits best after week 4 of the Google Cloud Security Operations Engineer (Google SecOps) course.

Where do I get the step-by-step tasks?

Enrolled students get every task with steps, "done when" checks, the submission form and a trainer review in the SOTT student portal.