Knowing What You Run in the Cloud

Try it out loud first. Then check yourself:

1. You cannot secure what you do not know exists: forgotten accounts, regions and test resources are common entry points.
2. Use the provider's inventory tools (AWS Config, Azure Resource Graph, Google Cloud Asset Inventory) across every account.
3. Require tags for owner, environment and data sensitivity, so every finding can be routed to someone who can fix it.
4. Watch for drift: new accounts, unused regions suddenly active, and resources nobody owns.

If the interviewer pushes back

• A security scan finds 300 resources with no owner tag. What do you do with them?

Go deeper

• docs.aws.amazon.com/config/latest/developerguide/WhatIsConfig.html