Abstract

Security for Serverless Systems is looked at from two perspectives, the server-level security managed by the infras-tructure company and the Application level Security managed by the tenants.The Trusted computing base for cloud systems is enormous as it encompasses all the functions running on a system. Authentication for systems is mostly done using ACL. Most Serverless Systems share data and thus, ACL isn’t sufficient. IFC using appropriate label design can enforce continuously through-out the application. IFC can be used to increase confidence between functions with other functions and cloud provider and also mitigate security vulnerabilities making the system safer. A survey of the present IFC implementations for Serverless Systems is presented and system designs which are relevant to Serverless Systems and could be added to Serverless Systems Architecture and, an idea of an IFC model that could be effectively applied in a decentralised model like serverless systems.

Highlights

  • Serverless Systems are systems where functions owned by tenants are executed when the functions are triggered, on platforms managed by the cloud provider

  • Security is looked at from two perspectives, the server-level security managed by the infrastructure company and the Application level Security managed by the tenants

  • Serverless Systems are cost-effective resource sharing platforms where the tenants only pay for the time their function/service is executing/working on the machines and the machine setup time for a function i.e the microVM/container creation and startup time has to be minimal, as that time is paid for by the cloud provider, which does not leave a lot of scope for setting up security measures specific for functions by the cloud provider

Read more

Summary

INTRODUCTION

Serverless Systems are systems where functions owned by tenants are executed when the functions are triggered, on platforms managed by the cloud provider. The infrastructure, security and updates of these systems along with the hardware are managed by the cloud provider and the tenant only manages their function and it’s security. Security is looked at from two perspectives, the server-level security managed by the infrastructure company and the Application level Security managed by the tenants. The reasons for the boom of serverless computing are elastic scalability, ease of deployment, and flexible pay-per-use pricing. Trusted computing base(TCB) consists of all the parts of the system (like hardware, software, libraries, firmware), all the components which could leave the system vulnerable and jeopardize the security of the whole system. The TCB for cloud systems is enormous

Server-Level Security
Application Level Security
Paper Outline
BACKGROUND
Containers
MicroVM
Scheduling or Warm Containers
Hypervisors
Attacks on Serverless Systems
PRESENT SECURITY SOLUTIONS FOR SERVERLESS SYSTEMS
LACK IN PRESENT SECURITY SOLUTIONS FOR SERVERLESS SYSTEMS
NEED FOR DISCRETIONARY ACCESS CONTROL
Warm Starts
Termination
Sticky Policies
Continuous Checks
Implicit Storage Channel
Audit Logs
Hardware Level - General Implementation
Kernel Level - Cloud Implementation
VM Level - General Implementation
OS Level - General Implementation
Network Level - Serverless Implementation
Service Level - Cloud Implementation
Chinese Wall - General Implementation
VIII. ADVANTAGES
TRADE-OFF
IMPLEMENTATION
FUTURE RESEARCH DIRECTION
CONCLUSION
Full Text
Paper version not known

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.