Objective. Students will explain the shared-responsibility security model for IaaS, PaaS, and DBaaS tiers and identify which security controls the DBA must own on each major cloud platform.
This lesson, its worked examples and its practice questions has not yet been verified by an industry-certified professional or by a certification or approval body. It is a study draft and may contain errors. Do not use it as instructions for work on a job site or on live equipment. Always follow your instructor, your supervising professional, and current official references and regulations.
VoTechWorks program approval and accreditation are still in progress. Credentials are issued only by the certifying bodies named in each program, after their own exams.
Cloud computing means accessing computing resources—servers, storage, databases, networking—over the internet from a provider who owns and operates the physical infrastructure. For a database administrator, the cloud is not a single thing; it is a spectrum of service models that each place different responsibilities on you and your employer. Understanding where your responsibility begins and ends is one of the most critical security skills you will develop in this program.
Infrastructure as a Service (IaaS) gives you a virtual machine running on the provider's hardware. You install the operating system, install the database engine, patch both, configure the firewall, and manage backups. AWS EC2, Azure Virtual Machines, and Google Compute Engine are IaaS examples. The provider keeps the physical data center secure; you are responsible for almost everything above the hypervisor.
Platform as a Service (PaaS) removes the operating system layer from your plate. The provider manages the OS, the underlying hardware, and often the database engine patches. Azure App Service and Google App Engine are general PaaS examples. When a managed database engine runs under PaaS rules—such as Amazon RDS or Azure Database for PostgreSQL Flexible Server—you still own network access rules, user accounts, encryption key choices, and data classification.
Database as a Service (DBaaS) is a specialized PaaS offering focused entirely on a database engine. Examples include Amazon RDS, Amazon Aurora, Azure SQL Database, Azure Cosmos DB, Google Cloud SQL, and Google Cloud Spanner. The provider manages the engine software, high availability, automated backups, and hardware. You manage who can connect, what data goes in, how encryption is configured, and whether audit logging is turned on.
As you move from IaaS toward DBaaS, the provider takes on more operational burden—but you never hand over accountability for your data.
Every major cloud provider publishes a shared-responsibility model: a formal statement of which security controls the provider handles and which the customer must handle. AWS, Microsoft Azure, and Google Cloud each publish this as a publicly available whitepaper or documentation page. The model exists because a cloud customer who assumes the provider handles everything will leave serious security gaps.
The core principle is straightforward: the provider is responsible for security OF the cloud; the customer is responsible for security IN the cloud.
At the IaaS tier, your DBA responsibilities include:
At the PaaS/DBaaS tier, the provider absorbs:
But you retain responsibility for:
The vast majority of cloud data breaches do not involve the provider's infrastructure being hacked. They involve customer-side misconfiguration: a database left publicly accessible without authentication, an overly permissive security group rule, encryption disabled, or audit logging never turned on. In each case, the provider did everything required under the model; the customer did not fulfill their side.
This is exactly why the shared-responsibility model is tested on credentials such as the Microsoft DP-300 and is a foundation topic in the DAMA DMBOK2. A DBA who cannot articulate which controls they own cannot protect their organization's data.
Amazon Web Services (AWS): Managed database services live under the RDS family and include MySQL, PostgreSQL, MariaDB, Oracle, SQL Server, and the Aurora engine. Access control uses IAM policies combined with database-engine-level users. Security groups control network access.
Microsoft Azure: Managed databases include Azure SQL Database, Azure Database for PostgreSQL, Azure Database for MySQL, and others. Azure uses Role-Based Access Control (RBAC) at the platform level and native database logins at the engine level. Network access is controlled by firewall rules and virtual network service endpoints.
Google Cloud Platform (GCP): Cloud SQL supports PostgreSQL, MySQL, and SQL Server. Cloud Spanner and BigQuery serve specialized workloads. IAM controls platform-level access; database-engine users control data-level access. Authorized networks and Private Service Connect control connectivity.
Cloud environments introduce unique operational risks:
Answer each question, then check it. Nothing is recorded; this is your own practice.
A free tech program — complimentary, as our commitment to get America working. Help us build VoTechWorks. Tell us what works, what doesn’t, and what you want to learn.