Commentary

George Hulme
 

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.


More Security Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

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?


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links