<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic 2017 Ponemon Cost of Data Breach Study in Member Support</title>
    <link>https://community.isc2.org/t5/Member-Support/2017-Ponemon-Cost-of-Data-Breach-Study/m-p/4373#M495</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please share your feedback to the 2017 Cost of Data Breach from Ponemon&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.ibm.com/security/data-breach" target="_self"&gt;https://www.ibm.com/security/data-breach&lt;/A&gt; in light with the comments made by Calyptix &lt;A href="https://www.calyptix.com/top-threats/top-3-causes-data-breach-expensive/" target="_self"&gt;https://www.calyptix.com/top-threats/top-3-causes-data-breach-expensive/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My personal point of view is that the top root cause of the 2017 data breaches should be "human error" or simply said "negligence". In fact I understand human error as an unintended error for example a system administrator doing a mistake while performing a configuration. But for the examples listed by Calyptix here below, I see them as pure negligence. The activities should be planned enforced by&amp;nbsp; proper policies, security baselines and procedures to avert the breaches.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Examples of the ways human error can lead to data breaches include:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Failure to apply patches to known vulnerabilities&lt;/LI&gt;&lt;LI&gt;Employees leaving laptops or other devices in unlocked cars, where they are &lt;A href="https://www.calyptix.com/hipaa/discover-the-top-3-causes-of-hipaa-violations-and-their-simple-solutions/" target="_blank"&gt;easily stolen&lt;/A&gt;&lt;/LI&gt;&lt;LI&gt;When an employee mistakenly emails sensitive information to an unintended party&lt;/LI&gt;&lt;LI&gt;When a database containing confidential information is unintentionally configured to be internet facing, and thereby accessible by search engines&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Brigitte.&lt;/P&gt;</description>
    <pubDate>Sun, 17 Dec 2017 21:12:32 GMT</pubDate>
    <dc:creator>JoshuaGabriel</dc:creator>
    <dc:date>2017-12-17T21:12:32Z</dc:date>
    <item>
      <title>2017 Ponemon Cost of Data Breach Study</title>
      <link>https://community.isc2.org/t5/Member-Support/2017-Ponemon-Cost-of-Data-Breach-Study/m-p/4373#M495</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please share your feedback to the 2017 Cost of Data Breach from Ponemon&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.ibm.com/security/data-breach" target="_self"&gt;https://www.ibm.com/security/data-breach&lt;/A&gt; in light with the comments made by Calyptix &lt;A href="https://www.calyptix.com/top-threats/top-3-causes-data-breach-expensive/" target="_self"&gt;https://www.calyptix.com/top-threats/top-3-causes-data-breach-expensive/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My personal point of view is that the top root cause of the 2017 data breaches should be "human error" or simply said "negligence". In fact I understand human error as an unintended error for example a system administrator doing a mistake while performing a configuration. But for the examples listed by Calyptix here below, I see them as pure negligence. The activities should be planned enforced by&amp;nbsp; proper policies, security baselines and procedures to avert the breaches.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Examples of the ways human error can lead to data breaches include:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Failure to apply patches to known vulnerabilities&lt;/LI&gt;&lt;LI&gt;Employees leaving laptops or other devices in unlocked cars, where they are &lt;A href="https://www.calyptix.com/hipaa/discover-the-top-3-causes-of-hipaa-violations-and-their-simple-solutions/" target="_blank"&gt;easily stolen&lt;/A&gt;&lt;/LI&gt;&lt;LI&gt;When an employee mistakenly emails sensitive information to an unintended party&lt;/LI&gt;&lt;LI&gt;When a database containing confidential information is unintentionally configured to be internet facing, and thereby accessible by search engines&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Brigitte.&lt;/P&gt;</description>
      <pubDate>Sun, 17 Dec 2017 21:12:32 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Member-Support/2017-Ponemon-Cost-of-Data-Breach-Study/m-p/4373#M495</guid>
      <dc:creator>JoshuaGabriel</dc:creator>
      <dc:date>2017-12-17T21:12:32Z</dc:date>
    </item>
  </channel>
</rss>

