Cybersecurity Cloud Security and Shared Responsibility

How it works

Cloud services divide responsibilities between provider and customer, and that division varies by service. A managed database may remove operating-system patching from the customer’s work while leaving identities, exposure, data access and backup choices with them. Review the actual service contract rather than a generic cloud diagram. Public storage access deserves a deliberate business decision. Review how an administrator loses access when leaving the team, including access through inherited groups and emergency accounts.

Work through the example

This is a worked design or investigation exercise. Read the fixture, write your own decision, then compare it with the worked result. No live system, external account or attack is executed by this listing.

Download the complete exercise

Example

Service: managed lending database
Provider concern: managed platform operation under its documented service model
Customer concern: identities, network access, data classification and recovery configuration
Evidence: deny anonymous access; test least-privileged application account; restore an isolated backup
Boundary: no cloud account or live provider change in this exercise

Expected result

The customer retains concrete checks even when infrastructure is managed.

The provider’s responsibilities depend on the product, so verify its current documentation before assigning tasks. A successful login with an administrator account says little about the application account’s privileges. Security and cost monitoring should have owners before deployment.