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

2/12/2008
10:02 PM
George V. Hulme
George V. Hulme
Commentary
50%
50%

The Changing Role Of The CISO?

Just a few years ago, the chief information security officer's focus was to defend business-technology systems from the continuous barrage of viruses, worms, denials-of-service, and many other types of attacks that placed system availability and information at risk. For many, I suspect, this role has changed dramatically.

Just a few years ago, the chief information security officer's focus was to defend business-technology systems from the continuous barrage of viruses, worms, denials-of-service, and many other types of attacks that placed system availability and information at risk. For many, I suspect, this role has changed dramatically.It all started with the high-profile cases of corporate fraud, increases in identity theft, transaction fraud, and breaches of personally identifiable financial information. These ushered in a tsunami of state, federal, and industry regulations that purport to reduce corporate fraud and secure electronic information.

And yet we still have insider frauds the likes of the SocGen fraud and breaches like the TJX fiasco. But I digress.

All of these government and industry regulatory pressures affect nearly every organization. From Sarbanes-Oxley, which governs the accounting information of publicly traded companies, to the California Security Breach Information Act (SB 1386), which aims to give consumers adequate notice whenever specific financial account information is breached. As well as the final security rules for the Health Insurance Portability and Accountability Act (HIPAA). And then there's the credit card industry's PCI Data Security Standard that touches nearly every retailer.

I'm sure I'm forgetting a few dozen new regulations, or mandates. So where do organizations turn when they need all of the new policies and procedures in place to ensure these rules are enforced throughout their organization? Usually, it's the CISO.

So how has this changed the day-to-day life of the chief information security officer? Are you spending more time designing strategies to successfully answer an auditor's checklist? Or, are you working to ensure all of the custom applications designed in your organization are developed securely?

Are you trying to figure out more cost-effective ways to manage the barrage of internal controls your company has recently put into effect to grapple with Sarbanes-Oxley; or are you making sure each and every employee has the training they need keep their endpoints safe?

Let us know where the bulk of your attention goes nowadays. Is it combating regulatory mandates, or security threats?

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.