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

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
7 Tips for Choosing Security Metrics That Matter
Ericka Chickowski, Contributing Writer,  10/19/2020
IoT Vulnerability Disclosure Platform Launched
Dark Reading Staff 10/19/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-2020-15270
PUBLISHED: 2020-10-22
Parse Server (npm package parse-server) broadcasts events to all clients without checking if the session token is valid. This allows clients with expired sessions to still receive subscription objects. It is not possible to create subscription objects with invalid session tokens. The issue is not pa...
CVE-2018-21266
PUBLISHED: 2020-10-22
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Notes: none.
CVE-2018-21267
PUBLISHED: 2020-10-22
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Notes: none.
CVE-2020-27673
PUBLISHED: 2020-10-22
An issue was discovered in the Linux kernel through 5.9.1, as used with Xen through 4.14.x. Guest OS users can cause a denial of service (host OS hang) via a high rate of events to dom0, aka CID-e99502f76271.
CVE-2020-27674
PUBLISHED: 2020-10-22
An issue was discovered in Xen through 4.14.x allowing x86 PV guest OS users to gain guest OS privileges by modifying kernel memory contents, because invalidation of TLB entries is mishandled during use of an INVLPG-like attack technique.