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

4/26/2013
02:05 AM
50%
50%

Cloud Security Starts With Development, Better Tools

Companies must train their developers in secure coding and rely on others' expertise for complex components of cloud services and Web applications

Companies that aim to exterminate security bugs from their software face a long and difficult road. The developers of Web and cloud applications are no exception.

Almost all Web applications continue to have vulnerabilities, according to a study released in March by Cenzic, a cloud-applications security provider. Based on software tested by the company in 2012, the study found that 99 percent of applications deployed as Web and cloud services had vulnerabilities -- an average of 13 flaws per application. Cross-site scripting, information leakage, and session-management flaws topped the list.

"The industry is not as ready to secure Layer 7 [the application layer] as they should be," says Bala Venkat, chief marketing officer for the firm. "Companies need to focus on the coding practices that are used by the developers, and really focus on the static side, even before the application gets into production."

Part of the problem is that early cloud providers -- and companies building private clouds -- focused on creating the applications, not getting all the security details right, says John Howie, chief operating officer at the Cloud Security Alliance. Fixing those problems after that fact has left many companies with hard-to-secure code.

"Developers were not really thinking about application security or code-level security," Howie says. "And in some cases, the problems were exacerbated because they were developing the equivalent of intranet applications, but putting them on the public Internet."

Attackers have noticed. Recent distributed denial-of-service attacks against financial institutions, for example, have been powered by botnets using Web servers that have been compromised through common vulnerabilities. And while most cloud compromises -- such as LinkedIn and CloudFlare -- have relied heavily on social engineering, software-security missteps played a role as well.

[What makes cloud computing so attractive to businesses -- the sharing of resources to achieve economies of scale -- also makes the model attractive to cybercriminals. See How Cybercriminals Attack The Cloud.]

To harden Web applications and cloud services, companies need to start with the developers and give them the tools they need to produce secure code.

Education and training are the first steps. The demand for Web application and cloud-service developers has resulted in many developers -- who may not have the training necessary to produce secure code -- writing code for online applications and cloud services, the CSA's Howie says.

"All of the major cloud providers will bring in people who are not classically trained software developers and train them to write software," Howie says.

Companies should focus on giving those developers the skills they need to program securely and placing the training within the framework of a secure product development life cycle.

Web developers and cloud-service providers should also invest in the tools needed to secure their applications and infrastructure. Static code analysis and dynamic vulnerability checking can help companies avoid common errors. Code libraries can help developers get the tricky security components -- such as authorization, encryption, and key management -- done correctly.

When cloud infrastructure, and the management of hundreds or thousands of virtual servers, made creating and distributing security policies difficult, data security firm Vormetric created a toolkit to help deploy the policies more easily.

"Smaller enterprise deployments, they can deal with managing the security policies," says Derek Tumulak, vice president of product management for the firm. "In the large-scale deployments, that is when you hit a pain point."

Developers should aim to make cloud services as secure as inside the corporate network -- a tall order, says Tsahy Shapsa, co-founder of CloudLock, a provider of cloud security tools. "You should be able to give [the cloud customer] the safeguards to ensure that they can use the public cloud, and use it with the same security and control over their data as on premise," Shapsa says.

Have a comment on this story? Please click "Add Your Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message. Veteran technology journalist of more than 20 years. Former research engineer. Written for more than two dozen publications, including CNET News.com, Dark Reading, MIT's Technology Review, Popular Science, and Wired News. Five awards for journalism, including Best Deadline ... View Full Bio

 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
marktroester
50%
50%
marktroester,
User Rank: Apprentice
5/1/2013 | 5:26:04 PM
re: Cloud Security Starts With Development, Better Tools
I agree that the developers have to have the tools necessary for them to develop secure applications, and not tools that are designed for security experts, or tools that provide false positives that require time and effort to address. The other thing to note is that applications are now constructed from components - per a recent survey of 3500 developers, architects and IT managers - modern applications consist of 80% open source components. So that has to be factored into the approach that the developers use to produce secure applications.

Survey results are here: http://blog.sonatype.com/peopl...

Thanks,
Mark Troester
@mtroester
Sonatype
COVID-19: Latest Security News & Commentary
Dark Reading Staff 5/28/2020
Stay-at-Home Orders Coincide With Massive DNS Surge
Robert Lemos, Contributing Writer,  5/27/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Can you smell me now?
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-11844
PUBLISHED: 2020-05-29
There is an Incorrect Authorization vulnerability in Micro Focus Service Management Automation (SMA) product affecting version 2018.05 to 2020.02. The vulnerability could be exploited to provide unauthorized access to the Container Deployment Foundation.
CVE-2020-6937
PUBLISHED: 2020-05-29
A Denial of Service vulnerability in MuleSoft Mule CE/EE 3.8.x, 3.9.x, and 4.x released before April 7, 2020, could allow remote attackers to submit data which can lead to resource exhaustion.
CVE-2020-7648
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.72.2 are vulnerable to Arbitrary File Read. It allows arbitrary file reads for users who have access to Snyk's internal network by appending the URL with a fragment identifier and a whitelisted path e.g. `#package.json`
CVE-2020-7650
PUBLISHED: 2020-05-29
All versions of snyk-broker after 4.72.0 including and before 4.73.1 are vulnerable to Arbitrary File Read. It allows arbitrary file reads to users with access to Snyk's internal network of any files ending in the following extensions: yaml, yml or json.
CVE-2020-7654
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.73.1 are vulnerable to Information Exposure. It logs private keys if logging level is set to DEBUG.