<?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: PCI Compliance in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/pci-compliance/m-p/4220663#M30313</link>
    <description>Hoff, thanks for the links.  I research the one from LJK and found that they have a tool that provides a mapping to NIST 800-53, but they are willing to create a PCI mapping policy for me -- immensely helpful!&lt;BR /&gt;&lt;BR /&gt;Can you also point me to an OpenVMS operating system hardening document?  I've read the one from Rob McMillan at Queensland, but I want to research what other documents are available.</description>
    <pubDate>Wed, 25 Jun 2008 16:56:14 GMT</pubDate>
    <dc:creator>patriceiggy</dc:creator>
    <dc:date>2008-06-25T16:56:14Z</dc:date>
    <item>
      <title>PCI Compliance</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/pci-compliance/m-p/4220660#M30310</link>
      <description>Is there any tool which maps OpenVMS operating system parameters to the PCI sata security standard, so that I can use it to prove to my auditors that the OpenVMS system meets current PCI requirements?</description>
      <pubDate>Mon, 23 Jun 2008 14:07:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/pci-compliance/m-p/4220660#M30310</guid>
      <dc:creator>patriceiggy</dc:creator>
      <dc:date>2008-06-23T14:07:00Z</dc:date>
    </item>
    <item>
      <title>Re: PCI Compliance</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/pci-compliance/m-p/4220661#M30311</link>
      <description>patriceiggy,&lt;BR /&gt;&lt;BR /&gt;The general underpinnings are mostly in the OpenVMS Guide to System Security (available on the OpenVMS www site at &lt;A href="http://www.hp.com/go/OpenVMS" target="_blank"&gt;http://www.hp.com/go/OpenVMS&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;I am not aware of an OpenVMS specific checklist for PCI, although the precise checklist should be deriveable from the precise checklist that is being used by your auditors (I am always careful in such situations to use the PRECISE checklist being asked, it does matter).&lt;BR /&gt;&lt;BR /&gt;- Bob Gezelter, &lt;A href="http://www.rlgsc.com" target="_blank"&gt;http://www.rlgsc.com&lt;/A&gt;&lt;BR /&gt;  Author, "OpenVMS Security", Handbook of Information Security (H.Bidgoli, Ed., Wiley &amp;amp; Sons, 2006)</description>
      <pubDate>Mon, 23 Jun 2008 15:03:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/pci-compliance/m-p/4220661#M30311</guid>
      <dc:creator>Robert Gezelter</dc:creator>
      <dc:date>2008-06-23T15:03:57Z</dc:date>
    </item>
    <item>
      <title>Re: PCI Compliance</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/pci-compliance/m-p/4220662#M30312</link>
      <description>AFAIK, everybody gets to do their own specific and local PCI compliance investigation.  (I could make a cynical comment or three around the likely PCI root goals, but that's probably not appropriate for ITRC.)&lt;BR /&gt;&lt;BR /&gt;Above and beyond the OpenVMS security manual and the NCSC Class C2 recommendations in the appendix of same cited earlier, some of the accepted security-related evaluation and documentation pointers, and a compliance-testing tool, are referenced here:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://64.223.189.234/node/43" target="_blank"&gt;http://64.223.189.234/node/43&lt;/A&gt; &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 23 Jun 2008 17:04:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/pci-compliance/m-p/4220662#M30312</guid>
      <dc:creator>Hoff</dc:creator>
      <dc:date>2008-06-23T17:04:16Z</dc:date>
    </item>
    <item>
      <title>Re: PCI Compliance</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/pci-compliance/m-p/4220663#M30313</link>
      <description>Hoff, thanks for the links.  I research the one from LJK and found that they have a tool that provides a mapping to NIST 800-53, but they are willing to create a PCI mapping policy for me -- immensely helpful!&lt;BR /&gt;&lt;BR /&gt;Can you also point me to an OpenVMS operating system hardening document?  I've read the one from Rob McMillan at Queensland, but I want to research what other documents are available.</description>
      <pubDate>Wed, 25 Jun 2008 16:56:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/pci-compliance/m-p/4220663#M30313</guid>
      <dc:creator>patriceiggy</dc:creator>
      <dc:date>2008-06-25T16:56:14Z</dc:date>
    </item>
    <item>
      <title>Re: PCI Compliance</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/pci-compliance/m-p/4220664#M30314</link>
      <description>patriceiggy,&lt;BR /&gt;&lt;BR /&gt;I noticed you are new here, so let me begin with&lt;BR /&gt;WELCOME to the VMS forum!&lt;BR /&gt;&lt;BR /&gt;As a Dutchie, I am not really familiar with USA regulation specifics, so I will refrain from comments apart from the general "VMS is by default already more secure than 'more popular' OSes can be made". &lt;BR /&gt;&lt;BR /&gt;But I like to point out&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums1.itrc.hp.com/service/forums/helptips.do?#33" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/helptips.do?#33&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;for the way to say "Thanks" to the ones you consider have been helpfull to you.&lt;BR /&gt;&lt;BR /&gt;Proost.&lt;BR /&gt;&lt;BR /&gt;Have one on me.&lt;BR /&gt;&lt;BR /&gt;jpe</description>
      <pubDate>Wed, 25 Jun 2008 18:43:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/pci-compliance/m-p/4220664#M30314</guid>
      <dc:creator>Jan van den Ende</dc:creator>
      <dc:date>2008-06-25T18:43:01Z</dc:date>
    </item>
    <item>
      <title>Re: PCI Compliance</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/pci-compliance/m-p/4220665#M30315</link>
      <description>Jan, thanks for helping me out.  I was wondering how to assign the points.  I've done it for these questions here.</description>
      <pubDate>Wed, 25 Jun 2008 21:09:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/pci-compliance/m-p/4220665#M30315</guid>
      <dc:creator>patriceiggy</dc:creator>
      <dc:date>2008-06-25T21:09:06Z</dc:date>
    </item>
    <item>
      <title>Re: PCI Compliance</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/pci-compliance/m-p/4220666#M30316</link>
      <description>Patrice:&lt;BR /&gt;&lt;BR /&gt;This is a really serendipidous post! I JUST went through this same issue. We just passed SAS/70 type II AND PCI audits and I had to prove both TRU-64 and OpenVMS on Alpha were compliant. I have documentation I can probably share with you after a little clean-up and I'm happy to share my experience with you if it could help. Very few PCI auditors have much experience with VMS and at least for me, it took a good bit of handholding and education from me to get over their "bias of ignorance". You can contact me off forum using jack at cybermill dot com&lt;BR /&gt;&lt;BR /&gt;Jack</description>
      <pubDate>Wed, 25 Jun 2008 21:34:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/pci-compliance/m-p/4220666#M30316</guid>
      <dc:creator>Jack M. Estes II</dc:creator>
      <dc:date>2008-06-25T21:34:39Z</dc:date>
    </item>
    <item>
      <title>Re: PCI Compliance</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/pci-compliance/m-p/4220667#M30317</link>
      <description>I've posted various links at the site I referenced earlier, including the SRR and related.&lt;BR /&gt;&lt;BR /&gt;Here's the link to a tag I've scattered around the site, as well.&lt;BR /&gt;&lt;BR /&gt;64.223.189.234/taxonomy/term/9&lt;BR /&gt;&lt;BR /&gt;As for hardening a system, there's no set and no single answer.  A truly secure computer system is an entirely unusable system, after all.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 26 Jun 2008 02:15:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/pci-compliance/m-p/4220667#M30317</guid>
      <dc:creator>Hoff</dc:creator>
      <dc:date>2008-06-26T02:15:10Z</dc:date>
    </item>
    <item>
      <title>Re: PCI Compliance</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/pci-compliance/m-p/4220668#M30318</link>
      <description>Jack, I tried to contact you off forum, but received no response from th cybermill address.  Would you send an e-mail to me at p51dpc@hotmail.com so I can reply to it in order to make contact?</description>
      <pubDate>Tue, 01 Jul 2008 22:09:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/pci-compliance/m-p/4220668#M30318</guid>
      <dc:creator>patriceiggy</dc:creator>
      <dc:date>2008-07-01T22:09:22Z</dc:date>
    </item>
    <item>
      <title>Re: PCI Compliance</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/pci-compliance/m-p/4220669#M30319</link>
      <description>This may help too (if not for you for the others to know what it is about).&lt;BR /&gt;&lt;A href="http://en.wikipedia.org/wiki/PCI_DSS" target="_blank"&gt;http://en.wikipedia.org/wiki/PCI_DSS&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;There already was a question once about scanning all files for card number and other security info.&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Wed, 02 Jul 2008 06:07:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/pci-compliance/m-p/4220669#M30319</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2008-07-02T06:07:11Z</dc:date>
    </item>
    <item>
      <title>Re: PCI Compliance</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/pci-compliance/m-p/4220670#M30320</link>
      <description>In response to these concerns, we have created a template command procedure for assessing VMS systems according to  PCI DSS (Payment Card Industry Data Security Standard).&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.ljk.com/ljk/ljk_security_pci_dss.html" target="_blank"&gt;http://www.ljk.com/ljk/ljk_security_pci_dss.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;As might be guessed by thinking about the nature of software:&lt;BR /&gt;&lt;BR /&gt;A. LJK/Security can do a good job of automatically measuring compliance with items like Requirement 8.5.9 (Change user passwords at least every 90 days).&lt;BR /&gt;&lt;BR /&gt;B. LJK/Security cannot automatically measure compliance with items like Requirement 9.5 (Store media back-ups in a secure location).</description>
      <pubDate>Fri, 19 Sep 2008 11:55:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/pci-compliance/m-p/4220670#M30320</guid>
      <dc:creator>LJK Software</dc:creator>
      <dc:date>2008-09-19T11:55:04Z</dc:date>
    </item>
  </channel>
</rss>

