An online gaming enterprise is transitioning its matchmaking service to a cloud provider's Function-as-a-Service (FaaS) event-driven architecture integrated with a managed API Gateway. As part of establishing the enterprise cloud security baseline, the lead architect must define operational boundaries under the shared responsibility model. Which of the following tasks remain the sole responsibility of the enterprise customer? (Select TWO.)
- Auditing and remediation of application source code vulnerabilities and third-party software dependenciesAnswer
- BApplying security patches and kernel updates to the host operating system executing the serverless functions
- Configuring least-privilege Identity and Access Management (IAM) execution roles and API Gateway authorization policiesAnswer
- DMaintaining physical security and environmental controls for the facility infrastructure hosting the compute clusters
Answer
The enterprise customer is responsible for auditing application source code and third-party dependencies, as well as configuring least-privilege IAM execution roles and API Gateway authorization policies.
In Function-as-a-Service (FaaS) models, the cloud provider abstracts away servers, operating systems, and physical infrastructure. However, the enterprise customer remains strictly responsible for everything inside their code (such as vulnerability scanning, fixing code bugs, and auditing third-party libraries) and for identity controls (such as defining granular IAM execution roles for functions and configuring access rules at the API Gateway).
Step-by-Step Solution
Key Concept
Cloud Shared Responsibility Model in Serverless (FaaS) Architectures