Unit 1: How a cloud account is laid out · Lesson 4 of 5 · 15 min
Build an asset inventory
Sort resources by owner and data class to decide where the review starts.
mission
- You are
- Security engineer at Brightwell.
- Situation
- You exported what you found into an inventory. Your manager wants to know where the risk is concentrated before the full review.
- Goal
- Use the inventory to find the resources that hold personal data, face the internet or belong to nobody.
- Hand in
- The three resources you would review first, with a reason each.
Risk sits where sensitive data meets wide access. Sort the inventory by data class, then look at what is public and who owns it.
Filter by data class
Type learner-pii in the filter box. These resources hold names and emails covered by GDPR.
you should see Two buckets tagged learner-pii, one of them with no public access block.
Sort by exposure
Click the Public column header. Public resources are fine when they are meant to be, like a website.
you should see The website is public on purpose. One bucket of learner data is public by mistake.
Find the orphans
Switch to the Identities tab and sort by Last used. Accounts that nobody uses are access that nobody watches.
defender tip Every finding needs an owner. Resources without one end up in the backlog forever.
Write the review order
Pick three rows: the public learner export, the dev box with SSH open to the world and old.contractor. Next to each, write the data it holds and who owns it.
you should see Each pick pairs sensitive data or admin rights with wide exposure. That pairing is what puts it first.
What a defender takes away
- 1Rank by sensitivity times exposure, not by how many resources a team has.
- 2Tags for owner and data class turn an inventory into a work plan.
- 3Unused identities with keys are risk without benefit.
Questions
0 of 3 solved
Answer each one from what you find on your lab machine.