It shouldn't matter too much for your PCI audit. The requirement is not really that each server has exactly the same time, as long as any time difference is fairly constant and is quantifiable. It's there really so that different server's system logs can be used collectively or in concert should some later investigation into something become necessary.
If you can demonstrate to your auditor that you take steps to ensure that the mainframe clock does not drift too much and that you know what any time difference is, he should accept that, or at least note that a compensating control is in place. For example, twice a year setting the HMC system clock with some external time reference (even the Speaking Clock) and ensuring that your IPL'd systems pick up that changed time. You don't need to be second-accurate, as long as the difference is known. Brian -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] Behalf Of Chauhan, Jasbir Sent: 16 June 2008 20:03 To: [email protected] Subject: Network Time Protocol (NTP) client support question As part of the PCI audit we need to look into adopting NTP (network time protocol) on the mainframe to ensure all of our 'systems' are synchronized. Can STP provide NTP client capability to maintain 'same time' across heterogeneous platforms. Hopefully, some one out there has a solution. I'll also contact IBM to see if how they have one. We are running on a z9-BC. ----------------------------------------- Email sent from www.virginmedia.com/email Virus-checked using McAfee(R) Software and scanned for spam ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
