Moving to the cloud does not transfer every responsibility
A fictional business stores internal files in a cloud service. The provider may operate the underlying infrastructure, while the business must still decide who can read the files. A well-operated service can still be configured inappropriately for the information it contains.
AWS describes shared responsibility as depending on the services selected and how they are used. The practical lesson is to identify the boundary rather than assume that either the provider or the customer does everything. A cloud-security practitioner and a governance reviewer can examine the same service from different perspectives.
Separate the risk, control and evidence
A risk statement explains what could go wrong and why it matters. A control is a measure intended to address it. Evidence is information that helps a reviewer understand whether that measure is in place and operating as expected. A policy document alone does not prove that every account follows it.
TWA’s existing direction connects identity, logging, configuration/access reviews, risk assessment, control mapping, evidence and repeatable checks. NIST CSF 2.0 provides industry guidance for organising cybersecurity outcomes, including governance. Using that framework does not mean TWA or a learner’s project is certified, audited or legally compliant.
Give a helper enough access—not everything.
A volunteer needs to read one report folder in a fictional cloud workspace. Their account currently has administrator access to everything.
Your role: Compare the job with the account’s access, reduce unnecessary permission, test it and explain what the evidence supports.
What you’ll learn: Limit access to a task and explain what evidence supports the change.
No account needed. Nothing is sent or saved. You can restart at any point.
Read the full guided story without the interactive controls
You can follow the same lesson here without JavaScript.
Compare the task with the permission
Inspect what the helper needs and what the account can currently do.
What happens and why: The job is to read reports, while administrator access allows changes beyond that job. Excess permission increases the potential harm from mistakes or account misuse.
Choose a permission that fits the task
Limit access to read-only for the report folder and test both a permitted report and an unrelated private folder.
What happens and why: Least privilege means enough access for the job without unnecessary capabilities. The report is readable; the private folder is denied in this model.
Collect evidence that the control operated
Select dated permission settings and matching access-test records for the review week. Compare this with a policy statement alone.
What happens and why: A policy states intent. Scoped settings and records of allowed/denied checks support operation within the sample. They do not prove universal coverage or compliance.
Explain the chain and its limits
Prepare a note connecting excessive access, the permission change, test evidence and the remaining review questions.
What happens and why: A useful control note names risk, control, evidence, scope and uncertainty. This model is not a framework audit or certification; real access and evidence must be reviewed by authorised people.
Takeaway: Fit permissions to the task, test what is allowed and denied, then document evidence and scope. A written policy and an operating control are different things.
Where this is useful: Useful in access reviews, cloud administration and governance/risk discussions.
A fictional educational example, not a confirmed TWA assignment, assessment or learner outcome. Simplified to explore one idea; real situations need context and authorised procedures.
Optional deeper exploration: open the original technical workspace
Want to explore the technical model?
The guided story above introduces the idea. This original workspace lets you try actions in different orders. It has its own reset and does not inherit your story choices.
- Least privilege
- Give only the permissions needed for a defined task.
- Read-only
- Permission to view information without changing it.
- Control
- A measure intended to reduce a defined risk.
- Operating evidence
- Records supporting that a control worked in a specified scope and period.
Connect a risk to proof.
Learning objective: Distinguish control design from evidence of operation.
A fictional cloud administrator account could be accessed using only a stolen password.
Evidence desk
- Risk
- Administrator account takeover
- Possible control
- Require MFA for privileged access
- Audit question
- Was the requirement applied during the review period?
Your workspace
Worked explanation & takeaway — available without JavaScript
MFA is a relevant control. A policy describes intent; dated identity-provider settings plus a sample of sign-in enforcement events support operation. Evidence needs scope, dates and review. Neither a screenshot nor this model proves compliance with a framework.
Fictional educational model. No live system, personal assessment or confirmed TWA assignment. All actions run locally in your browser.
From a risk to a reviewable control
The matrix is illustrative. It does not assess a live cloud account.
| Concern | Control direction | Evidence question |
|---|---|---|
| Unneeded access | Review and restrict permissions | Who approved the current access list? |
| Missing visibility | Define logging and review responsibilities | What was recorded and who checks exceptions? |
| Unresolved finding | Assign corrective action | Who owns the next review and what will show progress? |
Review approved access against the fictional business need. Useful evidence includes a scoped permission record and owner approval; do not expose real personal information.
Read both scenarios and explanations
Access is broader than intended
Review approved access against the fictional business need. Useful evidence includes a scoped permission record and owner approval; do not expose real personal information.
A control has no evidence owner
Identify who can supply and explain the evidence, define its scope and record the gap. A checked box without support is not the same as a verified control.
An educational illustration using fictional situations. It is not a confirmed TWA assignment, live system, assessment or promise of a particular tool.
Practise a control review with a clear scope
For the sample file service, define the information, account owners and intended access. Review whether an authorised access list matches the business need. Record the scope and date of the observation, any exceptions and the owner of a corrective action. Do not collect unnecessary sensitive records simply to make an evidence pack look substantial.
A screenshot may support one observation, but it can be incomplete or become outdated. A useful evidence note says what was checked, what the evidence can demonstrate and what remains uncertain. Repeated checks can improve consistency, while the governance decision still needs an accountable owner.
A scoped cloud-control evidence pack
Review a fictional internal file service using invented users and a stated access policy. Do not inspect a live organisation without authority.
What you could document
- A responsibility and system-boundary note
- A risk/control/evidence matrix
- A redacted example observation with scope and limitations
- An action log with ownership and a review point
What makes the explanation useful?
The pack should distinguish policy, observed configuration and inferred conclusions. It must not turn one screenshot into a claim of complete compliance.
The learning plan determines actual activities and assessment. These deliverables are examples, not contractual curriculum outcomes.
Choose the technical or governance emphasis deliberately
Cloud-security learning can deepen configuration and identity decisions. GRC work can emphasise risk communication, control mapping and evidence quality. The strongest handover connects both: a finding someone can understand and an action someone is responsible for.
Bring cloud or cybersecurity foundations to the discussion with TWA. The Nigerian selector below prices the Cloud Security focus only; it does not automatically price an independent GRC plan. Tell the team if your goal is governance depth, technical control review or a combination so the scope and fee can be confirmed.