<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearchrss/1.0/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0"><channel><atom:id>tag:blogger.com,1999:blog-244710282852357590</atom:id><lastBuildDate>Sun, 03 Aug 2008 21:26:32 +0000</lastBuildDate><title>practical risk management</title><description /><link>http://www.security-works.com/blog/</link><managingEditor>noreply@blogger.com (Bryan)</managingEditor><generator>Blogger</generator><openSearch:totalResults>34</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" href="http://feeds.feedburner.com/PracticalRiskManagement" type="application/rss+xml" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com" /><item><guid isPermaLink="false">tag:blogger.com,1999:blog-244710282852357590.post-6528182893552537340</guid><pubDate>Mon, 21 Jul 2008 21:34:00 +0000</pubDate><atom:updated>2008-07-21T16:43:43.223-05:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">it-grc</category><category domain="http://www.blogger.com/atom/ns#">it risk</category><category domain="http://www.blogger.com/atom/ns#">risk</category><category domain="http://www.blogger.com/atom/ns#">iso 27001</category><category domain="http://www.blogger.com/atom/ns#">grc</category><category domain="http://www.blogger.com/atom/ns#">ISO</category><category domain="http://www.blogger.com/atom/ns#">security</category><category domain="http://www.blogger.com/atom/ns#">security metric</category><category domain="http://www.blogger.com/atom/ns#">iso 17799</category><title>Seven steps to managing IT Risk</title><description>Came across this &lt;a href="http://www.pmportal.co.uk/content.asp?id=1812"&gt;overview read from a Gartner&lt;/a&gt; research note recently.  It lays out seven recommended steps managing risk. &lt;br /&gt;&lt;br /&gt;&lt;ul&gt;&lt;li&gt;Implement a framework for risk assessment and mapping.&lt;/li&gt;&lt;li&gt;Establish the responsibilities of risk managers with their areas of responsibility.&lt;/li&gt;&lt;li&gt;Identify and define the risks to which the business is exposed and what constitutes a risk event or "near miss" so that incidents can be mapped to specific risks.&lt;/li&gt;&lt;li&gt;Determine the threat level, and focus on those risks with the highest impact on performance.&lt;/li&gt;&lt;li&gt;Establish levels of controls for processes commensurate with the perceived threat.&lt;/li&gt;&lt;li&gt;Record and retain risk incident and near-miss information.&lt;/li&gt;&lt;li&gt;Conduct periodic risk assessments to determine changes in the operations risk profile and assess control performance.&lt;/li&gt;&lt;/ul&gt;Great advice.  These seven steps are precisely what IT-GRC solutions should help an Enterprise accomplish.  They provide the construct (aka think configuration wizard) for establishing and maintaining a quality risk management program.   If you have on your company priority list advancing the the risk mitigation/management capabilities or if you've recently been burned, take the time and check out some of our new product demonstration videos.  We strive to be transparent around what we offer with our software.  That's why our marketing isn't really "marketing" it's live product in action.  &lt;a href="http://security-works.com/metrics.html"&gt;Come check it out&lt;/a&gt;.&lt;img src="http://feeds.feedburner.com/~r/PracticalRiskManagement/~4/aoCfEo-FnPM" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/PracticalRiskManagement/~3/aoCfEo-FnPM/seven-steps-to-managing-it-risk.html</link><author>noreply@blogger.com (Ryan Shopp)</author><feedburner:origLink>http://www.security-works.com/blog/2008/07/seven-steps-to-managing-it-risk.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-244710282852357590.post-5706056588508961630</guid><pubDate>Sat, 31 May 2008 21:35:00 +0000</pubDate><atom:updated>2008-08-03T16:26:32.677-05:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">it grc</category><category domain="http://www.blogger.com/atom/ns#">it-grc</category><category domain="http://www.blogger.com/atom/ns#">it risk</category><category domain="http://www.blogger.com/atom/ns#">risk</category><category domain="http://www.blogger.com/atom/ns#">grc</category><title>So now everyone is an IT GRC vendor</title><description>As a marketeer for a technology company, you work really hard to tease out the key points of differentiation and attempt to coin a segment that defines your being.  IT-GRC (short for Information Technology Governance, Risk &amp;amp; Compliance) is a term that started gaining momentum about a year ago.  At that time Gartner, Forrester, EMA and other research analyst firms started using it to describe exactly what Securityworks does.  Next thing you know customers are achieving tangible results from these solutions and the press begins writing articles about it.&lt;br /&gt;&lt;br /&gt;Then, along comes tangential segments that do 20-30% of what we do...now all of a sudden they are "IT-GRC" vendors since it's the new "hot" term.&lt;br /&gt;&lt;br /&gt;Well, after all that hard work I have to simply say I love the candid &lt;a href="http://www.sysmannews.com/content/article.aspx?ArticleID=32188"&gt;article &lt;/a&gt;from Alex Handy over at Systems Management News.  A couple quotes that say it perfectly...&lt;br /&gt;&lt;br /&gt;&lt;snip&gt;&lt;br /&gt;&lt;span id="ctl00_content_PlaceHolder_articleBody_Label" class="arial_14_16 normalLink"&gt;When Jonathan Penn, research director at Forrester, walked around April's RSA conference, he was appalled by what he saw. “The vendors are destroying what's a very useful approach by claiming for themselves. If you're not an ITGRC vendor, just shut up,” said Penn.&lt;br /&gt;&lt;br /&gt;&lt;/span&gt;&lt;span id="ctl00_content_PlaceHolder_articleBody_Label" class="arial_14_16 normalLink"&gt;“ITGRC is an incredibly valuable approach to security,” said Penn. “What I like about it is it's a good way to structure what IT does. But it's much more a practice than a product. The tools that manage things at a high level, those are the ITGRC products.”&lt;/span&gt;&lt;br /&gt;&lt;span id="ctl00_content_PlaceHolder_articleBody_Label" class="arial_14_16 normalLink"&gt;&lt;/span&gt;&lt;/snip&gt;&lt;br /&gt;&lt;br /&gt;We completely agree.  No single product can encompass IT-GRC.  Our product is a good foundation but what's so very important is the people, process and technology that mold around our product.  This includes the integration points with other security products into a unified view of your overall security program, not those product calling themselves IT-GRC.&lt;img src="http://feeds.feedburner.com/~r/PracticalRiskManagement/~4/yw4CZvUaLQw" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/PracticalRiskManagement/~3/yw4CZvUaLQw/so-now-everyone-is-it-grc-vendor.html</link><author>noreply@blogger.com (Ryan Shopp)</author><feedburner:origLink>http://www.security-works.com/blog/2008/06/so-now-everyone-is-it-grc-vendor.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-244710282852357590.post-4973197044453680072</guid><pubDate>Thu, 24 Apr 2008 21:32:00 +0000</pubDate><atom:updated>2008-04-24T17:08:56.734-05:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">it grc</category><category domain="http://www.blogger.com/atom/ns#">it-grc</category><category domain="http://www.blogger.com/atom/ns#">ITIL</category><category domain="http://www.blogger.com/atom/ns#">CobiT</category><category domain="http://www.blogger.com/atom/ns#">it risk</category><category domain="http://www.blogger.com/atom/ns#">risk</category><category domain="http://www.blogger.com/atom/ns#">grc</category><category domain="http://www.blogger.com/atom/ns#">security</category><category domain="http://www.blogger.com/atom/ns#">security metric</category><title>Evolution of IT Security to Risk; driving IT GRC acceptance?</title><description>Great summary by Michael Rasmussen of Corporate Integrity on the &lt;a href="http://corp-integrity.blogspot.com/2008/04/2008-grc-drivers-trends-market.html"&gt;2008 State of the GRC market&lt;/a&gt; was posted earlier this month.&lt;br /&gt;&lt;br /&gt;I believe the title of one of the sections itself summarizes one of the biggest benefits of GRC, "GRC is About Organization Collaboration."  He is 100% correct from my perspective - independent of the people, technology and process - GRC solutions are about using software automation to help enterprises collaborate to reduce their exposure to the big three buzz areas each of those letters in the acronym represent (Governance, Risk, Compliance).&lt;br /&gt;&lt;br /&gt;Now, GRC solutions can't and won't solve these problems alone.  They are part of an overall ecosystems of technical control products, best practice processes and people communication/expertise.  You still need your Vulnerability, SIEM, IDS/IPS, Firewalls and other security products.  You still need your COBIT, ISO, ITIL and other best practice processes.  And of course, you still need the people who should know the overall business goals and priorities and then apply their expertise on how IT can help achieve those goals.  GRC as mentioned before is the organization collaboration construct that can successfully bring all these complex areas together into a tight and cohesive Governance, Risk and Compliance strategy.&lt;br /&gt;&lt;br /&gt;Another article I came across starts to highlight how some organizations are starting to elevate beyond operational security to strategic risk centric in culture.  Tim Wilson over at Dark Reading just put out this great write-up yesterday titled; &lt;a href="http://www.darkreading.com/document.asp?doc_id=151738"&gt;Market's Message to Security Pros: Adapt or Die&lt;/a&gt;. &lt;br /&gt;&lt;br /&gt;-snip-&lt;br /&gt;&lt;span&gt;&lt;span&gt;"...the question now is not how precarious the security manager's job is, but what it may evolve into, Schmidt observed. "As it becomes more about risk, security is not necessarily an IT problem. More and more, you see companies creating positions such as chief risk officer, who may report to a chief operating officer, and in some cases, the CSO might report to the [risk officer]."&lt;br /&gt;-snip-&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;This trend points directly at GRC solutions that can provide the common construct to help all aspects of the organization collaborate.  A decent analogy may be what ERP was to the CFO,  GRC is to the CRO.&lt;br /&gt;&lt;br /&gt;One last article that also points towards the trend around moving operational security tasks back into IT operations and thus security analysts evolving into internal Risk Consultants to the IT organization would be this &lt;a href="http://srmsblog.burtongroup.com/2008/04/operationalizin.html"&gt;blog from Trent Henry over at Burton Group&lt;/a&gt;.  Once these "Risk Consultants" are created, GRC provides the collaborative platform to conduct their more strategic initiatives mentioned; policy, risk &amp;amp; compliance monitoring, assessment program development, etc.&lt;img src="http://feeds.feedburner.com/~r/PracticalRiskManagement/~4/ipcgzDA6g38" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/PracticalRiskManagement/~3/ipcgzDA6g38/evolution-of-it-security-to-risk.html</link><author>noreply@blogger.com (Ryan Shopp)</author><feedburner:origLink>http://www.security-works.com/blog/2008/04/evolution-of-it-security-to-risk.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-244710282852357590.post-4832163538818457380</guid><pubDate>Tue, 08 Apr 2008 18:41:00 +0000</pubDate><atom:updated>2008-04-08T13:49:03.395-05:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">it grc</category><category domain="http://www.blogger.com/atom/ns#">it-grc</category><category domain="http://www.blogger.com/atom/ns#">grc</category><category domain="http://www.blogger.com/atom/ns#">compliance survey</category><title>Circumventing Enterprise Security Policies</title><description>&lt;a href="http://www.darkreading.com/document.asp?doc_id=150112"&gt;Interesting article&lt;/a&gt; on how employees are circumventing IT Security Department policies. &lt;br /&gt;&lt;br /&gt;This of course as we know exposes the company to IT GRC concerns (Governance, Risk &amp;amp; Compliance).  A couple hard numbers that jumped out at me.&lt;br /&gt;&lt;br /&gt;&lt;span&gt;&lt;span&gt;"80 percent of the enterprises are supporting proxy applications, such as KProxy or CGI proxies, which mask the user's identity and surfing habits from IT monitoring tools."&lt;br /&gt;&lt;br /&gt;&lt;/span&gt;&lt;/span&gt;&lt;span&gt;&lt;span&gt;:...half of the enterprises studied by Palo Alto are supporting Tor or other methods for encrypted "tunneling" through the corporate network. Tunneling enables the user to bypass IT traffic enforcement mechanisms."&lt;br /&gt;&lt;br /&gt;A comprehensive security policy starts from the top down with an IT-GRC solution.  It then incorporates all the scoring, controls and assessment automation products into a unified view to help expose situations like those identified in this study.  Once exposed and the risks understood, the priorities can be set to help quickly resolve these issues.&lt;br /&gt;&lt;/span&gt;&lt;/span&gt;&lt;img src="http://feeds.feedburner.com/~r/PracticalRiskManagement/~4/LFGQFY1qm0w" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/PracticalRiskManagement/~3/LFGQFY1qm0w/circumventing-enterprise-security.html</link><author>noreply@blogger.com (Ryan Shopp)</author><feedburner:origLink>http://www.security-works.com/blog/2008/04/circumventing-enterprise-security.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-244710282852357590.post-3502193604858000581</guid><pubDate>Mon, 24 Mar 2008 13:34:00 +0000</pubDate><atom:updated>2008-03-24T09:19:27.288-05:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">it grc</category><category domain="http://www.blogger.com/atom/ns#">non-technical</category><category domain="http://www.blogger.com/atom/ns#">it-grc</category><category domain="http://www.blogger.com/atom/ns#">it risk</category><category domain="http://www.blogger.com/atom/ns#">risk</category><category domain="http://www.blogger.com/atom/ns#">grc</category><category domain="http://www.blogger.com/atom/ns#">security</category><category domain="http://www.blogger.com/atom/ns#">security metric</category><category domain="http://www.blogger.com/atom/ns#">non-technical controls</category><title>Nice GRC write-up and how it relates to log management initiatives</title><description>Anton wrote a nice piece, called "&lt;a href="http://www.scmagazineus.com/Unified-GRC-Replacing-a-piecemeal-response-to-compliance/article/108090/"&gt;Unified GRC: Replacing a piecemeal response to compliance&lt;/a&gt;" for SC Magazine defining GRC and how it fits together with other areas of security and prevention management.  The article, as expected, has a major slant toward Log Management, but it is a very good summary that also highlights other key capabilities / areas important to GRC. &lt;br /&gt;&lt;br /&gt;Even though most security vendors are marketing IT Risk Management, many customers are beginning to realize there is this new breed of software products that compliments your vulnerability, log, configuration security solutions.  These IT GRC products normalize all the various regulatory or standardization controls into a common framework and then pull scores/results/data from these products into that model to go along-side data gathered from controls that can't be instrumented with software (e.g., people, processes, procedures, physical).  &lt;a href="http://www.security-works.com/blog/2007/12/users-continue-to-ignore-security.html"&gt;As mentioned in previous posts&lt;/a&gt;, without this other side of the coin you're not getting a complete picture of risk/compliance/governance. &lt;br /&gt;&lt;br /&gt;So if you you've already made investments in these other products but need something to pull them together into a unified view and are looking to get the complete picture, come check out IT GRC.&lt;img src="http://feeds.feedburner.com/~r/PracticalRiskManagement/~4/l8ZEfgA0XNo" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/PracticalRiskManagement/~3/l8ZEfgA0XNo/nice-grc-write-up-and-how-it-relates-to.html</link><author>noreply@blogger.com (Ryan Shopp)</author><feedburner:origLink>http://www.security-works.com/blog/2008/03/nice-grc-write-up-and-how-it-relates-to.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-244710282852357590.post-8781229859487041395</guid><pubDate>Mon, 17 Mar 2008 15:35:00 +0000</pubDate><atom:updated>2008-03-17T10:48:36.966-05:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">it grc</category><category domain="http://www.blogger.com/atom/ns#">it-grc</category><category domain="http://www.blogger.com/atom/ns#">it risk</category><category domain="http://www.blogger.com/atom/ns#">grc</category><category domain="http://www.blogger.com/atom/ns#">security</category><title>IT GRC is the next evolution for the Enterprise Security Organization</title><description>Great write-up and perspectives from the GRC guru, Michael Rasmussen; &lt;a href="http://corp-integrity.blogspot.com/2008/03/what-is-it-grc.html"&gt;What is IT GRC?&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;snip&gt;-snip-&lt;br /&gt;Interestingly enough, I was at an event last week of a dozen senior IT executives and we discussed this concept of IT-GRC.  These were all Fortune 500 firms.  Going around the room each was &lt;span style="font-weight: bold;"&gt;spending on average 5-6% of their IT budget this year on IT-GRC&lt;/span&gt;. A few were lower than this in the 2-3% range while one, who was significantly working on their IT-GRC strategy, was spending about 12% of their IT budget on IT-GRC.&lt;br /&gt;&lt;snip&gt;-/snip-&lt;br /&gt;&lt;br /&gt;Bottom line, the solutions in the IT-GRC space continue to mature and evolve, BUT the truth is - they can and will help save Fortune 500 IT Security organizations money through automation today!  There is no reason a Fortune 500 company should be spending this much of their IT budget on IT-GRC when these products today significantly reduce the amount of manual labor (consultants) performing these governance, risk &amp;amp; compliance duties.&lt;/snip&gt;&lt;/snip&gt;&lt;img src="http://feeds.feedburner.com/~r/PracticalRiskManagement/~4/2T5GI1u393A" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/PracticalRiskManagement/~3/2T5GI1u393A/it-grc-is-next-evolution-for-enterprise.html</link><author>noreply@blogger.com (Ryan Shopp)</author><feedburner:origLink>http://www.security-works.com/blog/2008/03/it-grc-is-next-evolution-for-enterprise.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-244710282852357590.post-8743839718053222701</guid><pubDate>Mon, 10 Mar 2008 13:37:00 +0000</pubDate><atom:updated>2008-03-10T09:21:59.929-05:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">it risk</category><category domain="http://www.blogger.com/atom/ns#">risk</category><category domain="http://www.blogger.com/atom/ns#">iso 27001</category><category domain="http://www.blogger.com/atom/ns#">grc</category><category domain="http://www.blogger.com/atom/ns#">security</category><category domain="http://www.blogger.com/atom/ns#">security metric</category><category domain="http://www.blogger.com/atom/ns#">controls</category><title>Great tutorial on Information Security Program Metrics</title><description>While reading a blog posting this morning I came across a great set of slides called &lt;a href="http://geer.tinho.net/measuringsecurity.tutorial.pdf"&gt;"Measuring Security."&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Slide 15 nails what are the questions security programs should answer on the head...&lt;br /&gt;How secure am I?&lt;br /&gt;Am I better off than this time last year?&lt;br /&gt;Am I spending the right amount of money?&lt;br /&gt;How do I compare to my peers?&lt;br /&gt;What risk transfer options do I have?&lt;br /&gt;&lt;br /&gt;Slide 36 has a great quote on "Risk Management"&lt;br /&gt;The essence of risk management lies in maximizing the areas where we have some control over the outcome, while minimizing the areas where we have absolutely no control over the outcomes and the linkage between effect and cause is hidden from us.&lt;br /&gt;&lt;br /&gt;The next 300 slides is a ton of background detail...overkill until your really ready to dig in.  I would simply recommend for now jumping to slide 402 to get to the punchline; here are some of the recommended metrics:&lt;br /&gt;&lt;br /&gt;• Cost of security per transaction&lt;br /&gt;• DoS and other attack downtimes&lt;br /&gt;• Data flow per transaction &amp;amp; per source&lt;br /&gt;• Budget correlation with risk measures&lt;br /&gt;• Comparison with like firms&lt;br /&gt;• Percentage of critical systems under DR plan&lt;br /&gt;• Percentage of systems obeying ______ policy&lt;br /&gt;• MTBF &amp;amp; MTTR for security incidents&lt;br /&gt;• Number of security team consultations&lt;br /&gt;• Latency to obey ______ change orders&lt;br /&gt;• Percentage of job reviews involving security&lt;br /&gt;• Percentage of security workers with training&lt;br /&gt;• Ratio of b.u. security staff to central staff&lt;br /&gt;• New system timely security consultations&lt;br /&gt;• Percentage of programs with budgeted security&lt;br /&gt;• Percentage of SLAs with security standards&lt;br /&gt;• Percentage of tested external-facing applications&lt;br /&gt;• Number of non-employees with access&lt;br /&gt;• Percentage of data secure-by-default&lt;br /&gt;• Percentage of customer data outside data center&lt;br /&gt;&lt;br /&gt;Where all this detail is extremely important, the beautiful thing about what Securityworks offers is it has built a method to normalize any/all metrics into a single score.  Think of it as your grade point average where you then have the ability to drill-down from the top and see how your doing for each subject, on each test, homework assignment, etc.&lt;img src="http://feeds.feedburner.com/~r/PracticalRiskManagement/~4/alt5w7OAEVc" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/PracticalRiskManagement/~3/alt5w7OAEVc/great-tutorial-on-information-security.html</link><author>noreply@blogger.com (Ryan Shopp)</author><feedburner:origLink>http://www.security-works.com/blog/2008/03/great-tutorial-on-information-security.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-244710282852357590.post-578626573587193945</guid><pubDate>Mon, 03 Mar 2008 13:51:00 +0000</pubDate><atom:updated>2008-03-03T08:18:59.153-06:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">it grc</category><category domain="http://www.blogger.com/atom/ns#">non-technical</category><category domain="http://www.blogger.com/atom/ns#">it-grc</category><category domain="http://www.blogger.com/atom/ns#">compliance</category><category domain="http://www.blogger.com/atom/ns#">it risk</category><category domain="http://www.blogger.com/atom/ns#">grc</category><category domain="http://www.blogger.com/atom/ns#">security</category><category domain="http://www.blogger.com/atom/ns#">non-technical controls</category><category domain="http://www.blogger.com/atom/ns#">controls</category><title>Going beyond technical security controls</title><description>Anton last week had this great write-up in ComputerWorld, &lt;a href="http://www.computerworld.com/action/article.do?command=printArticleBasic&amp;amp;articleId=9065202"&gt;"Five Basic Mistakes of Security Policy,"&lt;/a&gt; that hits the 5 basics that so many busy executives look past when leading a security organization.&lt;br /&gt;&lt;br /&gt;&lt;ol&gt;&lt;li&gt;Not having a policy&lt;/li&gt;&lt;li&gt;Not updating the policy&lt;/li&gt;&lt;li&gt;Not tracking compliance with the policy&lt;/li&gt;&lt;li&gt;Having a "tech only" policy&lt;/li&gt;&lt;li&gt;Having a large, unwieldy policy&lt;/li&gt;&lt;/ol&gt;&lt;br /&gt;One of the biggest we see every day is #4.  Most  enterprises have some policy in place that  they update (typically annually before a pending audit).  Their current compliance tracking is provided by one or more software products that unfortunately don't have the full picture.&lt;br /&gt;&lt;br /&gt;The reason why comes down to #4.  Traditionally, enterprises have thrown either a vulnerability scanner, security event/log manager or another security software application at a list of IP addressable assets...generate a few reports...and hope they have things covered.&lt;br /&gt;&lt;br /&gt;The truth be told, this misses so much of the full picture (&lt;a href="http://www.security-works.com/blog/2007/12/users-continue-to-ignore-security.html"&gt;over 50% per previous blog posts&lt;/a&gt;) that even the internal or external auditors don't have enough time to do a comprehensive review.  The goal of those auditors is not a "witch hunt," it's suppose to be to protect the company!  So what happens is each year, things get more and more detailed (which is good) as findings from the prior year are addressed allowing them to "peel the onion" back another layer.&lt;br /&gt;&lt;br /&gt;This is why we are seeing the emergence of the IT GRC market that compliments and extends these products you point at IP addressable assets.  These solutions use automation techniques to assess security controls around things that are not IP addressable (e.g., people, processes, facilities).  The other need these products are offering is a normalized, unified view of the entire security program.  Leveraging scoring from other products, they finally deliver the possibility of 100% visibility into the posture of your entire IT security, risk or compliance program.&lt;img src="http://feeds.feedburner.com/~r/PracticalRiskManagement/~4/TnYmNs-_v5A" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/PracticalRiskManagement/~3/TnYmNs-_v5A/going-beyond-technical-security.html</link><author>noreply@blogger.com (Ryan Shopp)</author><feedburner:origLink>http://www.security-works.com/blog/2008/03/going-beyond-technical-security.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-244710282852357590.post-6279780990035304826</guid><pubDate>Mon, 25 Feb 2008 14:28:00 +0000</pubDate><atom:updated>2008-02-25T09:30:01.900-06:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">it grc</category><category domain="http://www.blogger.com/atom/ns#">non-technical</category><category domain="http://www.blogger.com/atom/ns#">it-grc</category><category domain="http://www.blogger.com/atom/ns#">it risk</category><category domain="http://www.blogger.com/atom/ns#">risk</category><category domain="http://www.blogger.com/atom/ns#">iso 27001</category><category domain="http://www.blogger.com/atom/ns#">grc</category><category domain="http://www.blogger.com/atom/ns#">ISO</category><category domain="http://www.blogger.com/atom/ns#">security</category><category domain="http://www.blogger.com/atom/ns#">non-technical controls</category><category domain="http://www.blogger.com/atom/ns#">iso 17799</category><title>Top 3 conclusions about IT Risk Management we like hearing</title><description>I read a nice summary of a recent Symantec 40 page survey on IT Risk Management and felt compelled to share the links and highlights that jump out.  Symantec was recently noted as a &lt;a href="http://www.security-works.com/blog/2008/02/gartner-it-grc-predictions.html"&gt;leader in IT-GRC per this Gartner report&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;The summary I read was posted by &lt;a href="http://www.itsecurity.com/features/risk-management-myths-realities/"&gt;John Edwards over at ITSecurity.com.&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Here are the conclusions that grabbed our eye:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;Businesses would be far better served if they viewed security as an IT risk management element that can be addressed alongside other critical elements, such as availability, performance and compliance.&lt;/li&gt;&lt;li&gt;Technology alone can't mitigate IT risk. While technology plays a critical role in IT risk mitigation, balanced controls and frameworks are also necessary in order to provide complete risk management capabilities.&lt;/li&gt;&lt;li&gt;Management should consider implementing a continuous risk assessment process.&lt;/li&gt;&lt;/ul&gt;&lt;img src="http://feeds.feedburner.com/~r/PracticalRiskManagement/~4/F845jbo6zUU" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/PracticalRiskManagement/~3/F845jbo6zUU/top-3-conclusions-about-it-risk.html</link><author>noreply@blogger.com (Ryan Shopp)</author><feedburner:origLink>http://www.security-works.com/blog/2008/02/top-3-conclusions-about-it-risk.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-244710282852357590.post-3545779830103847669</guid><pubDate>Wed, 20 Feb 2008 14:57:00 +0000</pubDate><atom:updated>2008-02-20T09:10:24.090-06:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">it grc</category><category domain="http://www.blogger.com/atom/ns#">it-grc</category><category domain="http://www.blogger.com/atom/ns#">compliance</category><category domain="http://www.blogger.com/atom/ns#">grc</category><category domain="http://www.blogger.com/atom/ns#">compliance survey</category><title>PCI Compliance not going away - 42% not compliant</title><description>My inbox, like yours, is filled with numerous advertisements and spam on a daily basis, but this one actually grabbed my attention!  It started out by saying;&lt;br /&gt;&lt;br /&gt;"according to VISA, 42% of large and medium-sized US merchants did not reach their respective PCI compliance deadlines.  The penalty of non-compliance is merchants incur monthly fines (up to $25,000) until they meet and sustain data security compliance requirements."&lt;br /&gt;&lt;br /&gt;Now that is some attention grabbing marketing and I plan to be on that &lt;a href="http://presentations.inxpo.com/Shows/TechTarget/03-12-08/Registration/home.htm"&gt;virtual seminar.&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Almost half (and that's not a stacked number including small US merchants) is a very surprising number.  I looked around trying to find information behind the survey results but to no avail, so I'll be listening on the call for some details and facts to back it up.  Being that our IT GRC solution helps ensure that an enterprise is completely compliant with any regulation, I would like to hear what the top 2 or 3 reasons are they aren't yet compliant to see if they map up to what we are hearing.&lt;img src="http://feeds.feedburner.com/~r/PracticalRiskManagement/~4/luVugHSaw8s" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/PracticalRiskManagement/~3/luVugHSaw8s/pci-compliance-not-going-away-42-not.html</link><author>noreply@blogger.com (Ryan Shopp)</author><feedburner:origLink>http://www.security-works.com/blog/2008/02/pci-compliance-not-going-away-42-not.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-244710282852357590.post-6466360596080658016</guid><pubDate>Wed, 13 Feb 2008 17:30:00 +0000</pubDate><atom:updated>2008-02-13T12:01:43.938-06:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">it grc</category><category domain="http://www.blogger.com/atom/ns#">it-grc</category><category domain="http://www.blogger.com/atom/ns#">compliance</category><category domain="http://www.blogger.com/atom/ns#">it risk</category><category domain="http://www.blogger.com/atom/ns#">risk</category><category domain="http://www.blogger.com/atom/ns#">grc</category><category domain="http://www.blogger.com/atom/ns#">security</category><title>Gartner IT GRC Predictions</title><description>I just had a chance to take a look at some recent research put out by Gartner on the IT Governance, Risk &amp;amp; Compliance Management space (IT-GRC).&lt;br /&gt;&lt;br /&gt;They do an artful job laying out the customer desired capabilities and scoping the size of the market opportunity.&lt;br /&gt;&lt;br /&gt;A couple key points to soak in:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;IT GRCM products provide functions that address needs expressed by&lt;span style="font-weight: bold;"&gt; 75% of the Gartner client base&lt;/span&gt;.&lt;/li&gt;&lt;li&gt;Gartner estimates that software license revenue for vendors...was $73million for 2007, and we project a growth rate of &lt;span style="font-weight: bold;"&gt;70% for 2008.&lt;br /&gt;&lt;/span&gt;&lt;/li&gt;&lt;/ul&gt;This reinforces previous posts with hard numbers that 2008 is indeed the year of IT Risk Managment.  Here are links to those previous posts...&lt;br /&gt;&lt;br /&gt;&lt;ul&gt;&lt;li&gt;&lt;a href="http://www.security-works.com/blog/2008/01/2008-year-of-it-risk-management.html"&gt;2008 - The Year of IT Risk Management&lt;/a&gt;&lt;/li&gt;&lt;li&gt;&lt;a href="http://www.security-works.com/blog/2008/01/2008-year-of-it-risk-management-part-2.html"&gt;2008 - The Year of IT Risk Management, Part 2 - Rise of IT GRC&lt;/a&gt;&lt;/li&gt;&lt;li&gt;&lt;a href="http://www.security-works.com/blog/2008/01/2008-year-of-it-risk-management-part-3.html"&gt;2008 - The Year of IT Risk Management, Part 3 - More and more GRC oriented predictions&lt;/a&gt;&lt;/li&gt;&lt;/ul&gt;                                                                                                                                                                                                                        &lt;br /&gt;I highly recommend heading up to Gartner's website and reading each report;&lt;br /&gt;&lt;ul&gt;&lt;li&gt;&lt;a href="http://www.gartner.com/DisplayDocument?id=600315&amp;amp;ref=g_fromdoc"&gt;MarketScope for IT Governance, Risk and Compliance Management, 2008&lt;/a&gt;&lt;/li&gt;&lt;li&gt;&lt;a href="http://www.gartner.com/DisplayDocument?id=600307&amp;amp;ref=g_fromdoc"&gt;Critical Capabilities for IT GRCM Tools&lt;span style=";font-family:Times New Roman;font-size:100%;"  &gt; &lt;/span&gt;&lt;/a&gt;&lt;/li&gt;&lt;/ul&gt; Then come take a look at how Securityworks can help solve your IT-GRC needs by accomplishing those defined needs and capabilities.&lt;img src="http://feeds.feedburner.com/~r/PracticalRiskManagement/~4/l0wjVa7hTic" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/PracticalRiskManagement/~3/l0wjVa7hTic/gartner-it-grc-predictions.html</link><author>noreply@blogger.com (Ryan Shopp)</author><feedburner:origLink>http://www.security-works.com/blog/2008/02/gartner-it-grc-predictions.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-244710282852357590.post-6867125357407094085</guid><pubDate>Mon, 04 Feb 2008 13:27:00 +0000</pubDate><atom:updated>2008-02-04T08:15:33.109-06:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">it grc</category><category domain="http://www.blogger.com/atom/ns#">it-grc</category><category domain="http://www.blogger.com/atom/ns#">compliance</category><category domain="http://www.blogger.com/atom/ns#">it risk</category><category domain="http://www.blogger.com/atom/ns#">risk</category><category domain="http://www.blogger.com/atom/ns#">security</category><title>What is GRC vs. IT GRC - How does it help IT Security mature to the next level?</title><description>AMR Research shows that total &lt;a href="http://www.amrresearch.com/Content/View.asp?pmillid=20204"&gt;GRC spending approached $30B last year&lt;/a&gt;.  The technology portion (e.g., software, hardware &amp;amp; integration services) of that spending is around a third of it (approximately $10B).&lt;br /&gt;&lt;br /&gt;GRC is a very broadly defined space - very broad!  To gain a better understanding and appreciation for that, &lt;a href="http://www.corp-integrity.com/grc_perspectives/documents/GRCEcoSystemMap.pdf"&gt;here is a newly released map&lt;/a&gt; that identifies various areas and their relationships.&lt;br /&gt;&lt;br /&gt;Another AMR Research note talks about the current &lt;a href="http://www.amrresearch.com/Content/View.asp?pmillid=20065"&gt;maturity point of Enterprises implementing GRC&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;So where does Securityworks play in this "GRC Ecosystem?"  We are coming at it through the eyes of an IT Security Executive.&lt;br /&gt;&lt;br /&gt;Our goal - How can we make the IT audit process more efficient and less frustrating for the IT security organization?  When you look back at the model above we fit in the area called "IT GRC" which leverages/compliments current IT security management investments (e.g., vulnerability scanning, configuration policy management, SIEM) to accomplish this.  If your enterprise already leverages these products then its ready for the next step in the maturity curve, which is IT GRC.  Just to get an idea of some the unique capabilities that extend your current IT Security investments please check out our &lt;a href="http://security-works.com/?page_id=59"&gt;newly posted product demos&lt;/a&gt;.  Live product in action, no sign-up requirements, etc.  Just pure knowledge.&lt;img src="http://feeds.feedburner.com/~r/PracticalRiskManagement/~4/A-60hRRUnH4" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/PracticalRiskManagement/~3/A-60hRRUnH4/what-is-grc-vs-it-grc-how-does-it-help.html</link><author>noreply@blogger.com (Ryan Shopp)</author><feedburner:origLink>http://www.security-works.com/blog/2008/02/what-is-grc-vs-it-grc-how-does-it-help.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-244710282852357590.post-8266465217370037825</guid><pubDate>Mon, 28 Jan 2008 13:34:00 +0000</pubDate><atom:updated>2008-01-28T09:38:29.398-06:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">it grc</category><category domain="http://www.blogger.com/atom/ns#">qualitative</category><category domain="http://www.blogger.com/atom/ns#">it-grc</category><category domain="http://www.blogger.com/atom/ns#">compliance</category><category domain="http://www.blogger.com/atom/ns#">it risk</category><category domain="http://www.blogger.com/atom/ns#">risk</category><category domain="http://www.blogger.com/atom/ns#">grc</category><category domain="http://www.blogger.com/atom/ns#">compliance survey</category><category domain="http://www.blogger.com/atom/ns#">security</category><category domain="http://www.blogger.com/atom/ns#">quantitative</category><title>Compliance costs not slowing down - technology automation to the rescue</title><description>&lt;a href="http://www.deloitte.com/dtt/cda/doc/content/us_fsi_NavigatingCompLabyrinth1-08.pdf"&gt;Deloitte - Navigating the Compliance Labyrinth&lt;/a&gt; offers some great tidbits from recent surveying of financial executives.&lt;br /&gt;&lt;br /&gt;&lt;ul&gt;&lt;li&gt;Compliance continues to increase - from 2.83% of net income in 2002 to 3.69% of net income in 2006.&lt;/li&gt;&lt;li&gt;Primary costs continue to be driven through applying people, not technology to the problem.&lt;/li&gt;&lt;li&gt;and the kicker from our perspective, measuring compliance performance remains largely a qualitative rather than a quantitative process. Only 55% of financial institutions reported using quantitative metrics, implying a limited application of process management tools and methodology.&lt;/li&gt;&lt;/ul&gt;&lt;br /&gt;Forget the name of the segment (e.g., GRC, IT-GRC, ERM, VM).  &lt;span style="font-weight: bold;"&gt;The bottom line is taking a process management based approach with technology. &lt;/span&gt;  Commercial solutions (not home grown) that offer enterprises the opportunity to leverage technology automation to reduce people doing mundane/manual tasks producing the result of reduced compliance costs!&lt;img src="http://feeds.feedburner.com/~r/PracticalRiskManagement/~4/SyuvOl8YU2Q" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/PracticalRiskManagement/~3/SyuvOl8YU2Q/compliance-costs-not-slowing-down.html</link><author>noreply@blogger.com (Ryan Shopp)</author><feedburner:origLink>http://www.security-works.com/blog/2008/01/compliance-costs-not-slowing-down.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-244710282852357590.post-5124374430903016845</guid><pubDate>Mon, 21 Jan 2008 13:51:00 +0000</pubDate><atom:updated>2008-01-21T08:06:33.326-06:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">it risk</category><category domain="http://www.blogger.com/atom/ns#">risk</category><category domain="http://www.blogger.com/atom/ns#">iso 27001</category><category domain="http://www.blogger.com/atom/ns#">ID Theft Prevention</category><category domain="http://www.blogger.com/atom/ns#">privacy</category><category domain="http://www.blogger.com/atom/ns#">controls</category><title>Another security breach, but this one is different...</title><description>Late last week I saw the news around local JC Penney's hit the wire - &lt;a href="http://www.scmagazineus.com/Data-of-650000-customers-of-JCPenney-other-retailers-at-risk-after-backup-goes-missing/article/104368/"&gt;"Data of 650,000 customers at risk.&lt;/a&gt;"   Now this situation appears completely different then TJX.  The data, and I assume the protection of that data, were outsourced. &lt;br /&gt;&lt;br /&gt;So this begs the question - should it be a requirement for vendors providing services to enterprises that would include sensitive data be certified against ISO 27001?&lt;br /&gt;&lt;br /&gt;Here is a &lt;a href="http://www.esj.com/Enterprise/article.aspx?EditorialsID=2957"&gt;great write-up, case study I came across of a vendor doing this&lt;/a&gt;.  Just like we expect vendors to achieve specific Service Level Agreements on availability, performance...shouldn't we be doing the same things around security and risk?&lt;img src="http://feeds.feedburner.com/~r/PracticalRiskManagement/~4/L7QjMHYxGY8" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/PracticalRiskManagement/~3/L7QjMHYxGY8/another-security-breach-but-this-one-is.html</link><author>noreply@blogger.com (Ryan Shopp)</author><feedburner:origLink>http://www.security-works.com/blog/2008/01/another-security-breach-but-this-one-is.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-244710282852357590.post-594276781195973761</guid><pubDate>Wed, 16 Jan 2008 13:32:00 +0000</pubDate><atom:updated>2008-01-16T08:55:37.426-06:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">it grc</category><category domain="http://www.blogger.com/atom/ns#">it-grc</category><category domain="http://www.blogger.com/atom/ns#">it risk</category><category domain="http://www.blogger.com/atom/ns#">risk</category><category domain="http://www.blogger.com/atom/ns#">iso 27001</category><category domain="http://www.blogger.com/atom/ns#">grc</category><category domain="http://www.blogger.com/atom/ns#">security</category><category domain="http://www.blogger.com/atom/ns#">non-technical controls</category><category domain="http://www.blogger.com/atom/ns#">iso 17799</category><title>So much to read, so little time - Top Information Security Risks for 2008</title><description>Now this is impressive!  It's going to take a while to read the supporting reference documents, but this summary is gold and from my perspective a must read for IT Risk Management.&lt;br /&gt;&lt;br /&gt;In the primary summary document, "&lt;a href="http://www.iso27001security.com/Top_information_security_risks_for_2008.pdf"&gt;Top Information Security Risks for 2008&lt;/a&gt;" we get an impressive laundry list of threats &amp;amp; vulnerabilities, their impacts, the risk and the controls.  Page 5 talks of specific risks, some can be addressed with various technical control product on the market, example: #2 - Information Leakage.  If you want to get down and dirty understanding these products spend some time with Rich over at securosis, specifically his blog entries and the summary which formed this &lt;a href="http://securosis.com/publications/DLP-Whitepaper.pdf"&gt;white paper around understanding &amp;amp; selecting DLP solutions&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;This section also highlights non-technical controls, audits etc in #5:  "poor information security studies, risk assessments, projects/assignments and/or staffing/organization, causing failed, wasted, excessive or otherwise inadequate controls and practices selection, implementation, performance measurement, monitoring and/or auditing." Wow, that's a mouthful! But this is exactly what IT GRC is all about.  Through using these software platforms you can evolve from poor, ad-hoc attempts at mitigating this risk while ensuring your enterprise takes a comprehensive, top-down look at any and all potential risks and assess their potential impact.  If you then go down to #1 in the controls section of the document you will see what in my eyes is basically an advertisement for an IT GRC solutions and the process around deploying it, "investment in a good and systematic ISMS (Information Security Management System) incorporating high quality information assurance processes..."&lt;br /&gt;&lt;br /&gt;A key statement back in #5 of risks that I was surprised to see was the calling out of "excessive" controls.  This is something we at Securityworks (especially Bryan) are passionate about.  Some vendors in the IT GRC space believe in throwing the entire "book of controls" at it, and you will be fine...we believe its about making sure you have quality controls in place, not simply quantity.  Bryan has &lt;a href="http://www.security-works.com/blog/2007_09_01_archive.html"&gt;talked about this previously&lt;/a&gt;.&lt;img src="http://feeds.feedburner.com/~r/PracticalRiskManagement/~4/FM9BSsV6SB8" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/PracticalRiskManagement/~3/FM9BSsV6SB8/so-much-to-read-so-little-time-top.html</link><author>noreply@blogger.com (Ryan Shopp)</author><feedburner:origLink>http://www.security-works.com/blog/2008/01/so-much-to-read-so-little-time-top.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-244710282852357590.post-5996201728880576082</guid><pubDate>Tue, 15 Jan 2008 13:19:00 +0000</pubDate><atom:updated>2008-01-15T07:39:18.008-06:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">it grc</category><category domain="http://www.blogger.com/atom/ns#">it-grc</category><category domain="http://www.blogger.com/atom/ns#">compliance</category><category domain="http://www.blogger.com/atom/ns#">it risk</category><category domain="http://www.blogger.com/atom/ns#">risk</category><category domain="http://www.blogger.com/atom/ns#">grc</category><category domain="http://www.blogger.com/atom/ns#">security</category><title>2008 - The Year of IT Risk Management, Part 3 - More and more GRC oriented predictions!</title><description>I keep thinking I'm going to be able to move onto other topics related to IT Risk &amp;amp; Compliance management but it's hard to when my blog reader keeps popping up more and more articles and postings which talk about 2008 predictions and how GRC and IT GRC are going to be the "in thing" this year for IT Security groups. &lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.esj.com/Enterprise/article.aspx?EditorialsID=2956"&gt;IT &amp;amp; Compliance: 5 Big Predictions for 2008&lt;/a&gt; hightlights "...Managerial    evolutions, such as process-centric IT and better application of risk-management    principles to information security management, will help companies refine and    streamline IT governance and compliance."&lt;br /&gt;&lt;br /&gt;The post continues on later with two of the five predictions hitting on capabilities or features of IT GRC products.&lt;img src="http://feeds.feedburner.com/~r/PracticalRiskManagement/~4/WpM1iTSst9Y" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/PracticalRiskManagement/~3/WpM1iTSst9Y/2008-year-of-it-risk-management-part-3.html</link><author>noreply@blogger.com (Ryan Shopp)</author><feedburner:origLink>http://www.security-works.com/blog/2008/01/2008-year-of-it-risk-management-part-3.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-244710282852357590.post-7293563111642791556</guid><pubDate>Fri, 11 Jan 2008 12:43:00 +0000</pubDate><atom:updated>2008-01-15T07:19:10.104-06:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">it grc</category><category domain="http://www.blogger.com/atom/ns#">it-grc</category><category domain="http://www.blogger.com/atom/ns#">it risk</category><category domain="http://www.blogger.com/atom/ns#">grc</category><category domain="http://www.blogger.com/atom/ns#">security</category><title>2008 - The Year of IT Risk Management, Part 2 - Rise of IT GRC</title><description>The customer success stories, industry partnerships, market predictions, etc. drumbeat for IT Governance, Risk and Compliance Management (IT GRC) continues to get louder and louder.  Just caught this article over on TechTarget "&lt;a href="http://www.security-works.com/blog/2008/01/2008-year-of-it-risk-management.html"&gt;Security Management 2008 - What's in Store.&lt;/a&gt;"  About halfway through Mike highlights the GRC space.&lt;br /&gt;&lt;br /&gt;-snip-&lt;br /&gt;&lt;span class="a3"&gt; Hopefully, security professionals will finally come to grips with the discipline that is preparing for an audit, which will result in an opportunity for vendors that provide so-called GRC products -- glorified reporting and workflow packages meant to automate the compliance process. These products allegedly automate the data gathering and reporting processes, so managers don't have to spend days (or weeks) preparing for the audits. Clearly that is a problem for security professionals that should be doing something more productive than preparing for an audit. It pains me to think that we'll need to implement yet another point product to solve a problem, but it is what it is.&lt;br /&gt;-snip-&lt;br /&gt;&lt;/span&gt;&lt;br /&gt;Even though skeptical, I'll take that as an endorsement for GRC in 2008!  Mike give us a shout if you would like a demo, discussion and even an introduction to talk to customers using it.&lt;br /&gt;&lt;br /&gt;2007 was a great year of education on the value of IT GRC and we hope/expect 2008 to be where customer implementations of this security automation take off!  The ROI and team efficiency gains are tremendous, it also reduces the headaches and frustrations security team members get when having to prepare for audits.&lt;br /&gt;&lt;br /&gt;Oh yeah, here is part one of this blog title "&lt;a href="http://www.security-works.com/blog/2008/01/2008-year-of-it-risk-management.html"&gt;2008 - The Year of IT Risk Management&lt;/a&gt;" just in case you missed it.&lt;img src="http://feeds.feedburner.com/~r/PracticalRiskManagement/~4/nv1NxaaQ70Q" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/PracticalRiskManagement/~3/nv1NxaaQ70Q/2008-year-of-it-risk-management-part-2.html</link><author>noreply@blogger.com (Ryan Shopp)</author><feedburner:origLink>http://www.security-works.com/blog/2008/01/2008-year-of-it-risk-management-part-2.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-244710282852357590.post-122750990321932916</guid><pubDate>Tue, 08 Jan 2008 18:50:00 +0000</pubDate><atom:updated>2008-01-08T19:27:41.113-06:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">it grc</category><category domain="http://www.blogger.com/atom/ns#">it-grc</category><category domain="http://www.blogger.com/atom/ns#">it risk</category><category domain="http://www.blogger.com/atom/ns#">grc</category><category domain="http://www.blogger.com/atom/ns#">ID Theft Prevention</category><category domain="http://www.blogger.com/atom/ns#">ID Red Flag</category><category domain="http://www.blogger.com/atom/ns#">FACTA</category><title>How aware are your employees on IT security and risk policies?</title><description>&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://www.security-works.com/blog/uploaded_images/redflag-793627.jpg"&gt;&lt;img style="margin: 0pt 10px 10px 0pt; float: left; cursor: pointer;" src="http://www.security-works.com/blog/uploaded_images/redflag-793625.jpg" alt="" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;Nice read that highlights &lt;a href="http://www.bankinfosecurity.com/articles.php?art_id=669"&gt;10 area of risk that should be in focus for 2008&lt;/a&gt;.   One that really jumped out which we are starting to hear more about here in the IT-GRC space is awareness and training of employees on security and risk situation.&lt;br /&gt;&lt;br /&gt;-snip-&lt;br /&gt;&lt;b&gt;Employee and Customer Awareness&lt;/b&gt; It’s something everyone intends to do – better educate their employees and customers about the security threats that are facing institutions and customers. Now with the ID Theft Red Flags, it’s also been pushed to the top of the compliance list. Institutions by Nov. 1 must have a written program showing how they are educating their employees and customers about identity theft. &lt;p&gt;American Banker Association’s Doug Johnson, senior policy advisor for the largest industry association, lists this as one of the top risk management issues for 2008.”Increasing your institution’s security awareness pays off in several ways -- employees learn how to protect the data they’re working with, and their awareness reduces the threat of the insider threat (either malicious or unintentional),” says Johnson. Many times the malicious insider can be stopped, if the people working with them are trained and are aware of the red flags that show the work habits and behaviors of a malicious insider. Do your employees know what to look for, what indicators there are that an insider is doing something on your networks or to your institution’s data?&lt;br /&gt;-snip-&lt;/p&gt;&lt;p&gt;A new thing to many that was mention in here was "ID Red Flags."  Federal ID Red Flags are suppose to be in place by November 1, 2008 (about 10 months from now).  These rules (&lt;a href="http://www.bankinfosecurity.com/regulations.php?reg_id=552"&gt;announced in November&lt;/a&gt;) implement section 114 and 315 of the Fair and Accurate Credit Transactions Act (FACTA) of 2003.  Basically, each financial institution’s Identity Theft Prevention Program must include reasonable policies and procedures for detecting, preventing and mitigating identity theft.&lt;br /&gt;&lt;/p&gt;&lt;p&gt;Part of this process is prevention.  One of the best ways to prevent something is through education.  By having automated capabilities that require each employee to read what is expected of them in helping prevent Identity Theft.  IT-GRC automation can help with this in automating this policy dissemination and acceptance tracking for owners of any company IT resource that may contain consumer identity information (e.g., from server owners, to laptop owners and beyond).&lt;br /&gt;&lt;/p&gt;&lt;p&gt;&lt;br /&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/PracticalRiskManagement/~4/deH0ReyWRnA" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/PracticalRiskManagement/~3/deH0ReyWRnA/how-aware-your-employees-on-it-security.html</link><author>noreply@blogger.com (Ryan Shopp)</author><feedburner:origLink>http://www.security-works.com/blog/2008/01/how-aware-your-employees-on-it-security.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-244710282852357590.post-7734171841488415239</guid><pubDate>Fri, 04 Jan 2008 13:23:00 +0000</pubDate><atom:updated>2008-01-04T08:43:58.820-06:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">it grc</category><category domain="http://www.blogger.com/atom/ns#">it-grc</category><category domain="http://www.blogger.com/atom/ns#">compliance</category><category domain="http://www.blogger.com/atom/ns#">it risk</category><category domain="http://www.blogger.com/atom/ns#">risk</category><category domain="http://www.blogger.com/atom/ns#">iso 27001</category><category domain="http://www.blogger.com/atom/ns#">grc</category><category domain="http://www.blogger.com/atom/ns#">ISO</category><category domain="http://www.blogger.com/atom/ns#">iso 17799</category><category domain="http://www.blogger.com/atom/ns#">controls</category><title>2008 - The Year of IT Risk Management?</title><description>I've been busy over the holidays enjoying everyones blogs and articles recapping 2007 and making predictions for 2008.  Among other things highlighted in those articles, a common point pertains to Securityworks around "true" IT Risk Management (what I mean by "true" is the message is coming from companies who didn't adjust their marketing to be en vogue - e.g., SIEM products or Vulnerability Assessment products).&lt;br /&gt;&lt;br /&gt;Before IT Risk Management was "cool" Securityworks has been out their working away on it (for over 4 years now).&lt;br /&gt;&lt;br /&gt;One of my favorites that highlights this prediction for 2008 is over at &lt;a href="http://rationalsecurity.typepad.com/blog/2007/12/and-now-some-us.html"&gt;Rational Survivability&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;-snip-&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;Compliance stops being a dirty word  &amp;amp; Risk Management moves beyond buzzword&lt;/strong&gt;&lt;br /&gt;Today we typically see the role of information security described as blocking and tackling; focused on managing threats and vulnerabilities balanced against the need to be "compliant" to some arbitrary set of internal and external policies.  In many people's assessment then, compliance equals security.  This is an inaccurate and unfortunate misunderstanding.&lt;br /&gt;&lt;br /&gt;In 2008, we'll see many of the functions of security -- administrative, policy and operational -- become much more visible and transparent to the business and we'll see a renewed effort placed on compliance within the scope of managing risk because the former is actually a by-product of a well-executed risk management strategy.&lt;br /&gt;&lt;br /&gt;We have compliance as an industry today because we manage technology threats and vulnerabilities and don't manage risk.  Compliance is actually nothing more than a way of forcing transparency and plugging a gap between the two.  For most, it's the best they've got.&lt;br /&gt;&lt;br /&gt;What's traditionally preventing the transition from threat/vulnerability management to risk management is the principal focus on technology with a lack of a good risk assessment framework and thus a lack of understanding of business impact.&lt;br /&gt;&lt;br /&gt;The availability of mature risk assessment frameworks (OCTAVE, FAIR, etc.) combined with the maturity of IT and governance frameworks (CoBIT, ITIL) and the readiness of the business and IT/Security cultures to accept risk management as a language and actionset with which they need to be conversant will yield huge benefits this year.&lt;br /&gt;&lt;br /&gt;-snip-&lt;br /&gt;&lt;br /&gt;Well said (but then again I'm biased)!&lt;img src="http://feeds.feedburner.com/~r/PracticalRiskManagement/~4/omhFc5gUELU" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/PracticalRiskManagement/~3/omhFc5gUELU/2008-year-of-it-risk-management.html</link><author>noreply@blogger.com (Ryan Shopp)</author><feedburner:origLink>http://www.security-works.com/blog/2008/01/2008-year-of-it-risk-management.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-244710282852357590.post-3306822109111576602</guid><pubDate>Fri, 28 Dec 2007 15:21:00 +0000</pubDate><atom:updated>2008-01-04T08:42:36.141-06:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">compliance</category><category domain="http://www.blogger.com/atom/ns#">it risk</category><category domain="http://www.blogger.com/atom/ns#">risk</category><category domain="http://www.blogger.com/atom/ns#">ISO</category><category domain="http://www.blogger.com/atom/ns#">security</category><category domain="http://www.blogger.com/atom/ns#">non-technical controls</category><title>IT Risk Management vs. Information Security survey</title><description>I was playing catch-up on blog reading and came across this interesting post by a favorite blogging colleague of mine, Anton Chuvakin, "&lt;a href="http://chuvakin.blogspot.com/2007/12/review-of-my-2007-security-predictions.html"&gt;Review of my 2007 Security Prediction: Too Wimpy&lt;/a&gt;."&lt;br /&gt;&lt;br /&gt;Prediction #4 about Risk Management lead to some very &lt;a href="http://chuvakin.blogspot.com/2007/12/more-on-security-vs-risk.html"&gt;intriguing survey results&lt;/a&gt;.  Here is a copy of the graphic from those results which says it all...&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://www.security-works.com/blog/uploaded_images/riskvssecurity-787193.jpg"&gt;&lt;img style="cursor: pointer;" src="http://www.security-works.com/blog/uploaded_images/riskvssecurity-787190.jpg" alt="" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;span style="text-decoration: underline;"&gt;&lt;br /&gt;&lt;br /&gt;&lt;/span&gt;A personal point I can add here is this actually makes some sense to me.&lt;br /&gt;&lt;br /&gt;Here at Securityworks we are 100% focused on talking IT Risk Management.  When I talk with customers they are usually talking (strategic = risk) vs. (tactical = security).  Another thing to realize is IT risk encompasses more then technical control monitoring/management solutions (&lt;a href="http://www.security-works.com/blog/2007/12/users-continue-to-ignore-security.html"&gt;that is only 50% of the scope as discussed in my previous post)&lt;/a&gt;.  IT Risk also spans people &amp;amp; processes (e.g., non-technical controls).  Since that typically requires getting into process improvement it is naturally discussed as a strategic initiative due to the time/effort associated with it.&lt;br /&gt;&lt;br /&gt;So now with 2007 ending and looking ahead to 2008 we should be trying to use this opportunity to be more strategic before tactical day-to-day tasks re-consume us.  IT-GRC solutions (which Gartner, Forrester, etc are calling these solution) help you do this!  So go ahead, take a look...this is going to be a hot area for 2008 based on what I'm seeing and hearing for a variety of reasons.&lt;img src="http://feeds.feedburner.com/~r/PracticalRiskManagement/~4/f1ujeS52LuM" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/PracticalRiskManagement/~3/f1ujeS52LuM/it-risk-management-vs-information.html</link><author>noreply@blogger.com (Ryan Shopp)</author><feedburner:origLink>http://www.security-works.com/blog/2007/12/it-risk-management-vs-information.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-244710282852357590.post-2349927300241101382</guid><pubDate>Thu, 27 Dec 2007 17:37:00 +0000</pubDate><atom:updated>2008-01-04T08:41:22.187-06:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">compliance</category><category domain="http://www.blogger.com/atom/ns#">risk</category><category domain="http://www.blogger.com/atom/ns#">healthcare</category><category domain="http://www.blogger.com/atom/ns#">security</category><title>Healthcare Best Practices Security Framework</title><description>We are excited to see this &lt;a href="http://www.scmagazineus.com/Health-industry-leaders-IT-players-seek-to-establish-Health-Information-Security-Framework/article/100185/"&gt;announcement &lt;/a&gt;about the formation of HITRUST (Health Information Trust Alliance).  A health care vertical specific initiative around establishing and collaborating on information security best practices.  Why are we excited, our solution (along with other IT-GRC solutions) are specifically designed to enable a major enterprises to consolidate, centralize and simply organize from the top-down their Information Security Framework in an actionable, track-able way.&lt;img src="http://feeds.feedburner.com/~r/PracticalRiskManagement/~4/y-OIG56lY7o" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/PracticalRiskManagement/~3/y-OIG56lY7o/healthcare-best-practices-security.html</link><author>noreply@blogger.com (Ryan Shopp)</author><feedburner:origLink>http://www.security-works.com/blog/2007/12/healthcare-best-practices-security.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-244710282852357590.post-6472137189735721875</guid><pubDate>Thu, 20 Dec 2007 12:40:00 +0000</pubDate><atom:updated>2008-01-04T08:40:59.085-06:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">compliance</category><category domain="http://www.blogger.com/atom/ns#">security</category><category domain="http://www.blogger.com/atom/ns#">privacy</category><category domain="http://www.blogger.com/atom/ns#">efficiency</category><title>Is Security about improving the operational efficiency of IT?</title><description>Just had the chance to check out &lt;a href="http://www.ey.com/Global/assets.nsf/International/EY_TSRS_GISS2007/$file/EY_TSRS_GISS2007.pdf"&gt;Ernst &amp;amp; Young's 10th Annual Global Information Security Survey:  Achieving a Balance of Risk &amp;amp; Performance&lt;/a&gt;.  It's a very details document that has a ton of great information.  What caught my eye this morning was the answers to the question:&lt;br /&gt;&lt;br /&gt;What is driving information security?&lt;br /&gt;&lt;ul&gt;&lt;li&gt;Compliance with regulations&lt;/li&gt;&lt;li&gt;Privacy and data protection&lt;/li&gt;&lt;li&gt;Improving IT and operational efficiency&lt;br /&gt;&lt;/li&gt;&lt;/ul&gt;The first two didn't really surprise me, but I found this last one really interesting.  After re-reading that section of the survey I found myself re-phrasing it a little into "Improving the operational efficiency of IT."  Hmmm, another independent point back to something I was &lt;a href="http://www.security-works.com/blog/2007/12/is-it-risk-management-union-of-it.html"&gt;pondering the other day&lt;/a&gt; .&lt;br /&gt;&lt;br /&gt;These days I'm personally more focused on the vendor side of software product life cycles (e.g., design, implement, test, , feedback).  With that said, this smells very similar to the role a Quality Assurance/Testing organization plays to the Development organization.  While R&amp;amp;D is focused on understanding what needs to be built and attempting to delivering that capability ASAP, QA is always helping or sometime battling R&amp;amp;D with finding problems/issues/exposure points etc.&lt;br /&gt;&lt;br /&gt;The role of security, just like QA, is not to hinder their operational/development counterparts, but to help mitigate exposure/risk in a proactive way.  Bottom line, it's been my experience that it's better to find a problem early then late (major cost savings, greater customer satisfaction, etc).&lt;br /&gt;&lt;br /&gt;I may be out in left field here but I'm simply pondering out loud the placement and priority given to Security/Risk/Compliance Management versus the overall purpose of the business.&lt;br /&gt;&lt;br /&gt;Take a look at the survey and please throw down in the comments what you found interesting.&lt;img src="http://feeds.feedburner.com/~r/PracticalRiskManagement/~4/g4xImW3glvU" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/PracticalRiskManagement/~3/g4xImW3glvU/is-security-about-improving-operational.html</link><author>noreply@blogger.com (Ryan Shopp)</author><feedburner:origLink>http://www.security-works.com/blog/2007/12/is-security-about-improving-operational.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-244710282852357590.post-1633957403007558063</guid><pubDate>Tue, 18 Dec 2007 13:32:00 +0000</pubDate><atom:updated>2008-01-04T08:40:19.374-06:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">it risk</category><category domain="http://www.blogger.com/atom/ns#">risk</category><category domain="http://www.blogger.com/atom/ns#">security</category><title>Is IT Risk Management the Union of IT Security &amp; IT Operations?</title><description>This morning I read this statement from PCI Expert James Deluccia IV and it struck a cord...&lt;br /&gt;&lt;br /&gt;&lt;snip&gt;-snip-&lt;br /&gt;The best risk management initiatives don't simply protect data, they help the company to run more effectively," he said. "This is the case when equal consideration is given to areas like system continuity and service delivery that support operational measures. It's the blending of business necessity with core methods for data security that ensures overall risk management."&lt;br /&gt;&lt;snip&gt;-snip-&lt;br /&gt;&lt;br /&gt;Over the last couple years I've read and heard about the pending convergence of Security &amp;amp; Operations Management but we still haven't really seen it occur. With more and more attention being given to Risk, maybe it's right around the corner.&lt;br /&gt;&lt;br /&gt;After reading this snip it reminded be of emphasis applied to programs/organizations embracing TQM or other re-engineering practices back in mid-1990's. Security and Operations Managment are rooted in tactically solving pains; Operations focuses on keeping IT resources up and running while Security focuses on protecting those IT resources. Those two ideals, time to time, come into conflict. By taking a business goals driven, "quality-oriented" look at IT fromthe top-down we may find a union between Operations &amp;amp; Security.&lt;br /&gt;&lt;br /&gt;The snip was found in article &lt;a href="http://www.itcinstitute.com/display.aspx?ID=4664"&gt;"PCI Expert James DeLuccia IV Suggests Retailers Address Both Sides of Risk Management - Security and Business Availability"&lt;/a&gt;&lt;/snip&gt;&lt;/snip&gt;&lt;img src="http://feeds.feedburner.com/~r/PracticalRiskManagement/~4/xLcNBP5qTGE" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/PracticalRiskManagement/~3/xLcNBP5qTGE/is-it-risk-management-union-of-it.html</link><author>noreply@blogger.com (Ryan Shopp)</author><feedburner:origLink>http://www.security-works.com/blog/2007/12/is-it-risk-management-union-of-it.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-244710282852357590.post-8436337607531912031</guid><pubDate>Thu, 13 Dec 2007 12:37:00 +0000</pubDate><atom:updated>2008-01-04T08:39:29.417-06:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">non-technical</category><category domain="http://www.blogger.com/atom/ns#">it-grc</category><category domain="http://www.blogger.com/atom/ns#">risk</category><category domain="http://www.blogger.com/atom/ns#">compliance survey</category><category domain="http://www.blogger.com/atom/ns#">controls</category><title>Users continue to ignore security policies, while security organizations are overlooking non-technical controls</title><description>&lt;a href="http://www.itcinstitute.com/display.aspx?ID=4648"&gt;IT Compliance Institute had an article posted this morning that reinforces&lt;/a&gt; the point; "it's not the software/hardware/infrastructure/etc but the people and processes that expose the biggest risks to a company.&lt;p&gt;The article doesn't reveal who/where the survey was taken but it does highlight some key security items that people usually cut corners on.&lt;br /&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;Fifty-six percent said they had accessed office e-mail via a public wireless hotspot&lt;/li&gt;&lt;li&gt;52 percent said they had accessed office e-mail via a public computer. &lt;/li&gt;&lt;li&gt; Eight percent admitted to having lost a mobile device containing corporate information. &lt;/li&gt;&lt;li&gt; Sixty-three percent admitted to sending corporate documents to their personal e-mail addresses so they could work at home.&lt;/li&gt;&lt;/ul&gt;There are security technologies out their (e.g., encryption, data leakage) that can help with each item but the challenge is keeping up with other IT technologies being deployed and business demands/challenges the users are trying to productively solve. Bottom line, you can't bypass making sure you have the right policies, procedures and education in place for your users (aka non-technical controls).&lt;br /&gt;&lt;br /&gt;After reading this I decided to do some searching around for some type of survey numbers around technical vs. non-technical controls. I didn't see much out there but did come across this ("&lt;a href="http://csdl2.computer.org/comp/mags/sp/2007/01/j1036.pdf"&gt;Is Information Security Under Control&lt;/a&gt;') from IEEE Computer Society published in early 2007.&lt;br /&gt;&lt;br /&gt;The survey focused in on 80 of the highest quality security controls as determined by a group of experts. From that list of 80 their wasn't a place that specifically counted the number of non-technical vs. technical controls BUT, there were two very interesting graphs.&lt;br /&gt;&lt;br /&gt;The first one (figure 2 in the article. - see below) showed the top 10 with the highest level of quality implementation. It revealed that 6 are technical controls and 4 are non-technical controls. Meanwhile, the second graphic (figure 3 in the article - see below) showed the bottom 10 related to quality of implementation. It revealed that 3 are technical while 7 were non-technical.&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://www.security-works.com/blog/uploaded_images/bottomqualitycontrols-760776.jpg"&gt;&lt;img style="cursor: pointer;" src="http://www.security-works.com/blog/uploaded_images/bottomqualitycontrols-760772.jpg" alt="" border="0" /&gt;&lt;/a&gt;  &lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://www.security-works.com/blog/uploaded_images/topqualitycontrols-768992.jpg"&gt;&lt;img style="cursor: pointer;" src="http://www.security-works.com/blog/uploaded_images/topqualitycontrols-768989.jpg" alt="" border="0" /&gt;    &lt;/a&gt;&lt;br /&gt;&lt;br /&gt;So just running crude number here shows 11 of those 20 were non-technical controls while 9 were technical controls.  The articles goes on to make the statement "...we found that of all 80 practices surveyed, management controls (non-technical controls) had substantially lower implementation ratings then controls in the technical and operational categories... Organizations must realize that a large proportion of information security problems extend far beyond technology and learn to appreciate the role that less technical controls, such as policy development, play in minimizing security breaches' impact on mission-critical operations.&lt;br /&gt;&lt;br /&gt;So this begs the question, "when was the last time your security group considered software products that help with managing these non-technical controls instead of just technical controls?"  I've talked with numerous enterprises that have installed or are investigating various software products like Vulnerability Assessment, Patch/Configuration Management, Antivirus, SEIM, data leakage, etc.  Maybe it's time to do something for your non-technical controls also and consider adding IT-GRC products to that 2008 budget/priority list.&lt;img src="http://feeds.feedburner.com/~r/PracticalRiskManagement/~4/7fTvhmHIBGE" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/PracticalRiskManagement/~3/7fTvhmHIBGE/users-continue-to-ignore-security.html</link><author>noreply@blogger.com (Ryan Shopp)</author><feedburner:origLink>http://www.security-works.com/blog/2007/12/users-continue-to-ignore-security.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-244710282852357590.post-2425229358197842964</guid><pubDate>Tue, 11 Dec 2007 12:38:00 +0000</pubDate><atom:updated>2007-12-11T07:01:01.482-06:00</atom:updated><title>Data &amp; Application Security demand continues to rise</title><description>If you don't have this blog marked in your RSS reader or linked from your blog roll you are missing out!  The insights and candid perspectives are outstanding and extremely insightful when you take the time to read and ponder &lt;a href="http://securosis.com/"&gt;Rich Mogull's perspectives over at www.securosis.com&lt;/a&gt;.  Here are some recent gems:&lt;br /&gt;&lt;br /&gt;Rich recently blogged about the &lt;a href="http://securosis.com/2007/12/10/data-and-application-security-will-drive-most-security-growth-for-the-next-3-5-years/"&gt;upcoming trend around data and application security driving the security business growth in the next 3-5 years&lt;/a&gt;.  During that post he articulated the "rise of data security"  through a very concise recap on why/how we came to where we are today.&lt;br /&gt;&lt;br /&gt;Then I must also give major kudos to his crack editing and spoof video on public sensitive data breaches called &lt;a href="http://securosis.com/2007/12/02/data-breach-wars/"&gt;Data Breach Wars.&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;It's extremely entertaining for the first 60 seconds!!! Then unfortunately it starts to drag on a little (sorry Rich, maybe if the scrolling went faster).  It does drive home a key point.  Data Breaches are not slowing down but increasing exponentially and will continue to increase until Enterprises take a more strategic, not just tactical approach to  Security, Risk &amp;amp; Compliance Management of their data and applications.&lt;img src="http://feeds.feedburner.com/~r/PracticalRiskManagement/~4/87KpmJgJt8o" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/PracticalRiskManagement/~3/87KpmJgJt8o/data-application-security-demand.html</link><author>noreply@blogger.com (Ryan Shopp)</author><feedburner:origLink>http://www.security-works.com/blog/2007/12/data-application-security-demand.html</feedburner:origLink></item></channel></rss>
