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

3/14/2013
11:36 AM
Adrian Lane
Adrian Lane
Commentary
50%
50%

Database Security Operations

Process -- not tools -- is important

Meeting up with seasoned database security and IT operations teams always keeps me on my toes. The RSA Conference is one such event where I get to meet people who have been doing database security far longer than your average practitioner, and their perspective of the daily grind -- in the trenches -- is very different from my typical analyst inquiry on how to deploy a specific security technology.

To this group of veterans, the tools are secondary; they are only as good as the management process that leverages the tool to automate tasks. Get the process wrong and you end up doing more work, not less, regardless of automation. And if the process is not monitored, tasks -- security or otherwise -- don't get done at all. The lesson that was consistent among this group: Security needs to be part of dev-ops (development and operations teams), built into the process as part of the every day set of tasks to ensure basic quality.

Part of the reason for this is that security, if not implemented, is not something the average IT user notices. Don't do it, and no one complains, and no one notices. Well, until there is a breach. The second, and more selfish reason, is to preserve the sanity of the DBAs. There was only so much they could take on, so adherence to the process showed they were doing their job. It gave them a bar to measure against success or failure, and it limited the number of ad-hoc requests from other organizations. Defining what they would and would not do gives priority to tasks.

One thing clear from my experience is that unless security is systemic to the daily process, it won't work. It's a lesson learned from secure software development. No other security-related discipline is more at odds with productivity -- and the most likely to be set aside in favor of new feature development.

The example I cite most is the need to do security unit testing -- in essence, ensuring the code the developers send to QA does, in fact, meet minimum standards. If you actually require security as part of the hand-off requirement, then the work actually gets done. If you treat security as just another feature, then it must compete with more glamorous additions for attention. And any of you in software development know that, at the end of a waterfall development cycle, decisions are made as to what makes it into the build and what gets cut. Security usually loses to shiny, new toys.

The same holds true for database security. If it's not part of the dev-ops cycles, it gets sidelined in favor of other work. If patching is not a regular, regimented, and monitored process, it tends to sit on the sidelines. If you don't run predeployment validation -- making sure that configurations are accurate -- remove unwanted and unneeded modules, and close secondary avenues of database access like PUBLIC permissions or external procedures, then they hang around forever. Seldom does anyone find the time to go back and clean up a mess, as there is always more to do.

Next week I'll get back to setting up a basic database security program.

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
Newest First  |  Oldest First  |  Threaded View
News
FluBot Malware's Rapid Spread May Soon Hit US Phones
Kelly Sheridan, Staff Editor, Dark Reading,  4/28/2021
Slideshows
7 Modern-Day Cybersecurity Realities
Steve Zurier, Contributing Writer,  4/30/2021
Commentary
How to Secure Employees' Home Wi-Fi Networks
Bert Kashyap, CEO and Co-Founder at SecureW2,  4/28/2021
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
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-22675
PUBLISHED: 2021-05-07
The affected product is vulnerable to integer overflow while parsing malformed over-the-air firmware update files, which may allow an attacker to remotely execute code on SimpleLink Wi-Fi (MSP432E4 SDK: v4.20.00.12 and prior, CC32XX SDK v4.30.00.06 and prior, CC13X0 SDK versions prior to v4.10.03, C...
CVE-2021-22679
PUBLISHED: 2021-05-07
The affected product is vulnerable to an integer overflow while processing HTTP headers, which may allow an attacker to remotely execute code on the SimpleLink Wi-Fi (MSP432E4 SDK: v4.20.00.12 and prior, CC32XX SDK v4.30.00.06 and prior, CC13X0 SDK versions prior to v4.10.03, CC13X2 and CC26XX SDK v...
CVE-2020-14009
PUBLISHED: 2021-05-07
Proofpoint Enterprise Protection (PPS/PoD) before 8.17.0 contains a vulnerability that could allow an attacker to deliver an email message with a malicious attachment that bypasses scanning and file-blocking rules. The vulnerability exists because messages with certain crafted and malformed multipar...
CVE-2021-21984
PUBLISHED: 2021-05-07
VMware vRealize Business for Cloud 7.x prior to 7.6.0 contains a remote code execution vulnerability due to an unauthorised end point. A malicious actor with network access may exploit this issue causing unauthorised remote code execution on vRealize Business for Cloud Virtual Appliance.
CVE-2021-26122
PUBLISHED: 2021-05-07
LivingLogic XIST4C before 0.107.8 allows XSS via feedback.htm or feedback.wihtm.