<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>ERE-Security Blog &#187; Micro Governance</title>
	<atom:link href="http://ere-security.com/blog/tag/micro-governance/feed" rel="self" type="application/rss+xml" />
	<link>http://ere-security.com/blog</link>
	<description>NERC CIP, NERC CIP compliance, SCADA, SOX, digital certificates, harmonized TRA, privacy compliance audit, CSOX compliance audit,  it security audit, information security auditors, IT security auditors, web security auditors, information security audit, information security auditor, security policy document</description>
	<lastBuildDate>Sat, 21 May 2011 00:10:47 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>IT Security Micro Governance – A Practical Alternative Part 3</title>
		<link>http://ere-security.com/blog/it-security-micro-governance-%e2%80%93-a-practical-alternative-part-3</link>
		<comments>http://ere-security.com/blog/it-security-micro-governance-%e2%80%93-a-practical-alternative-part-3#comments</comments>
		<pubDate>Wed, 06 Jan 2010 04:35:32 +0000</pubDate>
		<dc:creator>Ron Lepofsky</dc:creator>
				<category><![CDATA[Information Security]]></category>
		<category><![CDATA[Internet Security]]></category>
		<category><![CDATA[Security Postings]]></category>
		<category><![CDATA[IT Security]]></category>
		<category><![CDATA[Micro Governance]]></category>

		<guid isPermaLink="false">http://ere-security.com/blog/?p=166</guid>
		<description><![CDATA[Last week’s blog described the problems caused by insufficient Governance and the root causes of this problem.  This week’s blog provides  an example situation which illustrates the steps for implementing IT security micro Governance to address a security threat.
Example Situation
The Problem Statement
1. A CIO of a fictitious company identifies weak identity management as a significant [...]]]></description>
			<content:encoded><![CDATA[<p>Last week’s blog described the problems caused by insufficient Governance and the root causes of this problem.  This week’s blog provides  an example situation which illustrates the steps for implementing IT security micro Governance to address a security threat.</p>
<h3><span style="color: #170cb4;"><strong>Example Situation</strong></span></h3>
<h3><strong><span style="color: #170cb4;">The Problem Statement</span></strong></h3>
<p>1. A CIO of a fictitious company identifies weak identity management as a significant risk to the privacy and integrity to corporate information as well as to SOX compliance.<br />
2. The problem has recently arisen due to several factors:<br />
* The external corporate auditors introduced new IT audit control points for monitoring unauthorized and attempted unauthorized accesses to critical servers and critical applications.<br />
* Corporate cost cutting has caused a reduction in the staff levels of the security administration group.<br />
* A cost cutting reorganization has dramatically changed employees’ roles and need to access various servers and applications.<br />
* The group of  recently terminated employees which include IT security administrators has  raised the potential threat of malicious activity from x-employees plus a diminished capacity for the corporation to adequately administer access privileges.<br />
3. There are insufficient funds for a comprehensive upgrade to the identity management infrastructure to ensure reasonable compliance for SOX.<br />
4. The problem is further obfuscated as the lack of any major security breach makes it appear to senior executives that there are no security threats.<br />
5. Nonexistent IT Governance means decision making about the new risk will be delayed until the next year’s budget cycle.</p>
<h3><span style="color: #170cb4;"><strong>IT micro Governance Solution</strong></span></h3>
<h3><span style="color: #170cb4;"> </span></h3>
<p>1. If the corporation does in fact have an IT Governance committee that is amenable to reacting quickly with micro Governance decisions, then the CIO can identify to the Governance committee the business risks relating to weak identity management.<br />
2. The governance committee works with the CIO to estimate the cost to the corporation in the event of a security event at $5,000,000 per incident.<br />
3. They build a business case modeled upon the chance of a security event occurring once per year.<br />
a. The CIO estimates the first year annual cost to technically mitigate the risk at $100,000 and $50,000 annually thereafter.<br />
b. The first year mitigation cost / annual loss expectation is $100,000 / $5,000,000 or 2% and 1% thereafter.<br />
c. The Governance committee decides the return is acceptable.<br />
4. The IT Governance committee formally creates a specific task force and IT micro Governance process to mitigate the identity management risk.<br />
5. They engage a third party advisor to expedite the process, so that an aggressive date of fully tested implementation is 6 months.<br />
6. They appoint virtual team leaders to manage each risk management process. The team leaders are comprised of two members of the IT Governance committee, the CIO, three members of the IT security team, 6 business line managers, a member of HR and a member of the CFO’s team. They also have external security consultants and auditors to assist with testing and evaluating the effectiveness of the new process.<br />
7. The virtual team leaders assign other employees to implement the project and to create an ongoing process to monitor, manage, and report on the proposed identity management process.<br />
8. The team creates a detailed project plan to complete the project.<br />
9. The third party consultants and auditors work with the team right from the beginning to design processes and mechanisms to test and report on the degree of success of the new identity management process.<br />
10. The virtual team and IT Governance committee creates a schedule for reporting / feedback / direction meetings as oversight for the new process, including:<br />
a. Evaluating the degree of success of the initial implementation.<br />
b. A subset of the virtual team continues to monitor and report to the Governance Committee.<br />
c. A third party with expertise in calculating IT security risk is assigned the task of re-evaluating the initial ROI or cost avoidance business model in terms of:<br />
i. Was risk correctly estimated?<br />
ii. Is there an ongoing evaluation of the degree of risk reduction?<br />
iii. Can the new process and its budget be integrated into IT security operations / administration. Can the virtual team be disbanded?</p>
<h3><span style="color: #ff0000;">Conclusion:  Keep it simple.</span></h3>
<p>Sources of Information &#8211; Governance Authorities<br />
* ISACA (Information Systems Audit and Control Association) www.isaca.org<br />
* ITGI (IT Governance Institute) www.itgi.org<br />
* Gartner Group www.gartner.com<br />
* IBM www-935.ibm.com/services/us/index.wss/offering/its/a1031003<br />
* SANS (SysAdmin, Audit, Network, Security Institute) www.sans.org/reading_room/whitepapers/casestudies/corporate_governance_and_information_security_1382<br />
* The IT Metrics and Productivity Institute  http://www.itmpi.org/default.aspx?pageid=198<br />
* MIT Sloan School of Management  http://web.mit.edu/cisr/working%20papers/cisrwp349.pdf</p>
<p>Have a secure week.</p>
<p>Regards, Ron Lepofsky, B.A. SC. (Mech Eng), CISSP<br />
ERE Information Security Auditors</p>
<p>www.ere-security.ca</p>
]]></content:encoded>
			<wfw:commentRss>http://ere-security.com/blog/it-security-micro-governance-%e2%80%93-a-practical-alternative-part-3/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>IT Security Micro Governance &#8211; A Practical Alternative Part 2</title>
		<link>http://ere-security.com/blog/it-security-micro-governance-a-practical-alternative-part-2</link>
		<comments>http://ere-security.com/blog/it-security-micro-governance-a-practical-alternative-part-2#comments</comments>
		<pubDate>Tue, 29 Dec 2009 21:06:04 +0000</pubDate>
		<dc:creator>Ron Lepofsky</dc:creator>
				<category><![CDATA[Information Security]]></category>
		<category><![CDATA[Internet Security]]></category>
		<category><![CDATA[Security Postings]]></category>
		<category><![CDATA[IT Security]]></category>
		<category><![CDATA[Micro Governance]]></category>

		<guid isPermaLink="false">http://ere-security.com/blog/?p=157</guid>
		<description><![CDATA[Last week’s blog introduced my concept of IT security micro Governance. This weeks installment covers the problems caused by insufficient Governance and the root causes of this problem.
Insufficient IT Governance Impedes the Security Team
In dynamic network environments, security issues can quickly appear where there are insufficient funds planned to mitigate new security risks. An active [...]]]></description>
			<content:encoded><![CDATA[<p>Last week’s blog introduced my concept of IT security micro Governance. This weeks installment covers the problems caused by insufficient Governance and the root causes of this problem.</p>
<h3><span style="color: #0000e0;">Insufficient IT Governance Impedes the Security Team</span></h3>
<p>In dynamic network environments, security issues can quickly appear where there are insufficient funds planned to mitigate new security risks. An active IT Governance process is invaluable to deal with such issues.</p>
<p>Insufficient IT Governance:<br />
* Slows decision making.<br />
* Inhibits communication of risk and associated potential financial loss between the IT Security. Team and executive management.<br />
* Inhibits attaining unplanned, sufficient IT security funding.<br />
Barriers to implementing IT Governance</p>
<p>Well known barriers to attaining IT governance are:<br />
* The all encompassing scope of any Governance is a daunting challenge to face.<br />
* Expensive.<br />
* Time consuming.<br />
* IT security risk can be very difficult to quantify.<br />
* The executives may find it difficult to request additional funds particularly where the IT security team has done an excellent job and there are no expensive security vulnerabilities.<br />
* A false sense of security makes cost justifying security budgets difficult.<br />
* A Governance committee may get bogged down over confusion arising between identifying the content of compliance frameworks with compliance objectives.<br />
* Turf wars over accepting / relegating ownership of responsibilities for various aspects of IT compliance.<br />
* Maintaining longevity of the IT Governance process.</p>
<h3><span style="color: #0000e0;">ITSecurity micro Governance as a Practical Alternative</span></h3>
<p>A simplified alternative to the barriers mentioned above creates a bite-sized micro process which will provide the following value to a corporate entity:<br />
* Minimizes the liability of executives with respect to their fiduciary responsibilities for IT Governance.<br />
* Facilitates communications between the Governance Body and the IT Security Team regarding cost justification of unplanned or insufficient budget.<br />
* Provides a regular opportunity for the Security Team to convey top priorities with requests for expedited executive authorization.<br />
* Provides a regular opportunity for executives to convey business priorities that affect IT related risk directly to those responsible for physically managing those risks.<br />
* Minimizes decision time and frustration levels by identifying bite sized issues.</p>
<h3><span style="color: #0000e0;">Steps to Implement IT Micro Governance</span></h3>
<p>1. IT Security should identify the top priority IT security risk(s) that require immediate decisions / funding by the executive team.<br />
2. Estimate the ROI or potential cost avoidance by mitigating the risk(s).<br />
3. Formally create a micro-Governance process to address the risk(s).<br />
4. Engage a third party advisor to expedite the process.<br />
5. Create a virtual (temporary) team to manage each risk management process.<br />
6. Assign other management and employees as appropriate to the virtual team.<br />
7. Identify a timeline to complete the project.<br />
8. Identify a mechanism to test the degree of success of the mitigation.<br />
9. Identify a timeline to report the degree of success back to the IT Governance Committee.<br />
10. Assess whether ROI or cost avoidance goals were sufficiently met. *<br />
11. Mandate longevity for the micro Governance process by directing the virtual team to continue monitoring the process and reporting to the Governance Committee.<br />
12. Integrate the process into the IT security operations / administration processes and disband the virtual team.</p>
<p>* It is difficult to obtain data that captures the prevention of a security threat based on a specific action taken. One empirical yet evidentiary based method is to compare the frequency of similar threats before and after mediation steps are implemented.</p>
<p>To assist with calculating IT security related, risk, ROI / cost avoidance, and residual risk, Governance Committees (and IT security professionals) can contract third party expertise in these matters.</p>
<p>Next week’s blog will be an example situation which illustrates the steps for implementing IT security micro Governance to address a security threat.</p>
<p>Have a secure week.</p>
<p>Regards, Ron Lepofsky, B.A. SC. (Mech Eng), CISSP<br />
ERE Information Security Auditor</p>
<p>www.ere-security.ca</p>
]]></content:encoded>
			<wfw:commentRss>http://ere-security.com/blog/it-security-micro-governance-a-practical-alternative-part-2/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

