[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"lesson-cloud-computing-fundamentals-security-and-reliability-en":3,"cheat-sheet---en":3,"topic-info----en":3,"prev-cloud-computing-fundamentals-security-and-reliability-en":3,"next-cloud-computing-fundamentals-security-and-reliability-en":3,"domain-info-cloud-computing-fundamentals-security-and-reliability-en":4},null,{"meta":5,"body":8},{"title":6,"description":7},"Security and Reliability","Who secures what in the cloud, and how cloud systems stay up. You learn the shared responsibility model, identity and encryption basics, and the patterns behind high availability and disaster recovery.",{"type":9,"value":10,"toc":61},"minimark",[11,15,18,23,51,55,58],[12,13,14],"p",{},"Security and Reliability follows the services domain: now that you can name compute, storage, databases, and networking, you need to know who protects them and what keeps them running. This domain answers two questions cloud teams face every day: who owns security, and how does a system stay available.",[12,16,17],{},"It opens with the shared responsibility model, the idea that draws the line between what your provider secures and what you still own, then moves through identity, encryption, and compliance. The second half turns from protecting data to keeping it running: high availability, scaling, backups, and the service-level agreements that put a number on uptime.",[19,20,22],"h2",{"id":21},"what-this-domain-covers","What This Domain Covers",[24,25,26,30,33,36,39,42,45,48],"ul",{},[27,28,29],"li",{},"the shared responsibility model, and where the provider's security duties end and yours begin",[27,31,32],{},"identity and access management, and how the cloud confirms who you are and what you can do",[27,34,35],{},"encryption and data protection, both at rest and in transit",[27,37,38],{},"governance and compliance basics for regulated workloads",[27,40,41],{},"high availability and fault tolerance, and how systems keep running when a component fails",[27,43,44],{},"scalability and elasticity, and why they are not the same thing",[27,46,47],{},"backup and disaster recovery planning",[27,49,50],{},"monitoring and SLAs, and what an uptime guarantee actually promises",[19,52,54],{"id":53},"why-it-matters","Why It Matters",[12,56,57],{},"Most cloud security incidents you read about are not the provider's fault. They trace back to a team assuming the provider secured something that was actually the customer's job, like an open storage bucket or an overprivileged access key. The shared responsibility model removes that guesswork: once you can state where the provider's job ends and yours begins, \"who patches this\" or \"who encrypts that\" stop being guesses.",[12,59,60],{},"Reliability matters for a different reason: a perfectly secure system that goes down still fails the business relying on it. Once you understand high availability, scaling, and disaster recovery, you can explain why a well-designed system survives a server failure without anyone noticing, and what an SLA actually promises. This domain gives you the vocabulary that shows up constantly in cloud job interviews and in the certification path this course leads toward.",{"title":62,"searchDepth":63,"depth":63,"links":64},"",3,[65,67],{"id":21,"depth":66,"text":22},2,{"id":53,"depth":66,"text":54}]