All lessons Leer en español

Security in depth · Unit 25 · Lesson 4 of 12

Responsibility follows the service model

Use a migration record to assign database security work without leaving an ownership gap.

3 minreadyShort lesson

Helpful before thisCloud identity

See all lessons in this topic

After this lesson you can

  • Assign provider operations and customer decisions from a specific service record.

Follow one database as its operating model changes.

Read the service boundary

A service model describes which parts of a cloud system the provider operates and which parts the customer controls. Infrastructure as a service usually leaves guest operating-system work with the customer; a managed platform can transfer that work. Software as a service supplies a finished application, while customer account and data decisions remain.

These categories orient a review. The specific product, configuration, and agreement determine the actual handover.

Service model → Responsibility split → Customer controlsService modelResponsibility splitCustomer controls
The model guides the responsibility split; the service record identifies the controls that still need customer owners.

Harbor Library’s migration record

C1: The selected managed database service operates its host OS and backup mechanism. The customer selects database permissions and backup retention.

C2: The library approves two catalog editors, requires 14 days of recoverable backups, and has not yet assigned a retention owner.

Assume C1 accurately describes the purchased service and C2 is the approved requirement. No additional operations contract transfers the customer’s work.

The provider owns host maintenance under C1. The library must name an access owner and a retention owner. “Backups are automatic” describes a mechanism; it does not show that the chosen retention meets 14 days or that a useful restoration is possible.

Write three handover rows: responsibility, accountable owner, and acceptance evidence. A useful model pairs access with a reviewed editor list, retention with the selected setting and a restoration record, and provider maintenance with the documented service commitment.

If the service cannot meet C2, record a design gap before migration approval. Do not silently replace the requirement with the default. The handover records intended ownership; delivered maintenance and recovery still need their own service evidence.

Check yourself

No timer. No penalties. Read the explanation and try again whenever you like.

  1. Which handover matches Harbor Library’s supplied service record?

    Show the answer

    Correct answer: Assign OS maintenance to the provider and access and retention decisions to named library owners. This follows C1’s division of work and C2’s business requirements. Each customer decision still needs configuration and acceptance evidence.

Try it

  • WriteWrite a three-row handover for OS maintenance, database access, and backup retention. Name an owner, cite C1 or C2, and state the acceptance evidence needed before migration closes.
References