<?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 Re: Action to secure in Member Support</title>
    <link>https://community.isc2.org/t5/Member-Support/Action-to-secure/m-p/294#M30</link>
    <description>&lt;P&gt;Pretty much all&amp;nbsp;of our customers are required to ensure their systems are secure in accordance with government regulations. If it wasn't for requirements like HIPPA, Sarbanes-Oxley, PCI, etc. I imagine an awful lot of companies would just try whatever sounded like a good idea from the last salesman or not bother implementing anything.&lt;/P&gt;</description>
    <pubDate>Sun, 08 Oct 2017 14:02:53 GMT</pubDate>
    <dc:creator>minidriver</dc:creator>
    <dc:date>2017-10-08T14:02:53Z</dc:date>
    <item>
      <title>Action to secure</title>
      <link>https://community.isc2.org/t5/Member-Support/Action-to-secure/m-p/204#M14</link>
      <description>What compels your Enduser or customers to follow Security recommendations? Regulations or otherwise?</description>
      <pubDate>Mon, 09 Oct 2023 08:17:50 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Member-Support/Action-to-secure/m-p/204#M14</guid>
      <dc:creator>Help2Secure</dc:creator>
      <dc:date>2023-10-09T08:17:50Z</dc:date>
    </item>
    <item>
      <title>Re: Action to secure</title>
      <link>https://community.isc2.org/t5/Member-Support/Action-to-secure/m-p/294#M30</link>
      <description>&lt;P&gt;Pretty much all&amp;nbsp;of our customers are required to ensure their systems are secure in accordance with government regulations. If it wasn't for requirements like HIPPA, Sarbanes-Oxley, PCI, etc. I imagine an awful lot of companies would just try whatever sounded like a good idea from the last salesman or not bother implementing anything.&lt;/P&gt;</description>
      <pubDate>Sun, 08 Oct 2017 14:02:53 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Member-Support/Action-to-secure/m-p/294#M30</guid>
      <dc:creator>minidriver</dc:creator>
      <dc:date>2017-10-08T14:02:53Z</dc:date>
    </item>
    <item>
      <title>Re: Action to secure</title>
      <link>https://community.isc2.org/t5/Member-Support/Action-to-secure/m-p/542#M48</link>
      <description>Regulation here. I’m in banking and having examiners down your throat regularly is the fear factor.&lt;BR /&gt;&lt;BR /&gt;That being said, what keeps them actually doing more than the letter of the law is a robust training and employee involvement program. Many varieties of social engineering tests monthly or more frequently, fun games to “spot” security holes, posters and fliers in the break areas, mandatory testing, involvement with presentations in department meetings, full staff and board meetings. Individual meetings with department heads, executive staff and the board because... and this is the big bit... all of senior management getting involved is the game changer.&lt;BR /&gt;&lt;BR /&gt;If I know other Execs are passing down my info and taking it seriously, everyone does. Getting their buy-in can take time, but it’s necessary to implement a program and see real, long-term results. It’s not just a policy to sign, it’s keeping the culture security-conscious.</description>
      <pubDate>Sun, 08 Oct 2017 17:48:33 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Member-Support/Action-to-secure/m-p/542#M48</guid>
      <dc:creator>Anne</dc:creator>
      <dc:date>2017-10-08T17:48:33Z</dc:date>
    </item>
  </channel>
</rss>

