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

1/24/2008
04:22 PM
George V. Hulme
George V. Hulme
Commentary
50%
50%

Hey Joe, What Are You Doing With That Resume In Your Hand?

A buddy of mine called today. He's (we'll call him Joe) chief security officer at a fairly large public company in the health field. I hadn't spoken with Joe in a while, and he was sounding somewhat down. "What's wrong, Joe?" I asked.

A buddy of mine called today. He's (we'll call him Joe) chief security officer at a fairly large public company in the health field. I hadn't spoken with Joe in a while, and he was sounding somewhat down. "What's wrong, Joe?" I asked."Work," he said with a sigh. "It's changed so much in the past few years. It's meetings and audit reports, and more meetings."

I knew that wasn't it. Joe is used to lots of meetings. And lots of reports.

He then went on to describe a rather grim condition, at least for someone trying to keep corporate systems secure.

The focus of his work is becoming more about compliance for compliance sake. It's more about internal controls, procedures, and keeping auditors happy. This, said Joe, is actually working to make his organization compliant, but less secure.

In fact, he explained, he spent a good part of last week rectifying a decent number of vulnerabilities in print servers. It was Joe's opinion that these vulnerabilities were of low concern and mitigated by good network segmentation and firewall policies. "We had a few, far more serious, things that had to be taken care of. But they were postponed because they weren't on the audit finding," he said.

I continued to listen as Joe went to on explain how over the past 18 months he's tried to integrate security and compliance efforts, as a way to keep systems secure, compliant, and cut operational costs. He then listed a number of fires his security teams and the operation folks had to put out. Fires that kept him, among other managers, from getting to the higher level of governance they envisioned. These fires, more often than not, were lit by audit reports.

"Why don't you just go with it and deliver what the organization and auditors want?" I said.

"It's my job, and probably my career, when something goes wrong," he replied.

I keyed in on his use of the word "when" rather than "if," especially because Joe, more often than myself, sees the glass as half-full.

"E-mail me your resumé, I'll be happy to give it a read and call you later this evening with my thoughts," I said.

After I hung up I thought about this for a while. And if Joe's company really wanted to be secure and compliant -- and I mean in a long-term and sustainable way -- it would listen a bit more often to Joe and a little less to the auditors.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Stop Defending Everything
Kevin Kurzawa, Senior Information Security Auditor,  2/12/2020
Small Business Security: 5 Tips on How and Where to Start
Mike Puglia, Chief Strategy Officer at Kaseya,  2/13/2020
5 Common Errors That Allow Attackers to Go Undetected
Matt Middleton-Leal, General Manager and Chief Security Strategist, Netwrix,  2/12/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
6 Emerging Cyber Threats That Enterprises Face in 2020
This Tech Digest gives an in-depth look at six emerging cyber threats that enterprises could face in 2020. Download your copy today!
Flash Poll
How Enterprises Are Developing and Maintaining Secure Applications
How Enterprises Are Developing and Maintaining Secure Applications
The concept of application security is well known, but application security testing and remediation processes remain unbalanced. Most organizations are confident in their approach to AppSec, although others seem to have no approach at all. Read this report to find out more.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-5613
PUBLISHED: 2020-02-18
In FreeBSD 12.0-RELEASE before 12.0-RELEASE-p13, a missing check in the ipsec packet processor allows reinjection of an old packet to be accepted by the ipsec endpoint. Depending on the higher-level protocol in use over ipsec, this could allow an action to be repeated.
CVE-2020-7450
PUBLISHED: 2020-02-18
In FreeBSD 12.1-STABLE before r357213, 12.1-RELEASE before 12.1-RELEASE-p2, 12.0-RELEASE before 12.0-RELEASE-p13, 11.3-STABLE before r357214, and 11.3-RELEASE before 11.3-RELEASE-p6, URL handling in libfetch with URLs containing username and/or password components is vulnerable to a heap buffer over...
CVE-2019-10792
PUBLISHED: 2020-02-18
bodymen before 1.1.1 is vulnerable to Prototype Pollution. The handler function could be tricked into adding or modifying properties of Object.prototype using a __proto__ payload.
CVE-2019-10793
PUBLISHED: 2020-02-18
dot-object before 2.1.3 is vulnerable to Prototype Pollution. The set function could be tricked into adding or modifying properties of Object.prototype using a __proto__ payload.
CVE-2019-10794
PUBLISHED: 2020-02-18
All versions of component-flatten are vulnerable to Prototype Pollution. The a function could be tricked into adding or modifying properties of Object.prototype using a __proto__ payload.