Cloud & IT Career Foundations · Intermediate · ~7 hours
Cloud Security Fundamentals
Identify common cloud security risks across identity, configuration, networking, data and monitoring.
Status: Catalogue ready. This lesson version is available in review mode while subject-matter, accessibility and assessment checks are completed.
Secure the shared boundary
Shared responsibility and cloud boundaries
By the end of this lesson
- Explain why cloud security responsibility is shared and service-dependent.
- Build a control matrix with provider and customer owners.
- Identify a boundary that requires contract or specialist review.
The foundations of cloud shared responsibility
Cloud services change where technology runs, but they do not remove responsibility. A provider may operate physical facilities, core hardware, some managed platform components and parts of the service's resilience. The customer may still own identities, data classification, configuration, access, endpoint security, application code, retention and the decision about how the service is used. The exact split depends on the service model and contract, so a learner should ask what is actually included rather than relying on a generic diagram. Shared responsibility is useful because it prevents two opposite errors. A customer may assume the provider secures every configuration choice, or a provider may imply that the customer must solve a control the service actually owns. Write the boundary as a matrix: control area, provider responsibility, customer responsibility, evidence source, exception and owner. This makes a sales, support or security conversation more precise. A useful beginner habit is to name the decision before reaching for a tool. What is the organisation trying to protect, restore, understand or improve? Who owns that outcome? Which information is reliable enough to act on, and what would make the decision unsafe? This keeps a technical conversation connected to a real business need rather than a list of fashionable features. It also helps a learner explain a limit honestly. A control can reduce a risk without removing it, and a support action can restore service without proving the underlying cause. When several teams are involved, write the boundary between their responsibilities. A security analyst may identify a signal, an infrastructure owner may confirm service health and a business owner may decide whether a process can pause. Clear boundaries reduce duplicated work and prevent a learner from making a decision outside their authority. Use vendor-neutral language first: describe the capability, evidence and trade-off before naming a product. Never use a course scenario to imply that a learner has worked for a real organisation, handled real private data or achieved an employment outcome.
Applying cloud shared responsibility in a real workflow
A fictional community platform moves a reporting workload to a managed service. The provider explains physical resilience and platform maintenance; the customer remains responsible for identity, report permissions, data retention and secure integration. The team tests the matrix against a real workflow and records which questions need contract or architecture review. A safe workflow is proportionate. Start with the least disruptive action that can answer the question, preserve a record of what changed and escalate when the facts exceed the role or the agreed scope. If an action could affect availability, privacy, money, identity or customer trust, pause for approval rather than improvising. A good handover states the observed symptom, the time window, the affected scope, the checks already completed and the next decision needed. It does not contain secrets, unnecessary personal data or speculative blame. This approach is especially important for customer-facing technology work. Explain what is known, what is inferred and what still needs confirmation. Ask permission before collecting evidence, and use a fictional or redacted example for practice. If a learner cannot safely complete a step in a sandbox, the correct response is to describe the step and its approval boundary, not to try it against a live system.
Evidence, privacy and escalation
For cloud shared responsibility, evidence should be sufficient to support the next decision and limited to what that decision requires. Begin with an approved scope: the system, account, process, time window and owner. Use synthetic records in training. If a real example is unavoidable, redact names, addresses, identifiers, customer content, credentials, tokens and security-sensitive configuration before it is shared. Do not paste secrets into a ticket, chat, portfolio, lesson answer or CRM note. A screenshot is not automatically safe; it can reveal more than the visible field, including browser tabs, notifications and metadata. Record observations separately from interpretations. An observation might be “three sign-in attempts were rejected between 09:10 and 09:14”; an interpretation might be “the account was attacked”. The second may be a reasonable hypothesis, but it needs corroboration. Record the source, timestamp, confidence and next check. Protect the chain of custody or change history where the matter may become an incident, audit or customer conversation. Escalate through the approved route when there is possible compromise, personal-data exposure, material service impact, financial risk, a safety concern or a decision outside your authority. Escalation is not a failure; it is a control. Tell the receiving owner what has happened, what has not happened, what action is being requested and how urgent it is. Do not investigate beyond your authorisation, contact a suspected attacker, download unapproved tools or promise a customer a particular outcome. Close the loop with a short, privacy-safe summary and identify one improvement to the process. This is the evidence expected from a responsible foundation learner: careful scope, accurate language, a practical next step and an honest statement of limits. A responsibility matrix should name service model, control area, owner, evidence source, dependency and limitation.
Workplace example
Fictional charity Meadowline uses a managed database and records who owns backups, access, encryption settings, retention and recovery testing instead of assuming the provider owns all of them.
Try this walkthrough
- 1.Describe the workload, service model and data.
- 2.Map each control area to provider and customer responsibility.
- 3.Identify evidence, dependencies, gaps and owners.
- 4.Escalate contractual or architectural uncertainty before making a claim.
Watch for these traps
- Saying cloud means the provider handles every security decision.
- Copying a generic shared-responsibility diagram without checking the service.
- Ignoring customer identity and data configuration.
- Promising a cloud control without reviewing the contract or scope.
Knowledge check
Choose the response you think is strongest. These checks are practice until the course version has passed subject-matter review; graded attempts will be handled server-side.
For the reviewed pilot, answers are checked on the server. This draft result is not yet added to your official learning record.
Practice studio
Make a decision. Test a response. Leave evidence.
Use the case from this lesson to practise judgement without creating a score or changing your course record.
Scenario decision
Fictional charity Meadowline uses a managed database and records who owns backups, access, encryption settings, retention and recovery testing instead of assuming the provider o…
Choose a response
Branching roleplay
A colleague asks you to move this situation forward. What do you say next?
Evidence workspace
Draft a short known / assumed / next note from the fictional case. Use fictional details only.
This is a session-only practice draft. It is not saved, graded or added to your learning record. Never enter real personal or confidential information.
Practical assignment
Create a fictional shared-responsibility matrix for a managed reporting workload. Include identity, data, configuration, resilience, evidence, contract questions and owners.
Pass this lesson's knowledge check before recording it as complete.
Portfolio evidence
Practical portfolio project
Review a fictional cloud environment, identify configuration risks and recommend a prioritised remediation plan.
Turn the practical project into a bounded evidence record. Save a draft while you work, then submit it for human review when it is ready.
Sign in to save practical evidence. Sign in