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.

Risk

8/10/2012
01:59 PM
Adrian Lane
Adrian Lane
Quick Hits
50%
50%

Strategies For Protecting Web-Facing Databases

The Web is the cybercriminal's favorite medium for attacking your database. But some databases must face the Web. Here are some tips for protecting that exposed data

[Excerpted from "Strategies For Protecting Web-Facing Databases," a new report published this month in Dark Reading's Database Security Tech Center.]

What do recent database attacks have in common?Answer: in moste cases, the criminals used the Web as an attack vector. Web applications, by their very nature, expose your infrastructure to the public. And we have plenty of evidence that demonstrates that people will, for fun or profit, hack your databases.

So how do you keep Web-facing databases secure? Removing them from the Web would be the easy answer, but a system that does not serve a business function is worthless to the company. Companies push more features and functions to the Web to better serve their customers and, in turn, generate more revenue. That is the focus of their efforts.

There is no doubt that once an application is serving customers and making money, no one is willing to pull it out of service in the name of security. Revenue trumps database security, so it’s the job of security professionals to figure out how to secure databases with limited resources while keeping the business systems operational.

In practical terms, all applications and databases created today are designed to communicate over Web protocols -- as an option, if not the primary communications channel. And every Web application has a database that manages data and application "state." In essence, databases hold the record of all activity that has occurred up to now.

Some of you may be asking at this point, "Doesn’t the application protect the database?" or "Isn’t the database shielded behind the application?" The answer to both of these questions is "no."

Many IT administrators have considered databases safe, or at least less accessible to attack, because they sit "behind" the Web application that directly serves users. In reality, many attacks are passed directly to the database from the calling application. Unless the application was designed and built to cleanse user data before it reaches the database, it’s merely a gateway used by a remote attacker to hack into a database.

Applications only shield databases from specific -- or specific classes -- of attack if they were programmed to do so. Most applications are not coded to protect a database by default, so assume your databases are as exposed to bad actors as any other Web application.

For a detailed list of attacks and threats to Web-facing databases -- as well as a list of strategies for defending against those threats -- download the free report on protecting Web-facing databases.

Have a comment on this story? Please click "Add a Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message. Adrian Lane is a Security Strategist and brings over 25 years of industry experience to the Securosis team, much of it at the executive level. Adrian specializes in database security, data security, and secure software development. With experience at Ingres, Oracle, and ... 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 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.