Portfolio practice / 3 MIN READ
Map cloud responsibilities before asking who has the evidence
A fictional GRC case separates provider platform duties, customer sharing settings and evidence of actual use.
On this page
A provider's security statement does not answer every question about a customer's use of its service. First identify the specific responsibility, then ask which record can support the conclusion.
The AWS shared-responsibility explanation distinguishes provider and customer duties and emphasizes that the boundary depends on the services and use case. It is background for this original fictional exercise, not evidence about the invented service below or a universal assignment for every cloud product.
Read the fictional packet
Lumen Planning uses invented document service Cedar Share. The exercise's responsibility sheet assigns platform patching to Cedar and external-link configuration to Lumen. Lumen's fictional rule requires external links to name recipients and expire within seven days. These are supplied teaching criteria, not a legal or certification requirement.
The packet includes a provider statement about its platform-patching process, a dated tenant-settings export showing a fourteen-day default expiry, and three external-sharing records. Two records name recipients and expire in seven days. The third is a public link expiring in fourteen days.
| Question | Responsible party in this packet | Relevant evidence and limit |
|---|---|---|
| Who manages platform patches? | Cedar | Responsibility sheet assigns the duty; the statement describes a process, not a completed assessment |
| What default has Lumen configured? | Lumen | Tenant export shows fourteen days at the captured time |
| Did the three supplied links meet Lumen's rule? | Lumen | Two match; the public fourteen-day link does not |
| Did all external links meet the rule throughout the period? | Unresolved | Three records do not establish the complete population or period coverage |
Neither the provider statement nor two matching links resolves the third record. Conversely, the third record does not prove that Cedar failed to patch its platform. Those are different responsibilities and evidence questions.
Write the limited conclusion
Try: “The supplied responsibility sheet assigns external-link configuration to Lumen. The settings export shows a fourteen-day default, which does not align with the seven-day teaching criterion. One of three supplied links is public and expires in fourteen days; the other two meet the stated recipient and expiry conditions. Request the relevant sharing population and configuration history before drawing a period-wide conclusion. Platform-patching effectiveness is not established by this packet.”
The export and link records also answer different questions. A current default does not necessarily establish how every past link was created. A corrected default alone would not demonstrate that an existing public link had been removed or changed.
Revise only what new evidence resolves
Add a later settings export with a seven-day default. Update the current-configuration observation, retain the earlier mismatch and leave the third link's disposition unresolved until linked evidence addresses it. Do not turn one corrected setting into a claim that the whole service is secure.
Keep the responsibility matrix, record identifiers and both note versions clearly fictional. Compare cloud-responsibility preparation resources, or use the vendor-risk case for the separate question of defining a proposed service's scope.
PUT IT INTO PRACTICE
Risk & Evidence Portfolio Kit
Connect the individual document to a complete fictional case, with registers and a versioned decision memo.