Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Cloud

3/12/2019
10:30 AM
Ory Segal
Ory Segal
Commentary
Connect Directly
Twitter
LinkedIn
RSS
E-Mail vvv
50%
50%

The 12 Worst Serverless Security Risks

A new guide from the Cloud Security Alliance offers mitigations, best practices, and a comparison between traditional applications and their serverless counterparts.

Serverless computing has seen tremendous growth in recent years. This growth was accompanied by a flourishing rich ecosystem of new solutions that offer observability, real-time tracing, deployment frameworks, and application security.

As awareness around serverless security risks started to gain attention, scoffers, and cynics repeated the age-old habit of calling "FUD" — fear, uncertainty and doubt — on any attempt to point out that while serverless offers tremendous value in the form of rapid software development and huge reduction in TCO, there are also new security challenges.

The Evolving Serverless Ecosystem
One of the key indicators for a mature technology is the ecosystem that evolves around it. Having a thriving community, extensive documentation, best-practices guides, and tooling is what will drive organizations to trust new technologies and adopt them.

Recently, the Cloud Security Alliance (CSA) joined forces with PureSec, where I am CTO and co-founder, to develop an extensive serverless security guide. The guide draws much of its content from last year's effort, but with the addition of two important risk classes.

The guide, titled "The 12 Most Critical Risks for Serverless Applications," was written for both security and development audiences dealing with serverless applications but goes well beyond pointing the risks. It also provides best practices for all major platforms. The risk categories are defined as follows:

Risk 1: Function Event-Data Injection
Serverless functions can consume input from different types of event sources, and each event source has its own message format and encoding schemes. Various parts of these event messages may contain attacker-controlled or untrusted inputs that should be carefully inspected.

Risk 2: Broken Authentication
Since serverless promotes a microservices-oriented system design, applications may contain dozens or even hundreds of functions. Applying robust authentication can easily go awry if not executed carefully.

Risk 3: Insecure Serverless Deployment Configuration
Cloud providers offer many configuration settings to adapt services for specific needs. Out-of-the-box settings are not necessarily always the most secure. As more organizations are migrating to the cloud, cloud configuration flaws will become more prevalent.

Risk 4: Overprivileged Function Permissions and Roles
Managing function permissions and roles is one of the most daunting security tasks organizations are facing when deploying applications to the cloud. It is quite common to see developers cut corners and apply a "wildcard" (catch-all) permission model.

Risk 5: Inadequate Function Monitoring and Logging
While most cloud vendors provide extremely capable logging facilities, these logs are not always suitable for the purpose of providing a full security event audit trail at the application layer.

Risk 6: Insecure Third-Party Dependencies
While the problem of insecure third-party libraries is not specific to serverless, being able to detect malicious packages is more complex in serverless environments given the lack of ability to apply network and behavioral security controls.

Risk 7: Insecure Application Secrets Storage
One of the most frequently recurring mistakes related to application secrets storage, is to simply store these secrets in a plain text configuration file that is a part of the software project. Another common mistake is to store these secrets in plain text, as environment variables.

Risk 8: Denial-of-Service and Financial Resource Exhaustion
Serverless architectures bring promises of automated scalability and high availability; however, as with any other type of application, it is critical to apply best practices and good design in order to avoid bottlenecks.

Risk 9: Serverless Business Logic Manipulation
Business logic manipulation is a common problem in many types of software. However, serverless applications are unique, as they often follow the microservices design and contain numerous functions chained together to form the overall logic. Without proper enforcement, attackers may be able to tamper with the intended logic. 

Risk 10: Improper Exception Handling and Verbose Error Messages
Line-by-line debugging options for serverless-based applications are limited (and more complex) when compared with debugging capabilities for standard applications. As a result, developers frequently adopt the use of verbose error messages, which may leak sensitive data.

Risk 11: Legacy/Unused Functions & Cloud Resources
Over time, serverless functions and related cloud resources may become obsolete and should be decommissioned. The reason behind pruning obsolete components is to reduce unnecessary costs and eliminate avoidable attack surfaces. Obsolete serverless application components may include deprecated serverless function versions, unused cloud resources, unnecessary event sources, unused roles or identities, and unused dependencies.

Risk 12: Cross-Execution Data Persistency
Serverless platforms offer application developers local disk storage, environment variables, and memory to perform their tasks. To make serverless platforms efficient in handling new invocations, cloud providers might reuse the execution environment for subsequent invocations. If the serverless execution environment is reused for subsequent invocations, belonging to different users or sessions, it is possible that sensitive data will be left behind and might be exposed.

It's important to note that the purpose of the guide is to raise awareness and help organizations innovate with serverless securely, not to spread fear. Security risks exist in any type of platform, and serverless is no different. CSA's goal in raising these issues is to encourage organizations to adopt new technologies while avoiding risks and common mistakes.

Editors' note: Ory Segal is a CSA Israel chapter board member. He led the effort behind the "The 12 Most Critical Risks for Serverless Applications" guide.

Related Content:

 

 

 

Join Dark Reading LIVE for two cybersecurity summits at Interop 2019. Learn from the industry's most knowledgeable IT security experts. Check out the Interop agenda here.

Ory Segal is a world-renowned expert in application security, with 20 years of experience in the field. Ory is the CTO and co-founder of PureSec, a start-up that enables organizations to secure serverless applications. Prior to PureSec, Ory was senior director of threat ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/21/2020
Hacking Yourself: Marie Moe and Pacemaker Security
Gary McGraw Ph.D., Co-founder Berryville Institute of Machine Learning,  9/21/2020
Startup Aims to Map and Track All the IT and Security Things
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2015-4719
PUBLISHED: 2020-09-24
The client API authentication mechanism in Pexip Infinity before 10 allows remote attackers to gain privileges via a crafted request.
CVE-2020-15604
PUBLISHED: 2020-09-24
An incomplete SSL server certification validation vulnerability in the Trend Micro Security 2019 (v15) consumer family of products could allow an attacker to combine this vulnerability with another attack to trick an affected client into downloading a malicious update instead of the expected one. CW...
CVE-2020-24560
PUBLISHED: 2020-09-24
An incomplete SSL server certification validation vulnerability in the Trend Micro Security 2019 (v15) consumer family of products could allow an attacker to combine this vulnerability with another attack to trick an affected client into downloading a malicious update instead of the expected one. CW...
CVE-2020-25596
PUBLISHED: 2020-09-23
An issue was discovered in Xen through 4.14.x. x86 PV guest kernels can experience denial of service via SYSENTER. The SYSENTER instruction leaves various state sanitization activities to software. One of Xen's sanitization paths injects a #GP fault, and incorrectly delivers it twice to the guest. T...
CVE-2020-25597
PUBLISHED: 2020-09-23
An issue was discovered in Xen through 4.14.x. There is mishandling of the constraint that once-valid event channels may not turn invalid. Logic in the handling of event channel operations in Xen assumes that an event channel, once valid, will not become invalid over the life time of a guest. Howeve...