Skip to main content
Contact on WhatsApp

Cloud Security Practitioner: Shared Responsibility Without the Jargon

Cloud Security Practitioner: Shared Responsibility Without the Jargon

Moving to the cloud does not move your security responsibility to the provider. It splits it. The provider secures the cloud itself, meaning the physical facilities, the hardware, and the underlying infrastructure that runs the services. You secure what you put in the cloud and how you configure it, meaning your data, your identities, your network rules, and your application settings. That split is called the shared responsibility model, and it changes with the service you choose. With infrastructure services you carry more of the work, including the operating system and the applications you install. With managed services the provider carries more, but you still own your data, your access decisions, and your configuration. The most common cloud mistake is assuming the split is the same everywhere, or that it is the provider's job alone. Identity and access management, usually shortened to IAM, is the set of rules that decide which person, service, or application can touch which resource. The practical habits are simple to state and easy to get wrong: give each identity only the access its job needs, use multi-factor authentication for human access, remove access promptly when someone changes role or leaves, and review privileged accounts regularly. Most cloud incidents that look technical start here, with an over-privileged key or an account that should have been closed. Cloud resources are reachable by design, which is useful and dangerous at the same time. The question to ask about every resource is whether it needs to be public, and if it does not, whether it is actually private. Security groups, firewall rules, and private networking decide this, and a single open rule can undo careful work elsewhere. Checking exposure is not a one-time setup task. Every new deployment can reopen something, so exposure checks belong in the routine, not just in the launch week. Encryption protects data when it is stored and when it moves between systems, and the customer side of the job is choosing the right settings and managing the keys sensibly. The useful test is not whether encryption is mentioned somewhere in a console. It is whether you can say, for a given dataset, what is encrypted, with which key, who can use that key, and what happens if that key is lost or compromised. If you cannot answer that, encryption is a setting, not a control you understand. Cloud services generate detailed logs, but logs only help if someone collects them, reviews them, and knows what normal looks like. Logging covers who signed in, what changed, and which resources were accessed, and monitoring turns those events into alerts worth acting on. A cloud practitioner who cannot trace a change back to an identity, a time, and a resource will struggle to explain an incident, however good the rest of the setup looks. Kubernetes and container workloads follow the same principles, with faster moving parts. Images, pod permissions, network policies, and secrets all need the same discipline as virtual machines, plus attention to the cluster itself: who can administer it, what images are allowed to run, and what a compromised workload can reach next. Treating containers as if they were automatically secure because they are modern is a shortcut that does not survive contact with a real cluster.

CIS Benchmarks are widely used checklists for secure configuration of cloud platforms. Used well, a benchmark gives a learner a concrete list to work through: this setting, this value, this reason. Used badly, it becomes a score to chase, with exceptions nobody recorded and settings changed to pass a check without understanding the risk behind it. The healthier habit is to treat each benchmark item as a question. What risk does this control reduce, what breaks if it is applied here, and what is the documented exception if it cannot be applied? That habit transfers across AWS, Azure, and Google Cloud, even though the console names and default settings differ. The Cyber Legends Cloud Security Practitioner training is listed in the live audit across AWS, Azure, and Google Cloud. The topic map for this offering names its ground as shared responsibility, IAM, network, encryption, logging, Kubernetes, and CIS Benchmarks, which matches the sections above. The schedule entry on record lists this training as a 2-month programme with 24 sessions. The module-by-module list for this training was not in the files checked for this draft, so no module titles are quoted here. The programme is offered in Lahore and online, under the standing Cyber Legends terms: a one-time advance payment carries a 5 to 10 percent discount, or up to 3 installments at 50 percent, 25 percent, and 25 percent. The standing fee table includes a 2-month option at Rs 50,000, which matches the 2-month schedule entry, but confirm the current fee with the training advisors before enrolling. No training guarantees a job, a salary level, or a certification pass. Cloud platforms also change constantly, so a course that only teaches console clicks will age quickly. The durable value is the judgement underneath: how to read a shared responsibility split for a new service, how to decide what should be public, how to review access, and how to explain a cloud decision in business terms, not just in console terms. A practical way to prepare, before or alongside the course: open a free-tier cloud account and build one small workload, then practise locking it down: private by default, least-privilege access, and logging switched on. Learn one cloud identity model properly, including roles, policies, and how a service assumes a role, before trying to compare three clouds at once. Practise reading a CIS Benchmark item as a question about risk, not as a setting to copy without thinking. Write down every change you make in a lab, with the reason, so you practise the documentation habit employers actually test.

Frequently asked questions. Is cloud security the provider's job once we migrate? No. The provider secures the cloud infrastructure. You secure your data, identities, configuration, and applications in the cloud. The split changes by service type, so it must be checked for each service you use. Do I need to learn AWS, Azure, and GCP at once? The training is listed across all three, but the concepts transfer. Shared responsibility, IAM, network exposure, encryption, and logging work the same way in principle, even when the console names differ. Depth in one platform first, then comparison across platforms, is a sensible order. What does it cost? Confirm the current fee with the training advisors before enrolling. The standing terms on record are a 5 to 10 percent discount on one-time advance payment, or up to 3 installments at 50 percent, 25 percent, and 25 percent, and the standing fee table includes a 2-month option at Rs 50,000, matching the 2-month schedule entry for this training. Is this the same as the Cloud Security Posture Assessment service? No. This is a training programme for learners. The Cloud Security Posture Assessment is a separate service that assesses an organisation's cloud setup. Next step: Explore the training programme at https://cyberlegends.org/training/EqKjaP1g/ and the full catalogue at https://cyberlegends.org/trainings/ . When you are ready, apply through the official form at https://cyberlegends.org/application/ . For training enquiries, the address on record is [email protected]. References: AWS Shared Responsibility Model: https://docs.aws.amazon.com/wellarchitected/latest/security-pillar/shared-responsibility.html ; NIST Cybersecurity Framework: https://www.nist.gov/cyberframework ; CISA: https://www.cisa.gov/

Share Article

Related Insights

The Great DM Decryption: 5 Impactful Takeaways fr…
Mar 14, 2026
The Obsolete Roadmap: 6 Counter-Intuitive Truths …
Mar 16, 2026
5 Surprising Realities of the 2026 Cyber Landscap…
Mar 16, 2026
Link copied to clipboard!
Footer - Cyber Legends