Professor Franklin
Accessibility settings

Preferences are saved in this browser when storage is available.

Chapter 8 · Reading 1 of 5

Assigning responsibility in hybrid systems

Security+ SY0-801 · Objectives 3.1

The college moves its advising appointment system to a hosted platform. The first week, an advisor accidentally shares a calendar publicly. The provider reports that its infrastructure is healthy. The advisor reports a real disclosure. How can both accounts be true? They describe different parts of the same service.

Draw the management boundary before assigning a control. An on-premises team may own the power supply, hypervisor, operating system and application. An infrastructure service typically transfers facility and hardware responsibilities to a provider while the customer retains guest and access decisions. A managed application moves more maintenance to the provider, while tenant identities and data sharing still need an owner.

Responsibilities inside the service

Containers share a host kernel and require image provenance and runtime isolation. Serverless functions trade server administration for tightly scoped execution roles and dependency management. Infrastructure as code makes deployments repeatable but a template error can reach many environments. For each design, identify who patches each layer, who can inspect logs and who restores customer data.

Draw what the contract actually assigns

Start with a student's request and follow it through the identity service, application, database and hosting environment. For each layer, write the name of the team that configures it, the team that can see the evidence when it fails and the person who can authorize recovery. These may be three different people. A provider may operate the database while the customer decides which application identities may read it. The college may manage user accounts while relying on the provider to supply useful audit events.

Now compare two service purchases. Leasing a virtual machine leaves the guest operating system with the customer under a typical infrastructure arrangement. Buying a managed scheduling application can transfer patch responsibility for that application to the supplier. The customer still decides which advisors retain access after a transfer. Read the actual service description before making an assignment.

Who can produce the evidence?

The college and the supplier both say they monitor the service. During a tabletop, ask each to bring one actual kind of record to the meeting. The college may see that a user authenticated, while the supplier alone can show that an export job completed. Agree on a common transaction reference that both sides may retain. Without that link, two honest incident accounts can describe different requests.

Consider another boundary inside the college. The team paying the invoice may own the contract while a department administrator controls sharing settings. Giving the contract manager every incident ticket will not fix a setting they lack permission to change. Write down the operator who can make the change and the service owner who must approve it. The distinction becomes important at the end of the contract, when someone must revoke access and verify what happened to existing copies.

Find the gap during a tabletop

Give the operations team a hypothetical incident. Someone reports an unauthorized calendar export at 17:30. Who can obtain the audit record, how long is it retained and who can reach the provider outside business hours? If every person says another team owns that step, you have found a gap before an actual student is affected. Record the agreed owner, contact and evidence source. This responsibility drawing gives you the starting point for deciding where network controls belong.

Cloud responsibility stack

Inspect the three records, then use the evidence to answer the question.

1. Record A

Provider maintains physical facilities

2. Record B

Contract assigns guest OS patching to tenant

3. Record C

Workload runs on a leased virtual machine

Apply the reading

What evidence supports your decision in the cloud responsibility stack exercise?

Compare your reasoning

The contract places guest operating system maintenance with the tenant. Service abstractions move the boundary, so verify each service separately.