<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Key Content on Andrew Sheves</title><link>https://andrewsheves.com/tags/key-content/</link><description>Recent content in Key Content on Andrew Sheves</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 12 Sep 2017 00:00:00 +0000</lastBuildDate><atom:link href="https://andrewsheves.com/tags/key-content/index.xml" rel="self" type="application/rss+xml"/><item><title>A KISS Approach to Enterprise Security Risk Management</title><link>https://andrewsheves.com/2017/09/12/a-kiss-approach-to-enterprise-security-risk-management/</link><pubDate>Tue, 12 Sep 2017 00:00:00 +0000</pubDate><guid>https://andrewsheves.com/2017/09/12/a-kiss-approach-to-enterprise-security-risk-management/</guid><description>&lt;p&gt;Enterprise security risk management (ESRM) has been a topic of increasing interest for security managers over the past few years.  ASIS International has identified it as a strategic focus. However, after a review of the literature, beginning with the &lt;a href="https://cso.asisonline.org/esrm/Documents/CSORT_ESRM_whitepaper_%20pt%201.pdf"&gt;2010 CSO roundtable paper on ESRM&lt;/a&gt;, two issues are raised that could make ESRM implementation difficult.&lt;/p&gt;
&lt;p&gt;The initial papers on ESRM appeared to encourage security to fill the gap left by traditional enterprise risk management (ERM) systems, which often focused on financial and market risk exclusively. Although an effective ERM system should incorporate all risks, having security fill these gaps via the ESRM system would quickly overwhelm the chief security officer (CSO).&lt;/p&gt;</description></item></channel></rss>