OWASP / Serverless-Top-10-Project

OWASP Serverless Top 10

Home Page:https://owasp.org/www-project-serverless-top-10/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Should we add broken multi-tenancy and side-channel vulnerabilites to Other Risks?

MarcinHoppe opened this issue · comments

Serverless environments are inherently multi-tenant environments. If the multi-tenant isolation mechanisms were broken, this would be a very serious attack vector on serverless applications.

Similarly, side-channel attacks (such as Meltdown) pose a serious risk to secrets processed by serverless applications and the integrity of the processing logic itself.

Interesting how this attack always seems to be considered at the platform/service layer, and not at the application layer. Multi-tenant applications are becoming extremely prevalent, yet app-layer tenant isolation doesn't seem to have any clear patterns or solutions. Who cares if the cloud platform is secure if the application allows cross-tenant attacks?