<?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>Secure Today &#187; risk</title>
	<atom:link href="http://www.securetoday.net/tag/risk/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.securetoday.net</link>
	<description>Protecting your own for the future</description>
	<lastBuildDate>Thu, 25 Feb 2010 16:25:11 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Proceed at your own RISK</title>
		<link>http://www.securetoday.net/2009/04/proceed-at-your-own-risk/</link>
		<comments>http://www.securetoday.net/2009/04/proceed-at-your-own-risk/#comments</comments>
		<pubDate>Sun, 26 Apr 2009 16:16:01 +0000</pubDate>
		<dc:creator>Zarex dela Cruz, CISSP</dc:creator>
				<category><![CDATA[IT Security]]></category>
		<category><![CDATA[Risk Management]]></category>
		<category><![CDATA[risk]]></category>
		<category><![CDATA[threats]]></category>
		<category><![CDATA[vulnerabilities]]></category>

		<guid isPermaLink="false">http://www.securetoday.net/?p=90</guid>
		<description><![CDATA[RISK is a very common word. In the IT World, it had been becoming more and more used not only within the management realms but also going down the end-users. Risk is a big deal when it comes to Security. More often, it is tied with a value or even worse, reputation. That&#8217;s why when [...]]]></description>
			<content:encoded><![CDATA[<p><img class="aligncenter size-full wp-image-91" title="risk" src="http://www.securetoday.net/wp-content/uploads/2009/07/risk.jpg" alt="risk" width="620" height="152" /><strong>RISK </strong>is a very common word. In the IT World, it had been becoming more and more used not only within the management realms but also going down the end-users. Risk is a big deal when it comes to Security. More often, it is tied with a value or even worse, reputation. That&#8217;s why when it comes to managing it, the most important aspect everyone should adhere to is senior management awareness and approval.</p>
<p>Let&#8217;s dive into the meaning of the word risk in IT Security world. The simplest way of putting it is:</p>
<blockquote>
<p style="text-align: center;"><strong>THREAT + <span style="color: #008000;">VULNERABILITY</span> = <span style="color: #ff0000;">RISK</span></strong></p>
</blockquote>
<p><em>A risk is the likelihood of a threat agent taking advantage of a vulnerability and the corresponding business impact.</em> (All-in-One CISSP, Risk Management; Shon Harris). Before expanding that meaning, let&#8217;s take a look at what threats and vulnerabilities are.</p>
<p>A threat, as we all know, is any potential danger. Threat agents are the medium that carry out the threat. So a threat  is someone or something that can identify a weakness and take advantage of it. For instance, if I know a website is running an application that is not written properly, I could exploit it to defaced it or to cause denial of service. In this case, I am a threat agent. My inappropriate actions are threat to this website.</p>
<p>The site&#8217;s buggy code is subject to exposure, which is its instance of being exposed to losses from a threat agent.</p>
<p>A vulnerability is a weakness in the infrastructure. And weakness is always represented by an absence or lack of ability to safeguard itself. So in our previous example, the poorly written website is a weakness. Without a proper safeguard in place to protect it, it is a vulnerability that a threat agent is ready to exploit.</p>
<p>Safeguard was mentioned earlier. This is the countermeasure that must be in place to prevent and mitigate the potential risk. Mitigating risk comes in many flavors, which we&#8217;ll try to cover them in brief details later.</p>
<p>So in brief, the order of concepts for all of these is:</p>
<blockquote><p><strong>Threat &gt; Exposure &gt; Vulnerability &gt; Countermeasure/Safeguard &gt; Risk</strong></p></blockquote>
<h2>RISK MANAGEMENT</h2>
<p>Risk Management involves: Risk Identification, Risk Analysis and Assessments, and Risk Mitigation. This is the process where identified group (most likely the Risk Management team) identify the risk (threats and vulnerabilities), analyze, and mitigate it to an acceptable level. The goal is to implement countermeasures to reduce the risk at a level that is acceptable to the security policy.</p>
<p><span id="more-90"></span>Identifying potential risks start in a good way of identifying vulnerabilities. Various vulnerability assessment tools are out there to assist security professional undertake this rigid tasks. Assets must be properly identified in this area. On one hand, another assets, which are the users, do lack of understanding about threats in particular, and security in general. So keep that in the scope that the users, who unfortunately, are the weakest link in security and their lack of knowledge are also risk. Having users understand the scope of security policy is a must.</p>
<p>After identifying vulnerabilities and threats, it&#8217;s time to quantify or qualify them. The Quantitative and Qualitative Risk Analysis approaches can be selected depending on the nature of the assets. Quantitative is a risk calculation where monetary value are assign to assets. Qualitative is through judging the intrinsic value of an asset.</p>
<p>Risk mitigation comes in after analyzing the risk. This is the time where you decide what to do with the risk based on the value of the asset and the actual loss if it is exposed. As a general rule, it is not recommended to spend more to protect an asset than it is worth. So if the cost to mitigate the risk outweigh the value of the asset, it is a good idea to accept the risk than to spend money less its worth. Next, let&#8217;s cover different options on deciding how to mitigate these risks.</p>
<h2>It&#8217;s too risky, are you sure?</h2>
<p><strong>RISK ACCEPTANCE</strong>.<em> Well, let&#8217;s just accept the risk</em>. This is when you decide to accept the risk and don&#8217;t do anything about it and chose to live with it. The reason is the cost to mitigate it is too high and the impact is too low. for example, if the cost of putting an IDS (Intrusion Detection System) in an environment is too high for the value of the total potential loss there, it may be safe just to accept the risk.</p>
<p><strong>RISK AVOIDANCE</strong>. <em>I wanna avoid the risk, let&#8217;s go somewhere else.</em> This is when management decide not to continue with the activity that is introducing the risk. For example, if users uses a particular email client that posses many risks around it, they can chose to mandate stop the use of this email client if there is not enough business need. They can go around by using a different email client that has less risks.</p>
<p><strong>RISK REDUCTION</strong>. <em>Okay, let&#8217;s implement what you were suggesting.</em> This is when you decide that a countermeasure will reduce the loss if an event occurs. This is the real risk mitigation. Earlier, users were mentioned as the weakest link, because of their lack of knowledge. A countermeasure for this is proper awareness and training. This approach will reduce the level of risk to business acceptable level. Implementing firewalls, IDS to where it is needed, antivirus are good risk reduction approaches.</p>
<p><strong>RISK TRANSFERENCE</strong>. <em>This is too much for me now, let&#8217;s give it to someone else.</em> This is when management choose to transfer the risk to somebody else. A good example is buying an insurance to handle the risk for you. Instead of you taking care of the risk, the insurance company will take care of the risk for you.</p>
<p><strong>RISK IGNORANCE</strong>. <em>Ignore it? Are you sure?</em> This is tricky, while it sounds easy and very tempting to take, this is NOT an acceptable risk mitigation strategy. Don&#8217;t ignore any risk, after all, risk sometimes spells RI$K.</p>
<p>Risk Management is important in Security. In an enterprise, where there are various and different assets, it could be very challenging. But the concept is relatively straightforward. In our homes, or daily normal users of computers, it could be in a different form and challenge. The gist of it is that, risk equates to value. And value has a cost. You need to do something to protect its value so that it is not compromised or lost.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.securetoday.net/2009/04/proceed-at-your-own-risk/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
