Certified Cloud Security Professional (CCSP)Cloud Platform and Infrastructure SecurityMedium
A global enterprise is migrating its legacy applications to a serverless architecture to reduce operational overhead and improve scalability. The security team is concerned about potential over-privileging of serverless functions. Which security principle is most critical to apply when defining permissions for these functions?
- ANeed-to-Know
- BLeast Privilege
- CDefense in Depth
- DSeparation of Duties
Show answer & explanationAnswer & explanation
Correct answer: B. Least Privilege
The principle of least privilege dictates that a process, user, or program (including a serverless function) should be given only the minimum privileges necessary to perform its task. This is crucial for serverless functions, as over-privileging can lead to significant security risks if a function is compromised.
Why the other options are wrong
- A. Need-to-Know is related to access control based on job function, but Least Privilege is the more encompassing principle for defining the actual permissions granted.
- C. Defense in Depth involves multiple layers of security controls, but doesn't specifically address the granular permissions of a single function.
- D. Separation of Duties applies to human roles and responsibilities, not directly to the permissions granted to an automated serverless function.
Least Privilege (Serverless)
Applying the principle of least privilege to serverless functions, granting them only the minimum necessary permissions to perform their specific tasks, thereby reducing the attack surface.
- Minimizes the blast radius of a compromised function.
- Requires careful IAM policy definition for each function.
- Challenges include dynamic permissions and multiple service integrations.
Memory trick: Only give the function what it absolutely needs to do its job.