Commentary

Mitch Irsfeld
 

Prediction No. 10: Continuous Controls, The Intersection of BPM, ECM And Event Monitoring

This final prediction for 2006 is a look at where the rubber will meet the road in the journey toward a sustainable, automated compliance architecture. Your goal is to create an environment of continuous controls, but what exactly is that? Continuous controls are something that analysts, consultants and auditors stress but, somehow, only vaguely describe. It will be your number one priority for compliance management but there is no silver bullet technology that gets you there. There are no pre-packaged tools or services that will give you continuous controls across the range of regulatory requirements and internal risk management practices that govern most businesses. But more than anything else, continuous controls will make everyone's life much easier in 2006. That means you'll have to get there the hard way, and if you haven't already started, 2006 may not be your year. I'm not talking against pre-packaged tools. The reason there are so many tools is that there are so many unique problems to address and you'll, no doubt, find some of them useful in your overall compliance and risk management environment. For a large organization to achieve continuous controls, however, they will need a way to monitor and report all events that break with accepted security, risk and compliance policies and then document any and all remediation efforts. Most continuous controls environments also provide a centralized view of the entire enterprise risk management landscape via tools we've come to call dashboards.

This final prediction for 2006 is a look at where the rubber will meet the road in the journey toward a sustainable, automated compliance architecture. Your goal is to create an environment of continuous controls, but what exactly is that? Continuous controls are something that analysts, consultants and auditors stress but, somehow, only vaguely describe. It will be your number one priority for compliance management but there is no silver bullet technology that gets you there.

There are no pre-packaged tools or services that will give you continuous controls across the range of regulatory requirements and internal risk management practices that govern most businesses. But more than anything else, continuous controls will make everyone's life much easier in 2006.


More Global CIO Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

That means you'll have to get there the hard way, and if you haven't already started, 2006 may not be your year. I'm not talking against pre-packaged tools. The reason there are so many tools is that there are so many unique problems to address and you'll, no doubt, find some of them useful in your overall compliance and risk management environment. For a large organization to achieve continuous controls, however, they will need a way to monitor and report all events that break with accepted security, risk and compliance policies and then document any and all remediation efforts. Most continuous controls environments also provide a centralized view of the entire enterprise risk management landscape via tools we've come to call dashboards.Building a continuous controls environment means integrating the monitoring of controls with all the sources of information that could possibly generate a risk event, in other words, every place on your network where information is stored or exchanged.

Some companies elect to build continuous controls into their overall business process management system. That's a huge commitment, but front-ended with a business intelligence engine and augmented with enterprise content management (ECM) that implements the COSO framework, a BPM system may be in the best position to achieve continuous controls across a broad range of requirements. Then you have to make sure it can perform real-time auditing, analytics, reporting and mitigation. And then you have to make sure that all the processes are repeatable, an enormous but necessary undertaking.

Few compliance requirements are so specific and unchanging that a single packaged tool will get the job done. And the task of continuous controls will call for the tools you choose to work together. In the end, it forces you to examine your entire chain of information, from transaction systems to production systems and communication systems. It would be shame not to leverage such retooling and analysis to improve efficiencies, productivity throughout the organization.

Your greatest challenge could be getting management to understand the need for and the benefits of a continuous controls environment. If you were one of the majority of IT managers that were merely given a deadline to become compliant and little or no extra budget to do so, the fact that you were able to patch together controls for your first audit means you get to do it all over again. And that's not a New Year that anyone wants to look forward to.

So there you have it. That makes 10 predictions for IT compliance in 2006. If you missed any of the previous nine, you can review them below:

Prediction No. 1: The shift to internal threat threat monitoring

Prediction No. 2: Manpower Reductions

Prediction No. 3: Lockdown On Customer Data

Prediction No. 4: Data Centralization

Prediction No. 5: New Content To Manage

Prediction No. 6: The IT Hand-Off Brings Focus On Cost

Prediction No. 7: SOX Still Takes The Blame

Prediction No. 8: SMBs Forced To Wear Their Compliance Hats

Prediction No. 9: The Watchword in 2006 Will Be Sustainability


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