A healthcare organization deploys a microservice backend utilizing a serverless Function-as-a-Service (FaaS) architecture on a public cloud platform to ingest patient telemetry. Under the cloud shared responsibility model, which TWO of the following security tasks remain the responsibility of the organization rather than the cloud service provider?
- Defining granular execution roles and access permissions within the cloud identity and access management frameworkAnswer
- Performing static code analysis and enforcing input validation logic within the serverless function source codeAnswer
- CPatching security vulnerabilities in the host operating system and serverless container runtime environment engine
- DConfiguring network perimeter firewalls and maintaining physical security across host compute hardware
Answer
The organization is responsible for defining granular identity and access management policies for function execution roles and performing code-level security mitigations within the serverless application source code.
In serverless (FaaS) architectures, the cloud service provider abstracts and manages the underlying server hardware, operating systems, and runtime execution engines. The customer retains full responsibility for security 'in' the cloud—specifically writing secure application code, sanitizing input data, and defining granular access permissions and identity policies for execution roles.
Step-by-Step Solution
Key Concept
Shared Responsibility Model in Serverless (FaaS) Architectures