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.

Perimeter

2/16/2010
07:58 AM
Adrian Lane
Adrian Lane
Commentary
50%
50%

Measuring Database Security

How much does it cost to secure your database, and how do you calculate that? One of the more vexing problems in security is the lack of metrics models for measuring and optimizing security efforts. Without frameworks and metrics to measure the efficiency and effectiveness of security programs, it's difficult both to improve processes and to communicate our value to nontechnical decision makers.

How much does it cost to secure your database, and how do you calculate that? One of the more vexing problems in security is the lack of metrics models for measuring and optimizing security efforts. Without frameworks and metrics to measure the efficiency and effectiveness of security programs, it's difficult both to improve processes and to communicate our value to nontechnical decision makers."What's the ROI for this investment?" is a favorite question among by senior management and finance groups. It's a question that does not have an answer, and stymies the justification of spending time or purchasing tools to secure databases.

Itemizing costs and justifying efforts is a problem all IT departments have. Being able to assess costs, gauge time and resource requirements, and determine gaps is important in communicating project status with upper management. To address this community issue, Project Quant for Database Security was started. This is an open, community-driven, vendor-neutral effort with the models for database security free to the public.

The first step was to analyze how businesses go about securing their databases. We quickly discovered this is not a single process, but one that comprises of a dozen or more efforts. Worse, there really is no formal patch management, vulnerability assessment, or configurations management process for databases. With the goal to provide tangible metrics, we need to examine each of these efforts individually, breaking them into discrete tasks small enough to accurately assign quantitative metrics.

Building out individual processes for assessment, monitoring, auditing, and patching provided the granularity necessary. It allowed individual organization to mix and match processes, tailoring to their respective complexity, and assign time and resources that reflected their needs.

As with most open efforts, the more database and security professionals who participate, the better the results. And the more participating people and organizations, the better we can reflect DBA and IT efforts. Project Quant for database security is still under way, with the entire effort open to comments and critique. If you are interested in contributing to this effort, then you are invited to participate.

Adrian Lane is an analyst/CTO with Securosis LLC, an independent security consulting practice. Special to Dark Reading. 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

Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
Why Vulnerable Code Is Shipped Knowingly
Chris Eng, Chief Research Officer, Veracode,  11/30/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
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
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-16123
PUBLISHED: 2020-12-04
An Ubuntu-specific patch in PulseAudio created a race condition where the snap policy module would fail to identify a client connection from a snap as coming from a snap if SCM_CREDENTIALS were missing, allowing the snap to connect to PulseAudio without proper confinement. This could be exploited by...
CVE-2018-21270
PUBLISHED: 2020-12-03
Versions less than 0.0.6 of the Node.js stringstream module are vulnerable to an out-of-bounds read because of allocation of uninitialized buffers when a number is passed in the input stream (when using Node.js 4.x).
CVE-2020-26248
PUBLISHED: 2020-12-03
In the PrestaShop module "productcomments" before version 4.2.1, an attacker can use a Blind SQL injection to retrieve data or stop the MySQL service. The problem is fixed in 4.2.1 of the module.
CVE-2020-29529
PUBLISHED: 2020-12-03
HashiCorp go-slug before 0.5.0 does not address attempts at directory traversal involving ../ and symlinks.
CVE-2020-29534
PUBLISHED: 2020-12-03
An issue was discovered in the Linux kernel before 5.9.3. io_uring takes a non-refcounted reference to the files_struct of the process that submitted a request, causing execve() to incorrectly optimize unshare_fd(), aka CID-0f2122045b94.