Cloud Infrastructures - CompTIA Security+ SY0-701 - 3.1

Summary

The video explains key cloud infrastructure models and their security implications.

Shared responsibility

Cloud providers typically document a responsibility matrix showing which security tasks belong to the provider, the customer, or both. The division varies by service model and provider. For example, the provider may manage the operating system in SaaS and PaaS, while the customer manages it in IaaS. Customers remain responsible for protecting their accounts and identities. Contracts may change the default allocation.

Hybrid cloud complexity

Using multiple cloud providers offers flexibility but can make configuration and security harder to coordinate. Authentication, server settings, firewalls, and logs may differ between providers, creating inconsistencies and making monitoring more difficult. Data moving between providers also needs protection while in transit over the public internet.

Third-party risk

Organizations may rely on vendors beyond their cloud provider, such as a third-party firewall. A vendor risk-management policy, ongoing monitoring, and incident-response processes that include relevant vendors can help manage these dependencies.

Infrastructure as code (IaC)

IaC defines cloud infrastructure through code rather than individual hardware configurations. It can specify hosts, web servers, databases, and other components, making infrastructure easier to build, update, and reproduce—including across cloud providers.

Serverless architecture

Applications can be divided into smaller functions that run when needed, rather than relying on a continuously running server instance. This can reduce operating costs and shift much of the infrastructure and security work to the cloud environment. Developers focus on creating and deploying functions, with less concern for the underlying operating system.

Microservices and APIs

Compared with monolithic applications—large, single programs installed and updated on client machines—a microservice architecture separates application functions into independently running services. Clients make requests through an API gateway, which routes them to the appropriate service. This supports independent scaling, improves resilience when one service fails, and allows security controls to be tailored to each service’s role.

Reviews, guides, or tutorials

This is an instructional Security+ lesson. It explains cloud infrastructure concepts and security considerations; it does not review a specific product or provide a hands-on tutorial.

Main speaker/source

• Professor Messer — instructor and narrator of the lesson.