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.

Analytics

6/30/2009
03:47 PM
Connect Directly
Twitter
RSS
E-Mail
50%
50%

OWASP: Security Spending Remains Mostly Unchanged With Cloud Computing

New Open Web Application Security Project report finds enterprises aren't sufficiently verifying cloud providers' security, either

Organizations adopting cloud computing or software-as-a-service (SaaS) technology may be saving money when it comes to their IT infrastructures, but a new report shows it doesn't significantly affect their security spending.

The Open Web Application Security Project (OWASP) survey, released today by the OWASP Security Spending Benchmarks Project, also found enterprises aren't properly vetting the security provided by their cloud computing providers. While about 60 percent of them say security is mentioned in contracts with their service providers, only about half of them said they asked their providers about their internal security policies (53 percent), encryption (54 percent), data segregation (40 percent), data location (41 percent), and compliance (44 percent).

Failing to verify, audit, or test a cloud provider's security is a common misstep in taking the SaaS route, security experts say. Some recommend hiring a third party to verify and evaluate the cloud provider's security, or to even negotiate an on-site visit of your own.

OWASP found far fewer organizations require actual documentation of the cloud provider's security: Only 35 percent said they mandate their provider put in writing their internal security policies; 29 percent, the encryption measures; 29 percent, data segregation setup; 34 percent, data location; and 39 percent, compliance with security rules and regulations.

"That's pretty significant," says Boaz Gelbord, project leader of the OWASP Security Spending Benchmarks Project and executive director of information security for Wireless Generation. "That means that organizations are putting themselves out in the cloud and not even inquiring as to what security there is in place. They are relying on their contractual [arrangement], and that may not be enough."

Many companies are still stuck in the old-school outsourcing mindset and haven't yet factored in the security implications of running a SaaS model. "Their No. 1 concern with cloud computing was the risk of data breaches, but this hasn't translated into action yet," Gelbord says.

And, interestingly, security spending doesn't change much when a company adopts cloud computing -- so far, anyway. "It could be a reflection of the early phase of getting to the cloud, and security budgets can take some time to turn around," Gelbord says.

Only 4 percent said their network security spending rose 10 to 20 percent with their SaaS adoption, while another 4 percent said it increased 20 percent. More than half said their network security spending either increased or decreased by less than 10 percent. More than half said their spending on security staff in the wake of a SaaS implementation changed less than 10 percent, and 9 percent said their staffing expenses declined 10 to 20 percent.

More than half of the respondents deploy online applications (a la Google Docs and Salesforce.com), while less than 25 percent use infrastructure-as-a-service (computing power like Amazon's EC2 service) or platform-as-a-service provisioning services (like Google's App Engine).

Have a comment on this story? Please click "Discuss" below. If you'd like to contact Dark Reading's editors directly, send us a message. Kelly Jackson Higgins is the Executive Editor of Dark Reading. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
News
Inside the Ransomware Campaigns Targeting Exchange Servers
Kelly Sheridan, Staff Editor, Dark Reading,  4/2/2021
Commentary
Beyond MITRE ATT&CK: The Case for a New Cyber Kill Chain
Rik Turner, Principal Analyst, Infrastructure Solutions, Omdia,  3/30/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-28797
PUBLISHED: 2021-04-14
A stack-based buffer overflow vulnerability has been reported to affect QNAP NAS devices running Surveillance Station. If exploited, this vulnerability allows attackers to execute arbitrary code. QNAP have already fixed this vulnerability in the following versions: Surveillance Station 5.1.5.4.3 (an...
CVE-2020-36323
PUBLISHED: 2021-04-14
In the standard library in Rust before 1.50.3, there is an optimization for joining strings that can cause uninitialized bytes to be exposed (or the program to crash) if the borrowed string changes after its length is checked.
CVE-2021-31162
PUBLISHED: 2021-04-14
In the standard library in Rust before 1.53.0, a double free can occur in the Vec::from_iter function if freeing the element panics.
CVE-2017-20004
PUBLISHED: 2021-04-14
In the standard library in Rust before 1.19.0, there is a synchronization problem in the MutexGuard object. MutexGuards can be used across threads with any types, allowing for memory safety issues through race conditions.
CVE-2018-25008
PUBLISHED: 2021-04-14
In the standard library in Rust before 1.29.0, there is weak synchronization in the Arc::get_mut method. This synchronization issue can be lead to memory safety issues through race conditions.