XYGATE & PCI COMPLIANCE PCI DSS VERSION 3 - xypro.com · xygate® & pci compliance pci dss version...
-
Upload
truongcong -
Category
Documents
-
view
248 -
download
0
Transcript of XYGATE & PCI COMPLIANCE PCI DSS VERSION 3 - xypro.com · xygate® & pci compliance pci dss version...
XYGATE® & PCI COMPLIANCE PCI DSS VERSION 3.0
A SOLUTION PAPER
MARCH 2015
XYPRO TECHNOLOGY CORPORATION
4100 GUARDIAN STREET, SUITE 100
SIMI VALLEY, CALIFORNIA 93063 U.S.A. WWW.XYPRO.COM
TELEPHONE: +1 805-583-2874
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
2
Copyright - ©XYPRO Technology Corporation, 2015. All rights reserved.
This document, as well as the software described in it, is furnished under a License Agreement or Non-disclosure Agreement. The software may be used or copied only in accordance with the terms of the Agreement. Use of this document constitutes acceptance of the terms of the Agreement. No part of this document may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, and translation to another programming language, for any purpose without the written permission of XYPRO Technology Corporation.
Trademarks
XYGATE® and XYPRO® are registered trademarks of XYPRO Technology Corporation. All other brand or product names, trademarks or registered trademarks are acknowledged as the property of their respective owners.
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
3
Table of Contents
DISCLAIMERS ........................................................................................................................................... 5
INTRODUCTION ........................................................................................................................................ 6
OVERVIEW ................................................................................................................................................. 6
PCI Application to HP NonStop™ Server Systems .............................................................................................. 8
XYGATE PRODUCTS .............................................................................................................................. 10
PCI DSS 3.0 REQUIREMENTS ................................................................................................................ 12
BUILD AND MAINTAIN A SECURE NETWORK AND SYSTEMS .......................................................... 12
Requirement 1: Install and maintain a firewall configuration to protect cardholder data ............................... 12 PCI DSS 3.0 ....................................................................................................................................................... 12 Discussion .......................................................................................................................................................... 12 XYGATE Solution(s) on the HP NonStop™ Server ........................................................................................... 12
Requirement 2: Do not use vendor supplied defaults for system passwords and other security parameters .. 13 PCI DSS 3.0 ....................................................................................................................................................... 13 Discussion .......................................................................................................................................................... 13 XYGATE Solution(s) on the HP NonStop™ Server ........................................................................................... 13
PROTECT CARDHOLDER DATA ........................................................................................................... 14
Requirement 3: Protect stored cardholder data (data at rest)............................................................................ 14 PCI DSS 3.0 ....................................................................................................................................................... 14 Discussion .......................................................................................................................................................... 15 XYGATE Solution(s) on the HP NonStop™ Server ........................................................................................... 15
MAINTAIN A VULNERABILITY MANAGEMENT PROGRAM ................................................................. 16
Requirement 4: Encrypt transmission of cardholder data across open, public networks ................................ 16 PCI DSS 3.0 ....................................................................................................................................................... 16 Discussion .......................................................................................................................................................... 16 XYGATE Solution(s) on the HP NonStop™ Server ........................................................................................... 16
Requirement 5: Protect all systems against malware and regularly update anti-virus software or programs 17 PCI DSS 3.0 ....................................................................................................................................................... 17 Discussion .......................................................................................................................................................... 17 XYGATE Solution(s) on the HP NonStop™ Server ........................................................................................... 17
Requirement 6: Develop and maintain secure systems and applications .......................................................... 18 PCI DSS 3.0 ....................................................................................................................................................... 18 Discussion .......................................................................................................................................................... 18 XYGATE Solution(s) on the HP NonStop™ Server ........................................................................................... 18
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
4
IMPLEMENT STRONG ACCESS CONTROL MEASURES ..................................................................... 19
Requirement 7: Restrict access to cardholder data by business need-to-know................................................. 19 PCI DSS 3.0 ....................................................................................................................................................... 19 Discussion .......................................................................................................................................................... 19 XYGATE Solution(s) on the HP NonStop™ Server ........................................................................................... 19
Requirement 8: Assign a unique ID to each person with computer access ....................................................... 20 PCI DSS 3.0 ....................................................................................................................................................... 20 Discussion .......................................................................................................................................................... 20 XYGATE Solution(s) on the HP NonStop™ Server ........................................................................................... 21
Requirement 9: Restrict physical access to cardholder data ............................................................................. 22 PCI DSS 3.0 ....................................................................................................................................................... 22 Discussion .......................................................................................................................................................... 22 XYGATE Solution(s) on the HP NonStop™ Server ........................................................................................... 22
REGULARLY MONITOR AND TEST NETWORKS ................................................................................. 23
Requirement 10: Track and monitor all access to network resources and cardholder data ............................ 23 PCI DSS 3.0 ....................................................................................................................................................... 23 Discussion .......................................................................................................................................................... 23 XYGATE Solution(s) on the HP NonStop™ Server ........................................................................................... 23
Requirement 11: Regularly test security systems and processes ....................................................................... 24 PCI DSS 3.0 ....................................................................................................................................................... 24 Discussion .......................................................................................................................................................... 24 XYGATE Solution(s) on the HP NonStop™ Server ........................................................................................... 24
MAINTAIN AN INFORMATION SECURITY POLICY ............................................................................... 24
Requirement 12: Maintain a policy that addresses information security for all personnel.............................. 24 PCI DSS 3.0 ....................................................................................................................................................... 24 Discussion .......................................................................................................................................................... 25 XYGATE Solution(s) on the HP NonStop™ Server ........................................................................................... 25
PCI DSS 3.0 REQUIREMENTS SUMMARY ............................................................................................ 26
THE LEADER IN NONSTOP SECURITY ................................................................................................. 61
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
5
DISCLAIMERS
XYPRO has designed this document primarily to be educational. Readers should note that this document
has not been endorsed by Visa, MasterCard, American Express, JCB International Credit Card, or the
Payment Card Security Standards Council. Issues discussed in this paper will evolve over time.
Accordingly, companies interested in these issues should seek counsel from their compliance specialist.
In determining the propriety of any specific procedure or test, the IT professional should apply his or her
own professional judgement to the specific control circumstances presented by a particular system or
information technology environment.
XYPRO makes no representations or warranties and provides no assurance that an organization’s use of
this document or of XYPRO’s XYGATE products will result in full compliance with the Payment Card
Industry Data Security Standard.
Internal controls, whether automated or manual, no matter how well designed and operated, can only
provide reasonable insurance of achieving data security. The likelihood of achievement is affected by
limitations in the company’s security environment. These include the realities that human judgement in
decision making can be faulty and that breakdowns in internal security can occur because of human
factors such as errors or inappropriate override of defined security standards and controls.
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
6
XYPRO PCI Compliance and the HP Nonstop™ Server Enterprise
INTRODUCTION
PCI requirements are imposed by the payment card
organizations. Businesses that want to offer the ability to pay
with a credit or debit card have no recourse except
compliance with PCI standards. Fortunately for businesses
that use the HP NonStopTM server, compliance becomes
easier with the use of XYGATE products.
The Payment Card Industry Data Security Standard (PCI
DSS) is a standard based on the Visa Account Information
Security (AIS) program and Cardholder Information Security
Program (CISP), MasterCard Site Data Protection (SDP)
program, American Express Data Security Operating Policy
(DSOP), Discover Information Security and Compliance
(DISC), and JCB International Credit Card security
standards. All of these companies worked together to merge
their standards into a single standard that is much easier to
implement for companies that accept payment card
transactions. The entire PCI DSS can be found at
https://www.pcisecuritystandards.org/.
This white paper shows where PCI DSS Version 3.0 is
applicable to the HP NonStopTM server enterprise and how
XYPRO products can help information technology groups in
their efforts to comply with this standard.
A summary of the PCI requirements is provided that explains
the XYGATE products applicable to each.
OVERVIEW
The PCI DSS defines how payment card (credit and debit) information should be handled. Both physical
and logical security measures are considered. The PCI Security Standards Council (PCI SSC) is the
organization that maintains the PCI standards and works to broaden the number of merchants and
processors that have implemented the standards.
“XYGATE is indispensable
with regard to audit-
compliance control,
monitoring and reporting.”
Major International Credit
Card Company
"I have evaluated/used many
security products throughout
my over 30 year career and
XYGATE is my favorite."
Top 5 U.S. Banking
Institution
"We rely heavily upon
XYGATE for our daily
security management."
Top 10 Payments
Processor
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
7
PCI DSS compliance is required by the various payment card organizations and enforced by the
agreements these organizations have with their various merchants and processors. The payment card
organizations have different implementation requirements for merchants and service providers based on
transaction volume. The following table shows some of the requirements of the various payment cards.
Payment Card Level Annual
Onsite
Assessment
Self-Assessment Quarterly Network
Assessment
Visa Service Provider 1 QSA1 No ASV2
Visa Service Provider 2 QSA No ASV
Visa Service Provider 3 No Yes ASV
Visa Merchant 1 QSA No ASV
Visa Merchant 2 No Yes ASV
Visa Merchant 3 No Yes ASV
Visa Merchant 4 No Yes ASV
MasterCard Service Provider 1 QSA No ASV
MasterCard Service Provider 2 QSA No ASV
MasterCard Service Provider 3 No Yes ASV
MasterCard Merchant 1 QSA No ASV
MasterCard Merchant 2 No Yes ASV
MasterCard Merchant 3 No Yes ASV
MasterCard Merchant 4 No Yes ASV
American Express Service
Provider
Yes No ASV
American Express Merchant 1 Yes No ASV
American Express Merchant 2 No No ASV
American Express Merchant 3 No No Recommended
1 QSA means that only a company that has been certified as a Quality Security Assessor can perform the annual onsite assessment.
2ASV means that only a company that has been certified as an Approved Scanning Vendor can perform the quarterly network
assessment.
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
8
PCI Application to HP NonStop™ Server Systems
The PCI standard must be implemented by service providers and merchants to secure the cardholder
data in an orderly consistent manner. The PCI standard is divided into twelve areas:
Area Requirement Title
Build and Maintain A Secure
Network
1 Firewalls
Build and Maintain A Secure
Network
2 Eliminate vendor defaults
Protect Cardholder Data 3 Protect stored data
Protect Cardholder Data 4 Encrypt data during transmission
Maintain A Vulnerability
Management Program
5 Use and update anti-virus software
Maintain A Vulnerability
Management Program
6 Develop and maintain secure systems and applications
Implement Strong Access
Control Measures
7 Restrict access by need-to-know
Implement Strong Access
Control Measures
8 Assign a unique ID to each user who has access
Implement Strong Access
Control Measures
9 Restrict physical access to cardholder data
Monitor and Test Networks 10 Track and monitor all access to network resources and
cardholder data
Monitor and Test Networks 11 Regularly test security systems and processes
Maintain an Information
Security Policy
12 Maintain a policy that addresses information security
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
9
Because standards have to apply to a diverse array of
merchants and service providers, which can range from
multinational, multi-billion dollar organizations to small
community banks and even smaller merchants, the PCI
standards are stated as simply as possible, without specific
details of how the goal of the standard is to be achieved.
One first step that any organization using HP NonStop™
Servers can take in meeting these standards is to obtain the
definitive books on HP NonStop™ Server security.
Securing Your HP NonStop™ Server: A Practical Handbook (ISBN:
978-1555583149) and Securing HP NonStop™ Servers in an Open
Systems World: TCP/IP, OSS and SQL (ISBN: 78-1555583446).
A second step would be to use XYPRO’s XYGATE
Compliance PRO (XSW) product. This product with its
friendly and flexible GUI can greatly assist in determining the differences between the current security
configuration of a HP NonStop™ Server and those required for the security standards defined by the PCI
DSS.
WE WROTE THE BOOK-- TWICE
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
10
XYGATE PRODUCTS
XYPRO’s XYGATE security solutions are designed to enhance the security of the HP NonStop™ server
and where no native security feature exists, provide for that security. The following table describes each
XYGATE security product referenced in this document.
XYGATE Product Description
Access Control (XAC) XAC provides action control, keystroke auditing, and allows authorized
users to execute programs using a sensitive userid.
Configuration Manager (XCF) XCF is a graphical user interface (GUI) used to configure XYGATE
products running on the HP NonStop™ host.
CMON (XCM) XCM is a supported $CMON process, with IP address controls and
user logon limitations.
Data Protection (XDP) XDP provides application-based, Format-Preserving Encryption (FPE)
and Secure-Stateless-Tokenization (SST) support without requiring
any changes to the application or to the existing database. XDP works
in conjunction with XKM and HP Security Voltage software.
Event Monitor (XEM) XEM is a MS Windows-based application that connects via a
LISTNER process to the HP NonStop™ server to extract and display
information from the XMA database tables.
Encryption Library (XEL) XEL is an API toolkit that provides all the software needed to include
encryption services in a customer-written application. This product has
been placed on the Pre-Validation List for the Federal Information
Processing Standards Publications (FIPS) 140-2: Security
Requirements for Cryptographic Modules. FIPS 140-2 validation is a
requirement for any cryptographic product which will be used in a U.S.
government agency network.
File Encryption (XFE) XFE provides file encryption, decryption, compression,
decompression, and character set translation.
Host Encryption (XHE) XHE is a communication control process that provides encryption
command security for FTP, and encryption for other NonStop server
communications interfaces, such as Telnet and ODBC.
Key Manager (XKM) XKM creates, stores, supplies, and archives keys for use by other
encryption applications, such as XFE or applications that have XEL
integrated into them.
Merged Audit (XMA) XMA is an auditing environment that provides a way to combine all
Safeguard, EMS, BASE24, BASE24-eps, iTP Web Server, and
XYGATE product audits into a single database. Reports can be
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
11
generated, or audits can be filtered for events that trigger actions such
as e-mail, EMS, SNMP, and SYSLOG alerts.
Object Security (XOS) XOS is a Security Event Exit Process (SEEP) that works with
Safeguard to provide pattern driven, predictive object oriented
security.
Process Control (XPC) XPC provides process control; allowing specific users to control
processes that are not their own.
Password Quality (XPQ) XPQ can optionally work as a Security Event Exit Process (SEEP) that
can work with Safeguard or stand alone. It provides password quality
and network password synchronization.
Password Reset (XPR) XPR enables authorized users such as Helpdesk personnel to reset
passwords and thaw userids using an easy-to-use GUI, without having
to logon to a TACL.
Audit Report Manager (XRM) XRM is a graphical user interface (GUI) tool for running host-based
XYGATE report macros, including the Safeguard Reports product.
XRM provides PC-based Audit PRO (XMA) reports. The GUI is an
easy-to-use tool even for those who are not familiar with the NonStop
server.
Secure Client (XSC) XSC provides SSL/TLS security on a MS Windows-based platform for
use with XHE or other host SSL/TLS encryption product.
Secure Shell (XSH) XSH is a Secure Shell program for the NonStop server OSS
environment.
Safeguard Manager (XSM) XSM is a MS Windows-based graphical user interface (GUI) for
managing Safeguard on the HP NonStop™ platform. XSM enables
security administrators to view, add, delete, and change any
Safeguard security parameter from a single GUI client.
Compliance PRO (XSW) XSW collects data from the NonStop server to build a series of reports
documenting compliance, deviation from Best Practice standards, and
security environment integrity.
User Authentication (XUA) XUA is a Security Event Exit Process (SEEP) that provides enhanced
authentication services including LDAP support and an interface to the
RSA SecurID server.
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
12
PCI DSS 3.0 REQUIREMENTS
The following is a discussion of each set of PCI requirements with an explanation of how XYPRO’s
XYGATE products can be used to meet the IT department compliance requirements for payment card
applications in the HP NonStop™ Server areas of the enterprise.
BUILD AND MAINTAIN A SECURE NETWORK AND SYSTEMS
Requirement 1: Install and maintain a firewall configuration to protect cardholder data
PCI DSS 3.0
Firewalls are devices that control computer traffic allowed between an entity’s networks (internal) and
untrusted networks (external), as well as traffic into and out of more sensitive areas within an entity’s
internal trusted networks. The cardholder data environment is an example of a more sensitive area within
an entity’s trusted network.
A firewall examines all network traffic and blocks those transmissions that do not meet the specified
security criteria.
All systems must be protected from unauthorized access from untrusted networks, whether entering the
system via the Internet as e-commerce, employee Internet access through desktop browsers, employee
e-mail access, dedicated connections such as business-to-business connections, via wireless networks,
or via other sources. Often, seemingly insignificant paths to and from untrusted networks can provide
unprotected pathways into key systems. Firewalls are a key protection mechanism for any computer
network.
Other system components may provide firewall functionality, as long as they meet the minimum
requirements for firewalls as defined in Requirement 1. Where other system components are used within
the cardholder data environment to provide firewall functionality, these devices must be included within
the scope and assessment of Requirement 1.
Discussion
The goal of this requirement is to assure the payment card companies that the most common external
threat, outside compromise of the network, is reduced. The most effective manner of controlling an
external access point is to put a firewall in front of it. This requirement discusses the minimum necessary
implementation of firewall security to provide outside assurance.
XYGATE Solution(s) on the HP NonStop™ Server
The majority of requirement 1 can be met with a properly implemented and maintained firewall.
The security required to limit inbound Internet traffic to IP addresses within the DMZ can be substantially
enhanced by using XCM. Use XCM to limit incoming IP addresses by service requested. This, for
example, permits the security administrator to enable one set of IP addresses for FTP use, another for
ODBC, and another for SSH access to an interactive TACL session.
Use XMA reports and alerts to document incoming IP addresses.
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
13
Requirement 2: Do not use vendor supplied defaults for system passwords and other security parameters
PCI DSS 3.0
Malicious individuals (external and internal to an entity) often use vendor default passwords and other
vendor default settings to compromise systems. These passwords and settings are well known by hacker
communities and are easily determined via public information.
Discussion
This requirement tightens security by removing all the ‘expected’ values for the initial system. Each
requirement deals with a different area of initial system setup. Many of these changes are ‘human’ driven,
requiring adherence to corporate policies, procedures, and documentation to set the values and audit
investigation to ensure that manual procedures are followed. Then the system configuration must be
monitored on a regular basis.
Requirement 2 includes a mandate to configure and maintain secure systems. On the HP NonStop™
server, this includes configuring Safeguard global parameters and protection records; OSS file security;
and third party security products such as XYGATE.
Secure systems are up-to-date systems. The system components, including the configuration of the
security environment and any third party software must be monitored and kept up to date to prevent
exploitation of known errors in either. The company’s Policies, Procedures, and Documentation manual
must include policies for upgrade management. These systems separate the development, testing, and
production groups from each other so that cross-contamination is avoided.
XYGATE Solution(s) on the HP NonStop™ Server
Use XOS to provide pattern-driven, predictive subject-operation-object security that can be defined for all
resources on the HP NonStop™ server. Access to operating system object and configuration files can be
restricted to authorized userids and authorized requesting processes. Object level security prevents
unauthorized access to resources of any sort.
Use XMA to report and alert on changes made to the security configuration, including Safeguard and
XYGATE.
Use XSW to monitor the system security configuration. By using XSW System Policies, Best Practices,
and Integrity Checks, patterns can be investigated to assure that inappropriate values are not present and
that flags will be raised if they are found. Some examples are:
Identifying userids for which passwords have expired, not been changed, or which have not been used in the recent past
Comparing Safeguard globals to Best Practice values, identifying any value that deviates from the desired
Specifically monitoring SUPER.SUPER and NULL.NULL, the two default userids that are delivered with the HP NonStop™ server.
Setting Integrity Checks for important system configuration files and startup scripts such as the PORTCONF definition file, Safeguard startup file, Spooler startup file, TCPIP startup file, TMF startup file, and XYGATE configuration files to ensure that any change is detected.
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
14
Best Practices for the HP NonStop™ server are defined in the books Securing Your HP NonStop™
Server: A Practical Handbook (ISBN: 978-1555583149) and Securing HP NonStop™ Servers in an Open
Systems World: TCP/IP, OSS and SQL (ISBN: 78-1555583446).
XSW has Best Practices pre-defined for easy monitoring to ensure that the HP NonStop™ server
configuration meets these Best Practices.
XMA can also be configured to generate e-mail, EMS, SNMPv3 or syslog alerts at the time of the change.
While XSW highlights that changes have been made to the security configuration, XMA is used to report
on who made the changes and when.
Use XUA to manage authentication. No security model is valid until there is a positive action whereby a
person accessing the computing environment proves his or her identity as an authorized user.
Use XPQ to ensure that passwords are not easy to guess and are changed on regular basis. By
automatically expiring all the passwords when the users to which these passwords apply are first created,
the security administrators can be assured that users have up-to-date passwords that have been
changed since the userids were created and are updated regularly.
Use XHE to encrypt both Telnet sessions and FTP, and can be configured to deny service if such
encryption does not occur. Use XSH to provide Secure Shell (SSH) encryption functionality between an
HP Nonstop server and other platforms that provide SSH capabilities. Use XSC to provide a PC
encryption utility that can be placed in the PC’s communication stack without interfering with existing
communication utilities. Finally, the most versatile encryption tool kit for the HP NonStop™ server, XEL, is
available for any company that chooses to implement its own encryption transactions. The XEL software
has a FIPS 140-2 certification. XYPRO’s encryption products can be used to secure any type of
administrative access to the HP NonStop™ server.
Use XHE to provide FTP command controls.
Use XAC to obtain keystroke-level auditing so no action is invisible. XAC also supplies action control, so
users can have access to sensitive actions in a controlled manner, with authentication and auditing. The
best way to obtain a Secure System is to begin with a keystroke audited TACL.
Use XPC to provide the equivalent action control for processes. In many shops, the primary use for the
master SUPER.SUPER userid is to manage processes that are otherwise secured against operations or
technical support. With XPC, these processes can be managed by authorized users without giving these
users access to the process object file or code.
PROTECT CARDHOLDER DATA
Requirement 3: Protect stored cardholder data (data at rest)
PCI DSS 3.0
Protection methods such as encryption, truncation, masking, and hashing are critical components of
cardholder data protection. If an intruder circumvents other security controls and gains access to
encrypted data, without the proper cryptographic keys, the data is unreadable and unusable to that
person. Other effective methods of protecting stored data should also be considered as potential risk
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
15
mitigation opportunities. For example, methods for minimizing risk include not storing cardholder data
unless absolutely necessary, truncating cardholder data if full PAN is not needed, and not sending
unprotected PANs using end-user messaging technologies, such as e-mail and instant messaging.
Please refer to the PCI DSS and PA-DSS Glossary of Terms, Abbreviations, and Acronyms for definitions
of “strong cryptography” and other PCI DSS terms.
Discussion
This requirement is the heart of PCI. Compromise of cardholder data must be avoided at all costs.
Measures mandated in this requirement include designing application requirements to minimize the
retention of cardholder data in memory, display of cardholder information, security of the computer’s
resources to prohibit unauthorized access to cardholder data, and encryption of the card holder data to
ensure that it is not compromised in storage or in transit. Encryption of the data also requires proper key
management procedures and software to ensure that the keys used to encrypt the data remain secure.
Enforcement of good design practices on any application that is developed to handle cardholder data
must exist within the corporation. Only properly written corporate policies, procedures, and documentation
that are enforced by management and regularly audited can increase the likelihood that any given
transaction will remain secure. Once the policies, procedures, and documentation exist, however, security
software is required to give the programmers and non-application users the tools necessary to build the
security into the HP NonStop™ server environment.
XYGATE Solution(s) on the HP NonStop™ Server
The first layer of protection of the HP NonStop™ server environment must be closest to the heart of the
operating system: object level security that prevents unauthorized access to resources of any sort.
Use XOS to provide pattern-driven predictive subject-operation-object security that can be defined for all
resources on the HP NonStop™ server. Access to cardholder data stored on disk can be restricted to
authorized userids and authorized requesting processes.
The second layer of protection is encryption, which makes any data revealed through error or malicious
action unusable until it is decrypted. XYGATE products provide three ways to encrypt cardholder
information in storage and transit.
Use XFE to encrypt and decrypt entire files.
Use XDP to provide encryption for data at rest. XDP provides Format Preserving Encryption (FPE) and
Secure-Stateless-Tokenization (SST) support without requiring any changes to the application or to the
existing database. XDP intercepts all NonStop file I/Os, seamlessly encrypting or tokenizing data as it is
written, and decrypting or de-tokenizing data as it is read. This is particularly useful for applications that
might be difficult or risky to change.
Use XEL to add encryption transactions to any application, allowing the application programs to control
what data is encrypted and when it is decrypted.
When encryption is incorporated into the environment, key management must be included. Use XKM to
provide strong key creation using split-administration and optionally allowing N of M key reconstruction.
With these features, the security administrator can define how many users are required to create a key
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
16
(split-administration) and can opt to use the N of M key reconstruction algorithm, so that initiating of key
availability requires only a subset (N of M) of the key creators to be present. Thus, the security
administrator can require five users to create the master key for the system, but only three out of the five
may be necessary to start key management services. Once keys are created, they can be used for
general encryption or decryption, or can be defined to be keys for a specific customer.
Note: Requirement 3 mentions the following:
Encryption of the entire physical or logical disk. Volume Level Encryption (VLE) is available from
HP for this purpose. However, using VLE as the sole means of protecting cardholder data is not
recommended since VLE only protects a disk after it has been removed from the system.
Destruction of keys. XYPRO’s XKM key management software does not destroy keys. Once a
key has been used for an encryption operation, it is retained forever. It can be archived to remove
it from daily use, but never destroyed. A key that has been destroyed cannot be recovered for use
in decrypting old data, which would be lost without the proper decryption key.
Use XHE to provide FTP command controls.
MAINTAIN A VULNERABILITY MANAGEMENT PROGRAM
Requirement 4: Encrypt transmission of cardholder data across open, public networks
PCI DSS 3.0
Sensitive information must be encrypted during transmission over networks that are easily accessed by
malicious individuals. Misconfigured wireless networks and vulnerabilities in legacy encryption and
authentication protocols continue to be targets of malicious individuals who exploit these vulnerabilities to
gain privileged access to cardholder data environments.
Discussion
Requirement 4 deals with cardholder data in transit and states that encryption transmission of cardholder
data is required. Some of the acceptable encryption protocols, such as SSL and TLS are mentioned, but
other protocols such as 3DES or AES are not addressed. Both of these protocols are defined by NIST
and ISO standards, and SSL/TLS is defined in RFC 2246.
XYGATE Solution(s) on the HP NonStop™ Server
Use XDP to provide encryption for data in transit between computer systems. XDP provides Format
Preserving Encryption (FPE) and Secure-Stateless-Tokenization (SST) support without requiring any
changes to the application or to the existing database. XDP intercepts all NonStop file I/Os, seamlessly
encrypting or tokenizing data as it is written, and decrypting or de-tokenizing data as it is read. This is
particularly useful for applications that might be difficult or risky to change.
XHE on the HP NonStop™ server works with SSL/TLS encryption modules on other hosts or personal
computer platforms to encrypt and decrypt traffic from any TCPIP port on the HP NonStop™ server
system. For example, XHE encrypts and decrypts FTP traffic to another HP NonStop™ server, IBM
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
17
platform machine, MS Windows computer, as long as the target machine also supports SSL/TLS
encryption. XHE works with Telnet, FTP, ODBC, RSC, and HTTP.
Use XSH to provide Secure Shell (SSH) encryption functionality between an HP Nonstop server and
other platforms that provide SSH capabilities including Secure Tunneling, SFTP and SCP.
Use XSC to provide client side SSL/TLS encryption from MS-Windows platforms to an HP NonStop™
server.
Requirement 5: Protect all systems against malware and regularly update anti-virus software or programs
PCI DSS 3.0
Malicious software, commonly referred to as “malware”—including viruses, worms, and Trojans—enters
the network during many business approved activities including employee e-mail and use of the Internet,
mobile computers, and storage devices, resulting in the exploitation of system vulnerabilities. Anti-virus
software must be used on all systems commonly affected by malware to protect systems from current and
evolving malicious software threats. Additional anti-malware solutions may be considered as a
supplement to the anti-virus software; however, such additional solutions do not replace the need for anti-
virus software to be in place.
Discussion
This requirement exists to define reasonable protection for end-user platforms and small processing
systems where connectivity to the Internet for both secure and non-secure activity leaves the system
open to attack from programs that perform malicious action. The most common malicious program, or
‘malware’, is a computer virus that enters through the network connection, installs itself into the system,
and performs some sort of inappropriate activity at some point in the future. Many companies offer
protection against this malware, with a suite of software tools that are referred to as ‘anti-virus’ software.
Traditional consumer anti-virus protection is not available for the HP NonStop™ server. The most likely
malware to be found on the HP NonStop™ server is a Trojan Horse, which is a program that looks
innocuous but performs malicious activity to the detriment of the application owner.
XYGATE Solution(s) on the HP NonStop™ Server
Traditional consumer anti-virus is not applicable to the HP NonStop™ server
Use XSW to watch for Trojan Horses using the Integrity Check feature. Integrity Checks investigate
defined lists of resources such as files or sub volumes to see if the current characteristics of the resource
match the previously stored characteristics. An integrity check for a file will check characteristics such as
the EOF, Last Create Date, Last Modification Date and File Code against the previously stored values.
Since most malware will causes changes in these file characteristics, any file that has changed is flagged
for investigation. File integrity can also be checked using file hashing. XSW permits the security
administrator to define actions that will be performed if Integrity Check violations are found. For example,
e-mail can be sent warning security administrators of the integrity check failure.
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
18
Requirement 6: Develop and maintain secure systems and applications
PCI DSS 3.0
Unscrupulous individuals use security vulnerabilities to gain privileged access to systems. Many of these
vulnerabilities are fixed by vendor provided security patches, which must be installed by the entities that
manage the systems. All systems must have all appropriate software patches to protect against the
exploitation and compromise of cardholder data by malicious individuals and malicious software.
Note: Appropriate software patches are those patches that have been evaluated and tested sufficiently to
determine that the patches do not conflict with existing security configurations. For in-house developed
applications, numerous vulnerabilities can be avoided by using standard system development processes
and secure coding techniques.
Discussion
Secure systems are up-to-date systems. System components and any third party software must be
regularly updated to prevent exploitation of known errors in either. The company’s Policies, Procedures,
and Documentation manual must include policies for upgrade management. These systems separate the
development, testing, and production groups from each other so that cross-contamination is avoided.
Requirement 6 includes mandates to develop secure applications and to implement change control for
both the operating system and applications. Secure applications must be developed by the application
team, or, if the application has been purchased from a third party, the third party must be contacted to
ensure that these requirements are met by the third party. These requirements are primarily policy driven.
Procedures for upgrading the operating system and applications must include security considerations at
all steps.
Secure applications begin with a secure design. This design is supplied to a programming group that
understands the principles of secure computing and builds these details into the environment. The
programming group supplies completed code to a testing group, which tests in an environment separate
from that of the developers who built the application. This testing group works with the requirements to
ensure that the code meets the requirements of the application and the security requirements in the
company’s policies, procedures, and documentation guides. Finally, a production group integrates the
code into a separate production environment, which is not normally accessible to the development or
testing groups.
For applications that deal with cardholder data, secure application design includes encryption of data at
rest and data in transit.
XYGATE Solution(s) on the HP NonStop™ Server
XYGATE contributes to secure change control procedures.
XAC supplies keystroke auditing so that no action is invisible. It also supplies action control, so users can
have access to sensitive actions in a controlled manner, with authentication and auditing. So, a security
rule can be created that allows an authorized user to upgrade applications files, but not execute those
files.
XOS works with Safeguard to provide pattern-controlled, predictive security that provides user, operation,
and object control. XOS can ensure that application files conform to approved naming conventions and
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
19
can only be placed on approved volumes and sub volumes, by approved users. So, a security rule can be
created that allows an authorized user to upgrade applications files, but not execute those files.
Secure applications require encryption. XDP and XEL provide application data encryption services.
XDP provides Format Preserving Encryption (FPE) and Secure-Stateless-Tokenization (SST) support
without requiring any changes to the application or to the existing database. XDP intercepts all NonStop
file I/Os, seamlessly encrypting or tokenizing data as it is written, and decrypting or de-tokenizing data as
it is read. This is particularly useful for applications that might be difficult or risky to change.
XEL is a toolkit for application development that provides encryption API calls. With XEL, the developer
can code the application to request keys from the XKM key management system or create net keys,
establish encryption sessions, encrypt and decrypt information, create a Message Authentication Code
(MAC) or validate a MAC, or destroy an encryption session as needed throughout processing.
The XKM key management system can work with XEL for application encryption services. It can also be
used with the XFE file encryption system that encrypts and decrypts, compresses and decompresses,
and translates files for secure transmission. XKM creates keys, maintains key, supplies keys on request,
and archives keys as needed.
IMPLEMENT STRONG ACCESS CONTROL MEASURES
Requirement 7: Restrict access to cardholder data by business need-to-know
PCI DSS 3.0
To ensure critical data can only be accessed by authorized personnel, systems and processes must be in place to limit access based on need to know and according to job responsibilities. “Need to know” is when access rights are granted to only the least amount of data and privileges needed to perform a job.
Discussion
Good security can be defined with three phrases:
1. Need to know 2. Least privileges 3. Separation of duties
Requirement 7 deals with the first two. These principles restrict access to a resource to only those
individuals who must have access to that resource in order to perform their jobs.
XYGATE Solution(s) on the HP NonStop™ Server
All XYGATE modules have as their core purpose the implementation of security rules that provide
separation of duties, limit access to need to know and provide the least privilege necessary for the
execution of a person’s duties. One module deals with the authentication that will be needed to provide
secured authorization. Three modules limit access so that all access that is not explicitly approved will be
denied.
XUA manages authentication. No security model is valid until there is a positive action whereby a person
accessing the computing environment proves his or her identity as an authorized user.
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
20
XOS secures resources at the subject-operation-object level, where operations are the basic computer
operations of open, read, write, execute, and purge. All subjects and objects can be defined as patterns,
so the security can be predictive, which means that it is in place and enforceable even before the
resource exists on the system. For example, XOS can be defined to enforce a rule that says only the
userid defined as the owner for the data can open any of the files in which the data is stored and even
then, can only open it with the specified authorized programs. This means that any malicious use of the
userid that owns the data still won’t yield access to the data, because malicious use does not generally
occur from within authorized programs, and unauthorized programs won’t be allowed access.
XAC secures resources using the user action model. All security rules in XAC are based on the action as
perceived by the user. So, a security rule can be created that allows an authorized user to start an
application, but not access the data in the application or modify the programs that make up the
application. Another sample security rule is one that allows a user access to a privileged program in order
to execute a small subset of commands.
XCM manages three separate security actions - processing a logon, starting a program, and altering the
priority of an executing program.
XHE provides FTP command controls.
Requirement 8: Assign a unique ID to each person with computer access
PCI DSS 3.0
Assigning a unique identification (ID) to each person with access ensures that each individual is uniquely
accountable for their actions. When such accountability is in place, actions taken on critical data and
systems are performed by, and can be traced to, known and authorized users and processes.
The effectiveness of a password is largely determined by the design and implementation of the
authentication system—particularly, how frequently password attempts can be made by an attacker, and
the security methods to protect user passwords at the point of entry, during transmission, and while in
storage.
Note: These requirements are applicable for all accounts, including point-of-sale accounts, with
administrative capabilities and all accounts used to view or access cardholder data or to access systems
with cardholder data. This includes accounts used by vendors and other third parties (for example, for
support or maintenance).
However, Requirements 8.1.1, 8.2, 8.5, 8.2.3 through 8.2.5, and 8.1.6 through 8.1.8 are not intended to
apply to user accounts within a point-of sale payment application that only have access to one card
number at a time in order to facilitate a single transaction (such as cashier accounts).
Discussion
This requirement is concerned with user authentication controls and userid maintenance controls and
procedures. A user logs on to a userid with authentication credentials that are unique to the person -
something he or she knows, something he or she has, something he or she is, or a combination of the
three. The authentication information must remain private; the person who uses the userid must
understand that the information is to remain private, and steps must be taken to assure that
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
21
authentication information is reliable. Without these steps, any subsequent authorization made based on
the authentication cannot be trusted.
The most secure first step for authentication is to commit to the “one person - one userid” model. That is,
one person has one userid. No two people share a userid. No user has more than one userid. With the
assurance that only one person is using one userid, authentication of the userid ensures that the person
performing any authorized actions is indeed the real person who is really allowed to take these actions.
The second step is to make the authentication operation less open to compromise. The use of a
password to authorize a user relies on something the user knows. Since it is intangible, it can be stolen or
revealed without the authorized user knowing about the loss. Also, since it is intangible, it has to be
remembered. By adding-on a token device or biometric, the chance of unauthorized use drops
substantially, since the theft of a token means that the authorized user can’t have access to the system,
and the biometric value cannot be stolen at all.
Finally, this requirement defines measures to take to reduce the opportunity for an unauthorized user to
attempt access.
XYGATE Solution(s) on the HP NonStop™ Server
XSM is the tool to use to create userids. XSM interfaces with Safeguard and with the XYPRO Personnel
Database, allowing the userid that is created to be associated with the demographic data. Details from
the customizable Personnel Database are also available with XPR, the help desk application that resets
passwords for already created userids. XSM can also be used to revoke access in any of three ways. The
user can be ‘frozen’, which does not delete the userid but prevents any logon. Any batch jobs owned by
the user will continue to execute. Secondly, the user can be ‘expired’, which also does not delete the
userid but prevents any logons. Batch jobs will not execute, since the Netbatch system checks the
authentication of the user before starting the job. Finally, XSM can be used to delete the userid, which will
prevent logons and prevent batch jobs from executing. Additionally, a deleted userid leaves disk files
previously owned by the user without a valid owner, leaving the disk files ‘orphaned’.
XUA performs authorization. It integrates with Safeguard, and it has extensions that support LDAP and
interface with a corporate RSA ACE Server. XUA controls who can logon to which services on the HP
NonStop™ server based on rules that match userids to ports and to requesting processes. Additionally,
XUA has extended controls that define what happens when too many invalid password attempts occur.
For example, one set of users can have their privileges suspended for 30 minutes after six bad attempts
and another group can have their access to the HP NonStop™ server frozen.
In an environment where Safeguard is not in use, XCM can provide controls on a logon based on the
incoming party’s IP address and the userid the user is logging on to.
All XYGATE modules that perform a logon or verify the userid’s identity before executing a sensitive
command support the use of an RSA SecureID token in addition to the password.
All XYGATE modules that make up the MS Windows-based XYGATE Configuration and Auditing package
provide built-in password encryption from the PC to the HP NonStop™ server so a network sniffer cannot
be used to steal passwords.
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
22
XPQ can be used with or without Safeguard to provide password quality and network password change
controls. In either case, XPQ can set a password so that the user must change it as part of the first logon.
Password content can be limited to rules, such as it must contain one letter, one number, one special
character and cannot have more than 2 repeating characters. Passwords can also be generated, if
desired. The value of a password can be split among many users. Password change intervals can be
defined and a password history is retained, allowing the security administrator to preclude users from re-
using previous passwords.
XSW monitors a user’s access to system resources. Regular reports can be generated showing userids
that have not logged on the last 30, 60 or 90 days, users that have expired, users with passwords that
have expired, how the XPQ and XUA Security Event Exit Processes (SEEPs) are defined, what orphaned
files exist, and what the current settings are for the Safeguard global user and authentication controls.
XMA provides reporting on a user's activities and can be configured to generate alerts when particular
actions are attempted. Also, use XMA to produce reports and alerts for changes to user and
authentication configuration as well as the security configurations for both applications and the operating
system.
XAC keystroke-audited sessions provide a ‘password’ timeout facility. After a set amount of time, the user
is required to re-authenticate his or her identity before execution can continue. Additionally, XAC can be
configured to control access to user actions that affect databases containing cardholder information. XAC
can authenticate the user to ensure that the user is authorized to perform actions such as using FUP to
load the database or using SQLCI to generate ad-hoc queries against the database.
At the system resource level, XOS can be used to define who can access specific system resources,
such as the programs that manage the cardholder database.
Requirement 9: Restrict physical access to cardholder data
PCI DSS 3.0
Any physical access to data or systems that house cardholder data provides the opportunity for
individuals to access devices or data and to remove systems or hardcopies, and should be appropriately
restricted. For the purposes of Requirement 9, “onsite personnel” refers to full-time and part-time
employees, temporary employees, contractors and consultants who are physically present on the entity’s
premises. A “visitor” refers to a vendor, guest of any onsite personnel, service workers, or anyone who
needs to enter the facility for a short duration, usually not more than one day. “Media” refers to all paper
and electronic media containing cardholder data.
Discussion
This requirement is not applicable to HP NonStop™ server. This is a function of the physical access
controls to the computing environment and is defined in Corporate Policies, Procedures and
Documentation.
XYGATE Solution(s) on the HP NonStop™ Server
Not applicable.
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
23
REGULARLY MONITOR AND TEST NETWORKS
Requirement 10: Track and monitor all access to network resources and cardholder data
PCI DSS 3.0
Logging mechanisms and the ability to track user activities are critical in preventing, detecting, or
minimizing the impact of a data compromise. The presence of logs in all environments allows thorough
tracking, alerting, and analysis when something does go wrong. Determining the cause of a compromise
is very difficult, if not impossible, without system activity logs.
Discussion
Requirement 10 deals with auditing access to system resources and cardholder data. The primary
principle of auditing accountability is showing who did which operation to what secured resource. This
can only be achieved if the audit data is complete, accurate, unaltered, and available when needed.
Requirement 10 also deals with storage of audit data and the integrity of the audit data, including the
prevention of tampering by moving audit information off box and securing the audit logs themselves.
XYGATE Solution(s) on the HP NonStop™ Server
All HP NonStop™ server-based XYGATE modules except XMA have built-in auditing that tracks all
security actions that the module has taken, including the time and date, the originating user, the userid
under which the action executed, details of the action, and a session id that allows association of all
actions taken in the same session. XMA reports on actions and thus does not execute any actions.
All XYGATE modules that audit, support the specification of up to nine different and simultaneous audit
files. Three types of audit files are supported. First, audits can be written to either local or remote disk file
locations, so audit traffic can be routed to a central HP NonStop™ server. Next, audits can be written to
processes, allowing the HP NonStop™ Server utility EMS to be used to monitor outputs or any third-party
monitor process. Finally, audits can be written to an external IP address, allowing audits to be written off-
box to a secured location such as a centralized log server.
Use XOS to secure audit files against unauthorized viewing or alterations. On HP NonStop™ servers,
XOS can be used to secure all system resources, including audit files. Pattern entries can be created that
allow audit files to be written to by authorized programs that perform the normal auditing activity and read
only by authorized individuals who generate reports while screening out all other access.
XRM works on the PC to run and display audit reports. The security for XRM allows access to these
reports to be limited to those who have authorized access.
XSW generates system integrity and security policy violation reports.
Use XMA to satisfy the requirement that audit data be immediately backed up to a centralized log server.
XMA can send audit data off-box, via SYSLOG, to a Security Information and Event Management (SIEM)
appliance.
Use XOS and XMA to satisfy the requirement that audit logs be monitored for alterations. XOS can
secure audit files and audit all access to them. XMA can send alerts if audit files are altered by anyone
other than the program generating the audit.
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
24
XEM, an adjunct to XMA, runs on the PC to display audit events as they happen. Alerts can be configured
to trigger emails, popup windows, and sounds when specific events occur. The security for XEM allows
access to audit information to be limited to authorized users.
Use XMA to satisfy the requirement for retention of audit logs. XMA can move all specified audit data into
a single SQL database that can have defined retention and archival schedules.
Requirement 11: Regularly test security systems and processes
PCI DSS 3.0
Vulnerabilities are being discovered continually by malicious individuals and researchers, and being
introduced by new software. System components, processes, and custom software should be tested
frequently to ensure security controls continue to reflect a changing environment.
Discussion
This requirement discusses the need to regularly test the security environment and to watch for
unauthorized changes to important system content and configuration files. Some of the testing as defined
in this requirement must be performed by organizations external to the company being tested. Other
portions of the testing and regular monitoring can be performed with software running on the HP
NonStop™ servers.
XYGATE Solution(s) on the HP NonStop™ Server
XYPRO products deal specifically with the requirements for monitoring unusual system events that can
indicate that an intruder is attempting to gain access to the system and monitoring critical system files and
configurations to ensure that they have not been subjected to unauthorized modification. Use XMA to
meet these requirements. XMA reports on system activity and can be configured to generate e-mail,
EMS, SNMP, and SYSLOG alerts when specified critical security events occur.
XEM, an adjunct to XMA, runs on the PC to display audit events as they happen. Alerts can be configured
to trigger emails, popup windows, and sounds when specific events occur. The security for XEM allows
access to audit information to be limited to authorized users.
XSW regularly compares the current security configuration of a system to the ideal configuration defined
in Best Practices and to the configuration of the system at the most recent previous collection, allowing
the security administrator to find deviations from the authorized configuration.
XSW generates system integrity and security policy violation reports.
MAINTAIN AN INFORMATION SECURITY POLICY
Requirement 12: Maintain a policy that addresses information security for all personnel
PCI DSS 3.0
A strong security policy sets the security tone for the whole entity and informs personnel what is expected
of them. All personnel should be aware of the sensitivity of data and their responsibilities for protecting it.
For the purposes of Requirement 12, “personnel” refers to full-time and part-time employees, temporary
employees, contractors and consultants who are “resident” on the entity’s site or otherwise have access
to the cardholder data environment.
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
25
Discussion
Requirement 12 is primarily about policies and procedures. It deals with the creation of security policies
for the organization. Necessary portions of the policy are delineated, procedures that implement the
policy are mandated, and dissemination of the policy to all interested parties is defined. Handling of
security breaches is dealt with. This requirement also requires other companies that do business with this
company to follow these same security goals.
For the purposes of this requirement, "employees" refers to full-time and part-time employees, temporary
employees and personnel, and contractors and consultants who are "resident" on the company's site.
XYGATE Solution(s) on the HP NonStop™ Server
XYGATE modules provide tools for accomplishing these goals.
Meeting requirement 12 is easier with tools such as XMA and XSW. These tools are used to prove that
the required procedures are in place and in use.
XMA provides an alert feature, so that the appropriate individuals can be apprised of any attempted
system intrusions. Use XMA to generate e-mail or SMS alerts for activity that fits the company-specified
security events. Use XEM to call attention to security events and generate alerts.
Use XSW to provide user access maps for system resources.
Use XAC to force disconnects within any session, regardless of utility.
Use XAC to force disconnects within any session, regardless of utility. XHE also provides inactivity
timeouts for FTP, ODBC, and other types of TCP/IP sessions.
Use XCM to allow vendors to logon through only approved IP addresses and can optionally enforce
session encryption on a vendor. By using NetBatch to switch XCM control rules in and out, vendor access
can be enabled and disabled in a controlled, audited manner.
Use XAC, XHE, and XCM to help control copying cardholder data to user's PCs or other portable storage
media.
Use XSM to provide user administration with controls to limit which user can perform which tasks and
audit who performed each action. XPQ allows security administrators to define who can reset passwords
for which sets of users. XPR can be installed on the PCs of authorized help desk personnel to allow them
to reset passwords for the sets of users for which they are authorized to reset the passwords. XRM
provides access to run and view audit reports to authorized users.
The goal behind all XYGATE security software is to monitor and control all access to data. Use XOS to
secure files. Use XAC to limit access to data via utilities such as SQL.
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
26
PCI DSS 3.0 REQUIREMENTS SUMMARY
PCI DSS 3.0 Requirement XYPRO Remarks
1: Install and maintain a firewall configuration to protect cardholder data
This requirement can be met with
corporate policies, procedures, and
documentation.
1.1 Establish and implement firewall and router configuration standards that include the following:
This requirement can be met with
corporate policies, procedures, and
documentation.
1.1.1 A formal process for approving and testing all network
connections and changes to the firewall and router configurations
This requirement can be met with
corporate policies, procedures, and
documentation.
1.1.2 Current network diagram that identifies all
connections between the cardholder data environment and other networks, including any wireless networks
This requirement can be met with
corporate policies, procedures, and
documentation.
1.1.3 Current diagram that shows all cardholder data flows
across systems and networks This requirement can be met with
corporate policies, procedures, and
documentation.
1.1.4 Requirements for a firewall at each Internet
connection and between any demilitarized zone (DMZ) and the internal network zone
This requirement can be met with
corporate policies, procedures, and
documentation.
1.1.5 Description of groups, roles, and responsibilities for management of network components
This requirement can be met with
corporate policies, procedures, and
documentation.
1.1.6 Documentation and business justification for use of all services, protocols, and ports allowed, including documentation of security features implemented for those protocols considered to be insecure. Examples of insecure services, protocols, or ports include
but are not limited to FTP, Telnet, POP3, IMAP, and SNMP
v1 and v2.
This requirement can be met with
corporate policies, procedures, and
documentation.
1.1.7 Requirement to review firewall and router rule sets at least every six months
This requirement can be met with
corporate policies, procedures, and
documentation.
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
27
PCI DSS 3.0 Requirement XYPRO Remarks
1.2 Build firewall and router configurations that restrict connections between untrusted networks and any system components in the cardholder data environment. Note: An “untrusted network” is any network that is external
to the networks belonging to the entity under review, and/or
which is out of the entity's ability to control or manage.
This requirement involves network
configuration external to the NonStop
server.
1.2.1 Restrict inbound and outbound traffic to that which is
necessary for the cardholder data environment, and specifically deny all other traffic.
This requirement involves network
configuration external to the NonStop
server.
XCM can be used on the NonStop to limit
incoming IP addresses by the service
requested.
1.2.2 Secure and synchronize router configuration files. This requirement involves network
configuration external to the NonStop
server.
1.2.3 Install perimeter firewalls between all wireless networks and the cardholder data environment, and configure these firewalls to deny or, if traffic is necessary for business purposes, permit only authorized traffic between the wireless environment and the cardholder data environment.
This requirement involves network
configuration external to the NonStop
server.
1.3 Prohibit direct public access between the Internet and any system component in the cardholder data environment.
This requirement involves network
configuration external to the NonStop
server.
1.3.1 Implement a DMZ to limit inbound traffic to only system components that provide authorized publicly accessible services, protocols, and ports.
This requirement involves network
configuration external to the NonStop
server.
1.3.2 Limit inbound Internet traffic to IP addresses within the DMZ.
This requirement involves network
configuration external to the NonStop
server.
1.3.3 Do not allow any direct connections inbound or
outbound for traffic between the Internet and the cardholder data environment.
This requirement involves network
configuration external to the NonStop
server.
1.3.4 Implement anti-spoofing measures to detect and
block forged source IP addresses from entering the network.
This requirement involves network
configuration external to the NonStop
server.
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
28
PCI DSS 3.0 Requirement XYPRO Remarks
(For example, block traffic originating from the Internet with
an internal source address.)
1.3.5 Do not allow unauthorized outbound traffic from the
cardholder data environment to the Internet. This requirement involves network
configuration external to the NonStop
server.
1.3.6 Implement stateful inspection, also known as dynamic
packet filtering. (That is, only “established” connections are allowed into the network.)
This requirement involves network
configuration external to the NonStop
server.
1.3.7 Place system components that store cardholder data
(such as a database) in an internal network zone, segregated from the DMZ and other untrusted networks.
This requirement involves network
configuration external to the NonStop
server.
1.3.8 Do not disclose private IP addresses and routing information to unauthorized parties. Note: Methods to obscure IP addressing may include, but are not limited to:
Network Address Translation (NAT) Placing servers containing cardholder data behind proxy
servers/firewalls, Removal or filtering of route advertisements for private
networks that employ registered addressing, Internal use of RFC1918 address space instead of
registered addresses.
This requirement involves network
configuration external to the NonStop
server.
1.4 Install personal firewall software on any mobile and/or employee-owned devices that connect to the Internet when outside the network (for example, laptops used by employees), and which are also used to access the network. Firewall configurations include: - Specific configuration settings are defined for personal firewall software. - Personal firewall software is actively running. - Personal firewall software is not alterable by users of
mobile and/or employee-owned devices.
This requirement involves network
configuration external to the NonStop
server.
1.5 Ensure that security policies and operational procedures for managing firewalls are documented, in use, and known to all affected parties.
This requirement involves network
configuration external to the NonStop
server.
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
29
PCI DSS 3.0 Requirement XYPRO Remarks
2: Do not use vendor-supplied defaults for system
passwords and other security parameters
All XYGATE modules.
2.1 Always change vendor-supplied defaults and remove or disable unnecessary default accounts before installing a
system on the network. This applies to ALL default passwords, including but not
limited to those used by operating systems, software that
provides security services, application and system
accounts, point-of-sale (POS) terminals, Simple Network
Management Protocol (SNMP) community strings, etc.).
XSW can be used to monitor for HP-
supplied accounts.
XPQ can be used to force system
passwords to change.
2.1.1 For wireless environments connected to the cardholder data environment or transmitting cardholder data, change ALL wireless vendor defaults at installation, including but not limited to default wireless encryption keys, passwords, and SNMP community strings.
This requirement involves network
configuration external to the NonStop
server.
2.2 Develop configuration standards for all system components. Assure that these standards address all known security vulnerabilities and are consistent with industry-accepted system hardening standards. Sources of industry-accepted system hardening standards may include, but are not limited to:
XSW can be used to compare NonStop
server security to Best Practices as
defined in the books “Securing Your HP
NonStop Server: A Practical Handbook”
(ISBN: 978-1555583149) and “Securing
HP NonStop Servers In An Open Systems
World”: TCP/IP, OSS and SQL (ISBN: 78-
1555583446).
2.2.1 Implement only one primary function per server to prevent functions that require different security levels from co-existing on the same server. (For example, web servers, database servers, and DNS should be implemented on separate servers.) Note: Where virtualization technologies are in use,
implement only one primary function per virtual system
component.
This requirement can be met with
corporate policies, procedures, and
documentation.
XSW can be used for monitoring.
2.2.2 Enable only necessary services, protocols, daemons,
etc., as required for the function of the system.
XSW can be used for monitoring.
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
30
PCI DSS 3.0 Requirement XYPRO Remarks
2.2.3 Implement additional security features for any required services, protocols, or daemons that are considered to be insecure—for example, use secured technologies such as SSH, S-FTP, SSL, or IPSec VPN to protect insecure services such as Net
XHE, XSH, XSC, and XEL can be used.
2.2.4 Configure system security parameters to prevent misuse.
All XYGATE modules.
2.2.5 Remove all unnecessary functionality, such as scripts, drivers, features, subsystems, file systems, and unnecessary web servers
Use XSW to identify this unnecessary
functionality.
2.3 Encrypt all non-console administrative access using strong cryptography. Use technologies such as SSH, VPN, or SSL/TLS for web-based management and other non-console administrative access.
Use XHE, XSH, XSC, and XEL for this
encryption.
2.4 Maintain an inventory of system components that are in scope for PCI DSS.
This requirement can be met with
corporate policies, procedures, and
documentation.
2.5 Ensure that security policies and operational procedures for managing vendor defaults and other security parameters are documented, in use, and known to all affected parties.
This requirement can be met with
corporate policies, procedures, and
documentation.
2.6 Shared hosting providers must protect each entity’s hosted environment and cardholder data. These providers must meet specific requirements as detailed in Appendix A: Additional PCI DSS Requirements for Shared Hosting Providers.
All XYGATE modules.
3: Protect stored cardholder data XOS can be used for object level security.
XDP can be used for application- and
database-level security without changes to
the application or database.
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
31
PCI DSS 3.0 Requirement XYPRO Remarks
3.1 Keep cardholder data storage to a minimum by implementing data retention and disposal policies, procedures and processes that include at least the following for all cardholder data (CHD) storage: - Limiting data storage amount and retention time to that which is required for legal, regulatory, and business requirements - Processes for secure deletion of data when no longer needed - Specific retention requirements for cardholder data - A quarterly process for identifying and securely deleting stored cardholder data that exceeds defined retention.
This requirement can be met with
corporate policies, procedures, and
documentation.
3.2 Do not store sensitive authentication data after authorization (even if encrypted). If sensitive authentication data is received, render all data unrecoverable upon completion of the authorization process. It is permissible for issuers and companies that support issuing services to store sensitive authentication data if: - There is a business justification and - The data is stored securely. Sensitive authentication data includes the data as cited in
the following Requirements 3.2.1 through 3.2.3:
This requirement can be met with
corporate policies, procedures, and
documentation.
3.2.1 Do not store the full contents of any track (from the magnetic stripe located on the back of a card, equivalent data contained on a chip, or elsewhere). This data is alternatively called full track, track, track 1, track 2, and magnetic-stripe data. Note: In the normal course of business, the following data elements from the magnetic stripe may need to be retained: - The cardholder’s name - Primary account number (PAN) - Expiration date - Service code To minimize risk, store only these data elements as needed
for business.
This requirement can be met with
corporate policies, procedures, and
documentation.
3.2.2 Do not store the card verification code or value (three-
digit or four-digit number printed on the front or back of a payment card) used to verify card-not-present transactions.
This requirement can be met with
corporate policies, procedures, and
documentation.
3.2.3 Do not store the personal identification number (PIN)
or the encrypted PIN block. This requirement can be met with
corporate policies, procedures, and
documentation.
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
32
PCI DSS 3.0 Requirement XYPRO Remarks
3.3 Mask PAN when displayed (the first six and last four digits are the maximum number of digits to be displayed), such that only personnel with a legitimate business need can see the full PAN.
Note: This requirement does not supersede stricter
requirements in place for displays of cardholder data—for
example, legal or payment card brand requirements for
point-of-sale (POS) receipts.
This requirement can be met with
corporate policies, procedures, and
documentation.
3.4 Render PAN unreadable anywhere it is stored
(including on portable digital media, backup media, and in logs) by using any of the following approaches: - One-way hashes based on strong cryptography, (hash must be of the entire PAN) - Truncation (hashing cannot be used to replace the truncated segment of PAN) - Index tokens and pads (pads must be securely stored) - Strong cryptography with associated key-management processes and procedures. Note: It is a relatively trivial effort for a malicious individual to reconstruct original PAN data if they have access to both the truncated and hashed version of a PAN. Where hashed and truncated versions of the same PAN are present in an entity’s environment, additional controls should be in place to ensure that the hashed and truncated versions cannot be correlated to reconstruct the original PAN.
XDP can be used in conjunction with
Voltage security software to provide
Format Preserving Encryption (FPE) or
Secure-Stateless-Tokenization (SST) for
PAN and other sensitive data without
application or database changes.
XEL can be used to provide strong
cryptography with associated key
management processes. XEL provides
tools to be included in any in-house
development.
XFE can be used to encrypt a file on one
system and decrypted on another, as long
as XFE is installed on both.
Use XKM for FIPS-validated encryption
key management. XKM is required with
XDP and XFE.
3.4.1 If disk encryption is used (rather than file- or column-level database encryption), logical access must be managed separately and independently of native operating system authentication and access control mechanisms (for example, by not using local user account databases or general network login credentials). Decryption keys must not be associated with user accounts.
Volume Level Encryption (VLE) is
available from HP for this purpose.
However, using VLE as the sole means of
protecting cardholder data is not
recommended since VLE only protects a
disk after it has been removed from the
system.
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
33
PCI DSS 3.0 Requirement XYPRO Remarks
3.5 Document and implement procedures to protect keys used to secure stored cardholder data against disclosure and misuse:
Note: This requirement applies to keys used to encrypt
stored cardholder data, and also applies to key-encrypting
keys used to protect data-encrypting keys—such key-
encrypting keys must be at least as strong as the data-
encrypting key.
This requirement can be met with
corporate policies, procedures, and
documentation.
3.5.1 Restrict access to cryptographic keys to the fewest number of custodians necessary.
XOS can be used to protect cryptographic
keys at the resource level.
XDP, XKM, and XEL can be used to
integrate encryption into the application.
3.5.2 Store secret and private keys used to encrypt/decrypt
cardholder data in one (or more) of the following forms at all times: - Encrypted with a key-encrypting key that is at least as strong as the data-encrypting key, and that is stored separately from the data-encrypting key - Within a secure cryptographic device (such as a host security module (HSM) or PTS-approved point-of-interaction device) - As at least two full-length key components or key shares, in accordance with an industry-accepted method Note: It is not required that public keys be stored in one of
these forms.
XOS can be used to protect cryptographic
keys at the resource level.
XDP, XKM, and XEL can be used to
integrate encryption into the application.
3.5.3 Store cryptographic keys in the fewest possible
locations.
XDP, XKM, and XEL can be used to
integrate encryption into the application.
3.6 Fully document and implement all key-management
processes and procedures for cryptographic keys used for encryption of cardholder data, including the following:
Note: Numerous industry standards for key management
are available from various resources including NIST, which
can be found at http://csrc.nist.gov.
This requirement can be met with
corporate policies, procedures, and
documentation.
3.6.1 Generation of strong cryptographic keys XDP, XKM, and XEL can be used to
integrate encryption into the application.
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
34
PCI DSS 3.0 Requirement XYPRO Remarks
3.6.2 Secure cryptographic key distribution XDP, XKM, and XEL can be used to
integrate encryption into the application.
3.6.3 Secure cryptographic key storage XDP, XKM, and XEL can be used to
integrate encryption into the application.
3.6.4 Cryptographic key changes for keys that have reached the end of their crypto-period (for example, after a defined period of time has passed and/or after a certain amount of cipher-text has been produced by a given key), as defined by the associated application vendor or key owner, and based on industry best practices and guidelines (for example, NIST Special Publication 800-57).
This requirement can be met with
corporate policies, procedures, and
documentation.
3.6.5 Retirement or replacement (for example, archiving, destruction, and/or revocation) of keys as deemed necessary when the integrity of the key has been weakened (for example, departure of an employee with knowledge of a clear-text key component), or keys are suspected of being compromised. Note: If retired or replaced cryptographic keys need to be retained, these keys must be securely archived (for example, by using a key-encryption key). Archived cryptographic keys should only be used for decryption/verification purposes.
The required solution is not included in the
XYGATE product offering.
3.6.6 If manual clear-text cryptographic key-management operations are used, these operations must be managed using split knowledge and dual control. Note: Examples of manual key-management operations include, but are not limited to: key generation, transmission, loading, storage and destruction.
XDP, XKM, and XEL can be used to
integrate encryption into the application.
3.6.7 Prevention of unauthorized substitution of
cryptographic keys.
XDP, XKM, and XEL can be used to
integrate encryption into the application.
3.6.8 Requirement for cryptographic key custodians to
formally acknowledge that they understand and accept their key-custodian responsibilities.
XDP, XKM, and XEL can be used to
integrate encryption into the application.
3.7 Ensure that security policies and operational
procedures for protecting stored cardholder data are documented, in use, and known to all affected parties.
This requirement can be met with
corporate policies, procedures, and
documentation.
4: Encrypt transmission of cardholder data across
open, public networks
XHE, XSH and XFE can be used to
encrypt all varieties of data transmission.
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
35
PCI DSS 3.0 Requirement XYPRO Remarks
XDP, XKM, and XEL can be used to
integrate encryption into the application.
XSC can be used to provide the
encryption component for the PC.
4.1 Use strong cryptography and security protocols (for
example, SSL/TLS, IPSEC, SSH, etc.) to safeguard sensitive cardholder data during transmission over open, public networks, including the following:
he protocol in use only supports secure versions or
configurations.
methodology in use. Examples of open, public networks include but are not limited to: - The Internet - Wireless technologies, including 802.11 and Bluetooth - Cellular technologies, for example, Global System for Mobile communications (GSM), Code division multiple access (CDMA) - General Packet Radio Service (GPRS). - Satellite communications.
XHE, XSH and XFE can be used to
encrypt all varieties of data transmission.
XDP, XKM, and XEL can be used to
integrate encryption into the application.
XSC can be used to provide the
encryption component for the PC.
4.1.1 Ensure wireless networks transmitting cardholder data or connected to the cardholder data environment, use industry best practices (for example, IEEE 802.11i) to implement strong encryption for authentication and transmission.
Note: The use of WEP as a security control is prohibited.
This requirement involves network
configuration external to the NonStop
server.
4.2 Never send unprotected PANs by end-user messaging
technologies (for example, e-mail, instant messaging, chat, etc.).
This requirement can be met with
corporate policies, procedures, and
documentation.
4.3 Ensure that security policies and operational
procedures for encrypting transmissions of cardholder data are documented, in use, and known to all affected parties.
This requirement can be met with
corporate policies, procedures, and
documentation.
5: Protect all systems against malware and regularly
update anti-virus software or programs
Traditional consumer anti-virus is not
applicable to the HP NonStop server.
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
36
PCI DSS 3.0 Requirement XYPRO Remarks
5.1 Deploy anti-virus software on all systems commonly affected by malicious software (particularly personal computers and servers).
XSW can be used for file integrity
checking to provide object file validation
that is close to the same functionality as a
virus-check or registry-guard on the PC.
5.1.1 Ensure that anti-virus programs are capable of
detecting, removing, and protecting against all known types of malicious software.
XSW can be used for file integrity
checking to protect against Trojan Horses.
5.1.2 For systems considered to be not commonly affected by malicious software, perform periodic evaluations to identify and evaluate evolving malware threats in order to confirm whether such systems continue to not require anti-virus software.
XSW can be used for file integrity
checking.
5.2 Ensure that all anti-virus mechanisms are maintained
as follows: - Are kept current, - Perform periodic scans - Generate audit logs which are retained per PCI DSS Requirement 10.7.
XSW can be used for file integrity
checking.
5.3 Ensure that anti-virus mechanisms are actively running and cannot be disabled or altered by users, unless specifically authorized by management on a case-by-case basis for a limited time period. Note: Anti-virus solutions may be temporarily disabled only if there is legitimate technical need, as authorized by management on a case-by-case basis. If anti-virus protection needs to be disabled for a specific purpose, it must be formally authorized. Additional security measures may also need to be implemented for the period of time during which anti-virus protection is not active.
XSW can be used for file integrity
checking.
5.4 Ensure that security policies and operational procedures for protecting systems against malware are documented, in use, and known to all affected parties.
This requirement can be met with
corporate policies, procedures, and
documentation.
6: Develop and maintain secure systems and
applications
This requirement can be met with
corporate policies, procedures and
documentation.
6.1 Establish a process to identify security vulnerabilities, using reputable outside sources for security vulnerability information, and assign a risk ranking (for example, as “high,” “medium,” or “low”) to newly discovered security vulnerabilities. Note: Risk rankings should be based on industry best practices as well as consideration of potential impact. For
This requirement can be met with
corporate policies, procedures, and
documentation.
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
37
PCI DSS 3.0 Requirement XYPRO Remarks
example, criteria for ranking vulnerabilities may include consideration of the CVSS base score, and/or the classification by the vendor, and/or type of systems affected.
Methods for evaluating vulnerabilities and assigning risk
ratings will vary based on an organization’s environment
and risk-assessment strategy. Risk rankings should, at a
minimum, identify all vulnerabilities considered to be a “high
risk” to the environment. In addition to the risk ranking,
vulnerabilities may be considered “critical” if they pose an
imminent threat to the environment, impact critical systems,
and/or would result in a potential compromise if not
addressed. Examples of critical systems may include
security systems, public-facing devices and systems,
databases, and other systems that store, process, or
transmit cardholder data.
6.2 Ensure that all system components and software are
protected from known vulnerabilities by installing applicable vendor-supplied security patches. Install critical security patches within one month of release.
Note: Critical security patches should be identified
according to the risk ranking process defined in
Requirement 6.1.
This requirement can be met with
corporate policies, procedures, and
documentation.
6.3 Develop internal and external software applications (including web-based administrative access to applications) securely, as follows: - In accordance with PCI DSS (for example, secure authentication and logging) - Based on industry standards and/or best practices. - Incorporating information security throughout the software-development life cycle Note: this applies to all software developed internally as
well as bespoke or custom software developed by a third
party.
This requirement can be met with
corporate policies, procedures, and
documentation.
XDP, XKM, and XEL can be used to
integrate encryption into the application.
6.3.1 Remove development, test and/or custom application
accounts, user IDs, and passwords before applications become active or are released to customers.
This requirement can be met with
corporate policies, procedures, and
documentation.
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
38
PCI DSS 3.0 Requirement XYPRO Remarks
6.3.2 Review custom code prior to release to production or customers in order to identify any potential coding vulnerability (using either manual or automated processes) to include at least the following: - Code changes are reviewed by individuals other than the originating code author, and by individuals knowledgeable about code-review techniques and secure coding practices. - Code reviews ensure code is developed according to secure coding guidelines - Appropriate corrections are implemented prior to release. - Code-review results are reviewed and approved by management prior to release.
Note: This requirement for code reviews applies to all custom code (both internal and public-facing), as part of the system development life cycle.
Code reviews can be conducted by knowledgeable internal
personnel or third parties. Public-facing web applications
are also subject to additional controls, to address ongoing
threats and vulnerabilities after implementation, as defined
at PCI DSS Requirement 6.6.
XOS can be used to provide strong object
separation.
XCM can be used to control execution in
CPU resources.
6.4 Follow change control processes and procedures for all
changes to system components. The processes must include the following:
This requirement can be met with
corporate policies, procedures, and
documentation.
6.4.1 Separate development/test environments from
production environments, and enforce the separation with access controls.
This requirement can be met with
corporate policies, procedures, and
documentation.
XYGATE products can be used to enforce
separation of duties.
6.4.2 Separation of duties between development/test and production environments
This requirement can be met with
corporate policies, procedures, and
documentation.
XYGATE products can be used to enforce
separation of duties.
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
39
PCI DSS 3.0 Requirement XYPRO Remarks
6.4.3 Production data (live PANs) are not used for testing or development
This requirement can be met with
corporate policies, procedures, and
documentation.
6.4.4 Removal of test data and accounts before production
systems become active This requirement can be met with
corporate policies, procedures, and
documentation.
6.4.5 Change control procedures for the implementation of
security patches and software modifications must include the following:
This requirement can be met with
corporate policies, procedures, and
documentation.
6.4.5.1 Documentation of impact. This requirement can be met with
corporate policies, procedures, and
documentation.
6.4.5.2 Documented change approval by authorized
parties. This requirement can be met with
corporate policies, procedures, and
documentation.
6.4.5.3 Functionality testing to verify that the change does not adversely impact the security of the system.
This requirement can be met with
corporate policies, procedures, and
documentation.
6.4.5.4 Back-out procedures. This requirement can be met with
corporate policies, procedures, and
documentation.
6.5 Address common coding vulnerabilities in software-development processes as follows: - Train developers in secure coding techniques, including how to avoid common coding vulnerabilities, and understanding how sensitive data is handled in memory. - Develop applications based on secure coding guidelines. Note: The vulnerabilities listed at 6.5.1 through 6.5.10 were
current with industry best practices when this version of
PCI DSS was published. However, as industry best
practices for vulnerability management are updated (for
example, the OWASP Guide, SANS CWE Top 25, CERT
Secure Coding, etc.), the current best practices must be
used for these requirements.
This requirement can be met with
corporate policies, procedures, and
documentation.
6.5.1 Injection flaws, particularly SQL injection. Also
consider OS Command Injection, LDAP and XPath injection flaws as well as other injection flaws.
This requirement can be met with
corporate policies, procedures, and
documentation.
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
40
PCI DSS 3.0 Requirement XYPRO Remarks
6.5.2 Buffer overflows This requirement can be met with
corporate policies, procedures, and
documentation.
6.5.3 Insecure cryptographic storage This requirement can be met with
corporate policies, procedures, and
documentation.
6.5.4 Insecure communications This requirement can be met with
corporate policies, procedures, and
documentation.
6.5.5 Improper error handling This requirement can be met with
corporate policies, procedures, and
documentation.
6.5.6 All “high risk” vulnerabilities identified in the
vulnerability identification process (as defined in PCI DSS Requirement 6.1).
This requirement can be met with
corporate policies, procedures, and
documentation.
Note: Requirements 6.5.7 through 6.5.10, below, apply to web applications and application interfaces (internal or external):
6.5.7 Cross-site scripting (XSS) This requirement can be met with
corporate policies, procedures, and
documentation.
6.5.8 Improper access control (such as insecure direct
object references, failure to restrict URL access, directory traversal, and failure to restrict user access to functions).
This requirement can be met with
corporate policies, procedures, and
documentation.
6.5.9 Cross-site request forgery (CSRF) This requirement can be met with
corporate policies, procedures, and
documentation.
6.5.10 Broken authentication and session management
Note: Requirement 6.5.10 is a best practice until June 30,
2015, after
This requirement can be met with
corporate policies, procedures, and
documentation.
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
41
PCI DSS 3.0 Requirement XYPRO Remarks
6.6 For public-facing web applications, address new threats and vulnerabilities on an ongoing basis and ensure these applications are protected against known attacks by either of the following methods: - Reviewing public-facing web applications via manual or automated application vulnerability security assessment tools or methods, at least annually and after any changes Note: This assessment is not the same as the vulnerability scans performed for Requirement 11.2. - Installing an automated technical solution that detects and prevents web-based attacks (for example, a web-application firewall) in front of public-facing web applications, to continually check all traffic.
The required solution is not included in the
XYGATE product offering.
6.7 Ensure that security policies and operational procedures for developing and maintaining secure systems and applications are documented, in use, and known to all affected parties.
This requirement can be met with
corporate policies, procedures, and
documentation.
7: Restrict access to cardholder data by business need
to know
All XYGATE modules.
7.1 Limit access to system components and cardholder
data to only those individuals whose job requires such access.
XAC and XOS can be used to provide
action control and object control to
authorized individuals only.
7.1.1 Define access needs for each role, including:
- System components and data resources that each role needs to access for their job function - Level of privilege required (for example, user, administrator, etc.) for accessing resources.
XAC and XOS can be used to provide
action control and object control to
authorized individuals only.
7.1.2 Restrict access to privileged user IDs to least
privileges necessary to perform job responsibilities.
XAC and XOS can be used to provide
action control and object control to
authorized individuals only.
7.1.3 Assign access based on individual personnel’s job
classification and function.
XAC and XOS can be used to provide
action control and object control to
authorized individuals only.
7.1.4 Require documented approval by authorized parties specifying required privileges.
This requirement can be met with
corporate policies, procedures, and
documentation.
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
42
PCI DSS 3.0 Requirement XYPRO Remarks
7.2 Establish an access control system for systems components that restricts access based on a user’s need to know, and is set to “deny all” unless specifically allowed.
This access control system must include the following:
XAC, XCM, and XOS can be used.
7.2.1 Coverage of all system components XAC, XCM, and XOS can be used.
7.2.2 Assignment of privileges to individuals based on job
classification and function.
XAC, XCM, and XOS can be used.
7.2.3 Default “deny-all” setting. XAC, XCM, and XOS can be used.
7.3 Ensure that security policies and operational procedures for restricting access to cardholder data are documented, in use, and known to all affected parties.
This requirement can be met with
corporate policies, procedures, and
documentation.
8: Identify and authenticate access to system
components
XAC can be used to support the functional
use of unique userids.
XSM can be used to create userids.
8.1 Define and implement policies and procedures to ensure proper user identification management for non-consumer users and administrators on all system components as follows:
This requirement can be met with
corporate policies, procedures, and
documentation.
8.1.1 Assign all users a unique ID before allowing them to
access system components or cardholder data.
XUA, XCM, and XSM can be used.
8.1.2 Control addition, deletion, and modification of user IDs, credentials, and other identifier objects.
All XYGATE modules.
8.1.3 Immediately revoke access for any terminated users. All XYGATE modules.
8.1.4 Remove/disable inactive user accounts at least every 90 days.
XSW can be used to regularly identify
inactive user accounts.
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
43
PCI DSS 3.0 Requirement XYPRO Remarks
XSM can be used to remove/disable
inactive user accounts.
8.1.5 Manage IDs used by vendors to access, support, or
maintain system components via remote access as follows: - Enabled only during the time period needed and disabled when not in use. - Monitored when in use.
XSM, XAC, XCM, and XUA can be used.
8.1.6 Limit repeated access attempts by locking out the
user ID after not more than six attempts. This requirement can be met with
corporate policies, procedures, and
documentation.
8.1.7 Set the lockout duration to a minimum of 30 minutes
or until an administrator enables the user ID.
XUA can be used.
8.1.8 If a session has been idle for more than 15 minutes, require the user to re-authenticate to re-activate the terminal or session.
XAC can be used.
8.2 In addition to assigning a unique ID, ensure proper
user-authentication management for non-consumer users and administrators on all system components by employing at least one of the following methods to authenticate all users: - Something you know, such as a password or passphrase - Something you have, such as a token device or smart card - Something you are, such as a biometric.
XUA and/or XPQ can be used.
8.2.1 Using strong cryptography, render all authentication credentials (such as passwords/phrases) unreadable during transmission and storage on all system components.
XPQ can be used.
8.2.2 Verify user identity before modifying any authentication credential—for example, performing password resets, provisioning new tokens, or generating new keys.
XUA can be used.
8.2.3 Passwords/phrases must meet the following: - Require a minimum length of at least seven characters. - Contain both numeric and alphabetic characters. Alternatively, the passwords/phrases must have complexity
and strength at least equivalent to the parameters specified
above.
XPQ can be used.
8.2.4 Change user passwords/passphrases at least every 90 days.
XUA can be used.
8.2.5 Do not allow an individual to submit a new
password/phrase that is the same as any of the last four passwords/phrases he or she has used.
XUA can be used.
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
44
PCI DSS 3.0 Requirement XYPRO Remarks
8.2.6 Set passwords/phrases for first-time use and upon reset to a unique value for each user, and change immediately after the first use.
XUA and XPQ can be used.
8.3 Incorporate two-factor authentication for remote network access originating from outside the network by personnel (including users and administrators) and all third parties, (including vendor access for support or maintenance). Note: Two-factor authentication requires that two of the three authentication methods (see Requirement 8.2 for descriptions of authentication methods) be used for authentication. Using one factor twice (for example, using two separate passwords) is not considered two-factor authentication. Examples of two-factor technologies include remote authentication and dial-in service (RADIUS) with tokens; terminal access controller access control system (TACACS) with tokens; and other technologies that facilitate two-factor authentication.
XUA can be used.
8.4 Document and communicate authentication procedures
and policies to all users including: - Guidance on selecting strong authentication credentials - Guidance for how users should protect their authentication credentials - Instructions not to reuse previously used passwords - Instructions to change passwords if there is any suspicion the password could be compromised.
This requirement can be met with
corporate policies, procedures, and
documentation.
8.5 Do not use group, shared, or generic IDs, passwords,
or other authentication methods as follows: - Generic user IDs are disabled or removed. - Shared user IDs do not exist for system administration and other critical functions. - Shared and generic user IDs are not used to administer any system components.
This requirement can be met with
corporate policies, procedures, and
documentation.
8.5.1 Additional requirement for service providers: Service providers with remote access to customer premises (for example, for support of POS systems or servers) must use a unique authentication credential (such as a password/phrase) for each customer. Note: This requirement is not intended to apply to shared hosting providers accessing their own hosting environment, where multiple customer environments are hosted. Note: Requirement 8.5.1 is a best practice until June 30, 2015, after which it becomes a requirement.
This requirement can be met with
corporate policies, procedures, and
documentation.
8.6 Where other authentication mechanisms are used (for
example, physical or logical security tokens, smart cards, certificates, etc.), use of these mechanisms must be assigned as follows:
This requirement can be met with
corporate policies, procedures, and
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
45
PCI DSS 3.0 Requirement XYPRO Remarks
- Authentication mechanisms must be assigned to an individual account and not shared among multiple accounts. - Physical and/or logical controls must be in place to ensure only the intended account can use that mechanism to gain access.
documentation.
8.7 All access to any database containing cardholder data (including access by applications, administrators, and all other users) is restricted as follows: - All user access to, user queries of, and user actions on databases are through programmatic methods. - Only database administrators have the ability to directly access or query databases. - Application IDs for database applications can only be used by the applications (and not by individual users or other non-application processes).
XAC and XOS can be used to provide
action control and object control to
authorized individuals only.
XDP, XKM, and XEL can be used to
integrate encryption into the application.
8.8 Ensure that security policies and operational
procedures for identification and authentication are documented, in use, and known to all affected parties.
This requirement can be met with
corporate policies, procedures, and
documentation.
9: Restrict physical access to cardholder data This is not applicable to HP NonStop
server.
9.1 Use appropriate facility entry controls to limit and
monitor physical access to systems in the cardholder data environment.
This requirement can be met with
corporate policies, procedures, and
documentation.
9.1.1 Use video cameras and/or access control mechanisms to monitor individual physical access to sensitive areas. Review collected data and correlate with other entries. Store for at least three months, unless otherwise restricted by law.
Note: “Sensitive areas” refers to any data center, server
room or any area that houses systems that store, process,
or transmit cardholder data. This excludes public-facing
areas where only point-of-sale terminals are present, such
as the cashier areas in a retail store.
This requirement can be met with
corporate policies, procedures, and
documentation.
9.1.2 Implement physical and/or logical controls to restrict access to publicly accessible network jacks. For example, network jacks located in public areas and areas accessible to visitors could be disabled and only enabled when network access is explicitly authorized.
This requirement can be met with
corporate policies, procedures, and
documentation.
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
46
PCI DSS 3.0 Requirement XYPRO Remarks
Alternatively, processes could be implemented to ensure that visitors are escorted at all times in areas with active network jacks.
9.1.3 Restrict physical access to wireless access points, gateways, handheld devices, networking/communications hardware, and telecommunication lines.
This requirement can be met with
corporate policies, procedures, and
documentation.
9.2 Develop procedures to easily distinguish between onsite personnel and visitors, to include: - Identifying new onsite personnel or visitors (for example, assigning badges) - Changes to access requirements - Revoking or terminating onsite personnel and expired visitor identification (such as ID badges).
This requirement can be met with
corporate policies, procedures, and
documentation.
9.3 Control physical access for onsite personnel to the sensitive
areas as follows: - Access must be authorized and based on individual job function. - Access is revoked immediately upon termination, and all physical access mechanisms, such as keys, access cards, etc., are returned or disabled.
This requirement can be met with
corporate policies, procedures, and
documentation.
9.4 Implement procedures to identify and authorize visitors.
Procedures should include the following: This requirement can be met with
corporate policies, procedures, and
documentation.
9.4.1 Visitors are authorized before entering, and escorted at all times within, areas where cardholder data is processed or maintained.
This requirement can be met with
corporate policies, procedures, and
documentation.
9.4.2 Visitors are identified and given a badge or other identification that expires and that visibly distinguishes the visitors from onsite personnel.
This requirement can be met with
corporate policies, procedures, and
documentation.
9.4.3 Visitors are asked to surrender the badge or
identification before leaving the facility or at the date of expiration.
This requirement can be met with
corporate policies, procedures, and
documentation.
9.4.4 A visitor log is used to maintain a physical audit trail
of visitor activity to the facility as well as computer rooms and data centers where cardholder data is stored or transmitted. Document the visitor’s name, the firm represented, and the onsite personnel authorizing physical access on the log. Retain this log for a minimum of three months, unless otherwise restricted by law.
This requirement can be met with
corporate policies, procedures, and
documentation.
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
47
PCI DSS 3.0 Requirement XYPRO Remarks
9.5 Physically secure all media. This requirement can be met with
corporate policies, procedures, and
documentation.
9.5.1 Store media backups in a secure location, preferably
an off-site facility, such as an alternate or backup site, or a commercial storage facility. Review the location’s security at least annually.
This requirement can be met with
corporate policies, procedures, and
documentation.
9.6 Maintain strict control over the internal or external
distribution of any kind of media, including the following: This requirement can be met with
corporate policies, procedures, and
documentation.
9.6.1 Classify media so the sensitivity of the data can be
determined. This requirement can be met with
corporate policies, procedures, and
documentation.
9.6.2 Send the media by secured courier or other delivery method that can be accurately tracked.
This requirement can be met with
corporate policies, procedures, and
documentation.
9.6.3 Ensure management approves any and all media that is moved from a secured area (including when media is distributed to individuals).
This requirement can be met with
corporate policies, procedures, and
documentation.
9.7 Maintain strict control over the storage and accessibility of media.
This requirement can be met with
corporate policies, procedures, and
documentation.
9.7.1 Properly maintain inventory logs of all media and conduct media inventories at least annually.
This requirement can be met with
corporate policies, procedures, and
documentation.
9.8 Destroy media when it is no longer needed for business
or legal reasons as follows: This requirement can be met with
corporate policies, procedures, and
documentation.
9.8.1 Shred, incinerate, or pulp hard-copy materials so that
cardholder data cannot be reconstructed. Secure storage containers used for materials that are to be destroyed.
This requirement can be met with
corporate policies, procedures, and
documentation.
9.8.2 Render cardholder data on electronic media
unrecoverable so that cardholder data cannot be reconstructed.
This requirement can be met with
corporate policies, procedures, and
documentation.
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
48
PCI DSS 3.0 Requirement XYPRO Remarks
9.9 Protect devices that capture payment card data via direct physical interaction with the card from tampering and substitution. Note: These requirements apply to card-reading devices used in card-present transactions (that is, card swipe or dip) at the point of sale. This requirement is not intended to apply to manual key-entry components such as computer keyboards and POS keypads. Note: Requirement 9.9 is a best practice until June 30, 2015, after which it becomes a requirement.
This requirement can be met with
corporate policies, procedures, and
documentation.
9.9.1 Maintain an up-to-date list of devices. The list should include
the following: - Make, model of device - Location of device (for example, the address of the site or facility where the device is located) - Device serial number or other method of unique identification.
This requirement can be met with
corporate policies, procedures, and
documentation.
9.9.2 Periodically inspect device surfaces to detect tampering (for example, addition of card skimmers to devices), or substitution (for example, by checking the serial number or other device characteristics to verify it has not been swapped with a fraudulent device). Note: Examples of signs that a device might have been tampered with or substituted include unexpected attachments or cables plugged into the device, missing or changed security labels, broken or differently colored casing, or changes to the serial number or other external markings.
This requirement can be met with
corporate policies, procedures, and
documentation.
9.9.3 Provide training for personnel to be aware of attempted tampering or replacement of devices. Training should include the following: - Verify the identity of any third-party persons claiming to be repair or maintenance personnel, prior to granting them access to modify or troubleshoot devices. - Do not install, replace, or return devices without verification. - Be aware of suspicious behavior around devices (for example, attempts by unknown persons to unplug or open devices). - Report suspicious behavior and indications of device tampering or substitution to appropriate personnel (for example, to a manager or security officer).
This requirement can be met with
corporate policies, procedures, and
documentation.
9.10 Ensure that security policies and operational procedures for restricting physical access to cardholder data are documented, in use, and known to all affected parties.
This requirement can be met with
corporate policies, procedures, and
documentation.
10: Track and monitor all access to network resources
and cardholder data
All XYGATE modules.
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
49
PCI DSS 3.0 Requirement XYPRO Remarks
10.1 Implement audit trails to link all access to system components to each individual user.
All XYGATE modules.
10.2 Implement automated audit trails for all system components to reconstruct the following events:
All XYGATE modules.
10.2.1 All individual user accesses to cardholder data All XYGATE modules.
10.2.2 All actions taken by any individual with root or
administrative privileges All XYGATE modules.
10.2.3 Access to all audit trails All XYGATE modules.
10.2.4 Invalid logical access attempts All XYGATE modules.
10.2 5 Use of and changes to identification and
authentication mechanisms—including but not limited to creation of new accounts and elevation of privileges—and all changes, additions, or deletions to accounts with root or administrative privileges
All XYGATE modules.
10.2.6 Initialization, stopping, or pausing of the audit logs All XYGATE modules.
10.2.7 Creation and deletion of system-level objects All XYGATE modules.
10.3 Record at least the following audit trail entries for all
system components for each event: All XYGATE modules.
10.3.1 User identification All XYGATE modules.
10.3.2 Type of event All XYGATE modules.
10.3.3 Date and time All XYGATE modules.
10.3.4 Success or failure indication All XYGATE modules.
10.3.5 Origination of event All XYGATE modules.
10.3.6 Identity or name of affected data, system
component, or resource. All XYGATE modules.
10.4 Using time-synchronization technology, synchronize
all critical system clocks and times and ensure that the following is implemented for acquiring, distributing, and storing time.
Note: One example of time synchronization technology is
Network Time Protocol (NTP).
The required solution is not included in the
XYGATE product offering.
10.4.1 Critical systems have the correct and consistent time.
XOS, XRM, XMA, and XEM can be used.
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
50
PCI DSS 3.0 Requirement XYPRO Remarks
10.4.2 Time data is protected. XOS, XRM, XMA, and XEM can be used.
10.4.3 Time settings are received from industry-accepted
time sources.
XOS, XRM, XMA, and XEM can be used.
10.5 Secure audit trails so they cannot be altered. XOS can be used.
10.5.1 Limit viewing of audit trails to those with a job-
related need.
XOS, XRM, XMA, and XEM can be used.
10.5.2 Protect audit trail files from unauthorized modifications.
XOS can be used.
10.5.3 Promptly back up audit trail files to a centralized log server or media that is difficult to alter.
XMA can be used.
10.5.4 Write logs for external-facing technologies onto a
secure, centralized, internal log server or media device. This requirement involves network
configuration external to the NonStop
server.
10.5.5 Use file-integrity monitoring or change-detection
software on logs to ensure that existing log data cannot be changed without generating alerts (although new data being added should not cause an alert).
XOS and XMA can be used.
10.6 Review logs and security events for all system
components to identify anomalies or suspicious activity.
Note: Log harvesting, parsing, and alerting tools may be
used to meet this Requirement.
XRM, XMA, and XEM can be used.
10.6.1 Review the following at least daily: - All security events - Logs of all system components that store, process, or transmit CHD and/or SAD, or that could impact the security of CHD and/or SAD - Logs of all critical system components - Logs of all servers and system components that perform security functions (for example, firewalls, intrusion-detection systems/intrusion-prevention systems (IDS/IPS), authentication servers, e-commerce redirection servers, etc.).
XMA can be used.
10.6.2 Review logs of all other system components
periodically based on the organization’s policies and risk management strategy, as determined by the organization’s annual risk assessment.
This requirement can be met with
corporate policies, procedures, and
documentation.
10.6.3 Follow up exceptions and anomalies identified
during the review process. This requirement can be met with
corporate policies, procedures, and
documentation.
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
51
PCI DSS 3.0 Requirement XYPRO Remarks
10.7 Retain audit trail history for at least one year, with a minimum of three months immediately available for analysis (for example, online, archived, or restorable from backup).
This requirement can be met with
corporate policies, procedures, and
documentation.
10.8 Ensure that security policies and operational
procedures for monitoring all access to network resources and cardholder data are documented, in use, and known to all affected parties.
This requirement can be met with
corporate policies, procedures, and
documentation.
11: Regularly test security systems and processes XSW and XMA can be used.
11.1 Implement processes to test for the presence of
wireless access points (802.11), and detect and identify all authorized and unauthorized wireless access points on a quarterly basis. Note: Methods that may be used in the process include but are not limited to wireless network scans, physical/logical inspections of system components and infrastructure, network access control (NAC), or wireless IDS/IPS.
Whichever methods are used, they must be sufficient to
detect and identify both authorized and unauthorized
devices.
This requirement can be met with
corporate policies, procedures, and
documentation.
11.1.1 Maintain an inventory of authorized wireless access
points including a documented business justification. This requirement can be met with
corporate policies, procedures, and
documentation.
11.1.2 Implement incident response procedures in the
event unauthorized wireless access points are detected. This requirement can be met with
corporate policies, procedures, and
documentation.
11.2 Run internal and external network vulnerability scans at least quarterly and after any significant change in the network (such as new system component installations, changes in network topology, firewall rule modifications, product upgrades). Note: Multiple scan reports can be combined for the quarterly scan process to show that all systems were scanned and all applicable vulnerabilities have been addressed. Additional documentation may be required to verify non-remediated vulnerabilities are in the process of being addressed.
The required solution is not included in the
XYGATE product offering.
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
52
PCI DSS 3.0 Requirement XYPRO Remarks
For initial PCI DSS compliance, it is not required that four
quarters of passing scans be completed if the assessor
verifies 1) the most recent scan result was a passing scan,
2) the entity has documented policies and procedures
requiring quarterly scanning, and 3) vulnerabilities noted in
the scan results have been corrected as shown in a re-
scan(s). For subsequent years after the initial PCI DSS
review, four quarters of passing scans must have occurred.
11.2.1 Perform quarterly internal vulnerability scans and rescans as needed, until all “high-risk” vulnerabilities (as identified in Requirement 6.1) are resolved. Scans must be performed by qualified personnel.
The required solution is not included in the
XYGATE product offering.
11.2.2 Perform quarterly external vulnerability scans, via an Approved Scanning Vendor (ASV) approved by the Payment Card Industry Security Standards Council (PCI SSC). Perform rescans as needed, until passing scans are achieved. Note: Quarterly external vulnerability scans must be performed by an Approved Scanning Vendor (ASV), approved by the Payment Card Industry Security Standards Council (PCI SSC).
Refer to the ASV Program Guide published on the PCI
SSC website for scan customer responsibilities, scan
preparation, etc.
The required solution is not included in the
XYGATE product offering.
11.2.3 Perform internal and external scans, and rescans as needed, after any significant change. Scans must be performed by qualified personnel.
The required solution is not included in the
XYGATE product offering.
11.3 Implement a methodology for penetration testing that
includes the following: - Is based on industry-accepted penetration testing approaches (for example, NIST SP800-115) - Includes coverage for the entire CDE perimeter and critical systems - Includes testing from both inside and outside the network - Includes testing to validate any segmentation and scope-reduction controls - Defines application-layer penetration tests to include, at a minimum, the vulnerabilities listed in Requirement 6.5 - Defines network-layer penetration tests to include
The required solution is not included in the
XYGATE product offering.
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
53
PCI DSS 3.0 Requirement XYPRO Remarks
components that support network functions as well as operating systems - Includes review and consideration of threats and vulnerabilities experienced in the last 12 months - Specifies retention of penetration testing results and remediation activities results. Note: This update to Requirement 11.3 is a best practice
until June 30, 2015, after which it becomes a requirement.
PCI DSS v2.0 requirements for penetration testing must be
followed until v3.0 is in place.
11.3.1 Perform external penetration testing at least annually and after any significant infrastructure or application upgrade or modification (such as an operating system upgrade, a sub-network added to the environment, or a web server added to the environment).
The required solution is not included in the
XYGATE product offering.
11.3.2 Perform internal penetration testing at least annually and after any significant infrastructure or application upgrade or modification (such as an operating system upgrade, a sub-network added to the environment, or a web server added to the environment).
XMA can be used to report and alert on
system activity.
11.3.3 Exploitable vulnerabilities found during penetration
testing are corrected and testing is repeated to verify the corrections.
XSW can be used for file integrity
checking.
11.3.4 If segmentation is used to isolate the CDE from
other networks, perform penetration tests at least annually and after any changes to segmentation controls/methods to verify that the segmentation methods are operational and effective, and isolate all out-of-scope systems from in-scope systems.
The required solution is not included in the
XYGATE product offering.
11.4 Use intrusion-detection and/or intrusion-prevention techniques to detect and/or prevent intrusions into the network. Monitor all traffic at the perimeter of the cardholder data environment as well as at critical points in the cardholder data environment, and alert personnel to suspected compromises. Keep all intrusion-detection and prevention engines, baselines, and signatures up to date.
XMA can be used to report and alert on
system activity.
11.5 Deploy a change-detection mechanism (for example,
file-integrity monitoring tools) to alert personnel to unauthorized modification of critical system files, configuration files, or content files; and configure the software to perform critical file comparisons at least weekly. Note: For change-detection purposes, critical files are usually those that do not regularly change, but the
XSW can be used for file integrity
checking.
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
54
PCI DSS 3.0 Requirement XYPRO Remarks
modification of which could indicate a system compromise or risk of compromise. Change-detection mechanisms such as file-integrity monitoring products usually come pre-configured with critical files for the related operating system. Other critical files, such as those for custom applications, must be evaluated and defined by the entity (that is, the merchant or service provider). 11.5.1 Implement a process to respond to any alerts
generated by the change-detection solution. This requirement can be met with
corporate policies, procedures, and
documentation.
11.6 Ensure that security policies and operational
procedures for security monitoring and testing are documented, in use, and known to all affected parties.
This requirement can be met with
corporate policies, procedures, and
documentation.
12: Maintain a policy that addresses information
security for all personnel
XSW can be used for file integrity
checking.
12.1 Establish, publish, maintain, and disseminate a
security policy. This requirement can be met with
corporate policies, procedures, and
documentation.
12.1.1 Review the security policy at least annually and
update the policy when the environment changes. This requirement can be met with
corporate policies, procedures, and
documentation.
12.2 Implement a risk-assessment process that:
- Is performed at least annually and upon significant changes to the environment (for example, acquisition, merger, relocation, etc.), - Identifies critical assets, threats, and vulnerabilities, and - Results in a formal risk assessment. Examples of risk-assessment methodologies include but
are not limited to OCTAVE, ISO 27005 and NIST SP 800-
30.
This requirement can be met with
corporate policies, procedures, and
documentation.
12.3 Develop usage policies for critical technologies and
define proper use of these technologies. Note: Examples of critical technologies include, but are not limited to, remote access and wireless technologies, laptops, tablets, removable electronic media, e-mail usage and Internet usage.
This requirement can be met with
corporate policies, procedures, and
documentation.
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
55
PCI DSS 3.0 Requirement XYPRO Remarks
Ensure these usage policies require the following:
12.3.1 Explicit approval by authorized parties This requirement can be met with
corporate policies, procedures, and
documentation.
12.3.2 Authentication for use of the technology This requirement can be met with
corporate policies, procedures, and
documentation.
12.3.3 A list of all such devices and personnel with access XSW can be used to provide user access
maps.
12.3.4 A method to accurately and readily determine
owner, contact information, and purpose (for example, labeling, coding, and/or inventorying of devices)
This requirement can be met with
corporate policies, procedures, and
documentation.
12.3.5 Acceptable uses of the technology This requirement can be met with
corporate policies, procedures, and
documentation.
12.3.6 Acceptable network locations for the technologies This requirement can be met with
corporate policies, procedures, and
documentation.
12.3.7 List of company-approved products This requirement can be met with
corporate policies, procedures, and
documentation.
12.3.8 Automatic disconnect of sessions for remote-access technologies after a specific period of inactivity
XAC can be used for disconnecting
remote access technologies sessions.
12.3.9 Activation of remote-access technologies for vendors and business partners only when needed by vendors and business partners, with immediate deactivation after use
XAC can be used for remote access
technology disconnects.
XCM, XHE, and XUA can be used for port
protection in general
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
56
PCI DSS 3.0 Requirement XYPRO Remarks
12.3.10 For personnel accessing cardholder data via remote-access technologies, prohibit the copying, moving, and storage of cardholder data onto local hard drives and removable electronic media, unless explicitly authorized for a defined business need.
Where there is an authorized business need, the usage
policies must require the data be protected in accordance
with all applicable PCI DSS Requirements.
This requirement can be met with
corporate policies, procedures, and
documentation.
12.4 Ensure that the security policy and procedures clearly define information security responsibilities for all personnel.
This requirement can be met with
corporate policies, procedures, and
documentation.
12.5 Assign to an individual or team the following information security management responsibilities:
This requirement can be met with
corporate policies, procedures, and
documentation.
12.5.1 Establish, document, and distribute security policies and procedures.
This requirement can be met with
corporate policies, procedures, and
documentation.
12.5.2 Monitor and analyze security alerts and information,
and distribute to appropriate personnel.
XSW and XMA can be used to facilitate
monitoring and alerting.
12.5.3 Establish, document, and distribute security incident
response and escalation procedures to ensure timely and effective handling of all situations.
This requirement can be met with
corporate policies, procedures, and
documentation.
12.5.4 Administer user accounts, including additions,
deletions, and modifications.
XSM can be used to administer userids.
XPQ and XPR can be used to facilitate
strong passwords and password resets.
12.5.5 Monitor and control all access to data. XSW and XMA can be used for
monitoring.
XOS can be used for controlling access.
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
57
PCI DSS 3.0 Requirement XYPRO Remarks
12.6 Implement a formal security awareness program to make all personnel aware of the importance of cardholder data security.
This requirement can be met with
corporate policies, procedures, and
documentation.
12.6.1 Educate personnel upon hire and at least annually.
Note: Methods can vary depending on the role of the
personnel and their level of access to the cardholder data.
This requirement can be met with
corporate policies, procedures, and
documentation.
12.6.2 Require personnel to acknowledge at least annually that they have read and understood the security policy and procedures.
This requirement can be met with
corporate policies, procedures, and
documentation.
12.7 Screen potential personnel prior to hire to minimize the risk of attacks from internal sources. (Examples of background checks include previous employment history, criminal record, credit history, and reference checks.)
Note: For those potential personnel to be hired for certain
positions such as store cashiers who only have access to
one card number at a time when facilitating a transaction,
this requirement is a recommendation only.
This requirement can be met with
corporate policies, procedures, and
documentation.
12.8 Maintain and implement policies and procedures to
manage service providers with whom cardholder data is shared, or that could affect the security of cardholder data, as follows:
This requirement can be met with
corporate policies, procedures, and
documentation.
12.8.1 Maintain a list of service providers. This requirement can be met with
corporate policies, procedures, and
documentation.
12.8.2 Maintain a written agreement that includes an acknowledgement that the service providers are responsible for the security of cardholder data the service providers possess or otherwise store, process or transmit on behalf of the customer, or to the extent that they could impact the security of the customer’s cardholder data environment.
Note: The exact wording of an acknowledgement will
depend on the agreement between the two parties, the
details of the service being provided, and the
responsibilities assigned to each party. The
acknowledgement does not have to include the exact
This requirement can be met with
corporate policies, procedures, and
documentation.
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
58
PCI DSS 3.0 Requirement XYPRO Remarks
wording provided in this requirement.
12.8.3 Ensure there is an established process for engaging service providers including proper due diligence prior to engagement.
This requirement can be met with
corporate policies, procedures, and
documentation.
12.8.4 Maintain a program to monitor service providers’ PCI DSS compliance status at least annually.
This requirement can be met with
corporate policies, procedures, and
documentation.
12.8.5 Maintain information about which PCI DSS requirements are managed by each service provider, and which are managed by the entity.
This requirement can be met with
corporate policies, procedures, and
documentation.
12.9 Additional requirement for service providers:
Service providers acknowledge in writing to customers that they are responsible for the security of cardholder data the service provider possesses or otherwise stores, processes, or transmits on behalf of the customer, or to the extent that they could impact the security of the customer’s cardholder data environment. Note: This requirement is a best practice until June 30, 2015, after which it becomes a requirement.
Note: The exact wording of an acknowledgement will
depend on the agreement between the two parties, the
details of the service being provided, and the
responsibilities assigned to each party. The
acknowledgement does not have to include the exact
wording provided in this requirement.
This requirement can be met with
corporate policies, procedures, and
documentation.
12.10 Implement an incident response plan. Be prepared to respond immediately to a system breach.
This requirement can be met with
corporate policies, procedures, and
documentation.
12.10.1 Create the incident response plan to be implemented in the event of system breach. Ensure the plan addresses the following, at a minimum: - Roles, responsibilities, and communication and contact strategies in the event of a compromise including notification of the payment brands, at a minimum - Specific incident response procedures - Business recovery and continuity procedures - Data backup processes - Analysis of legal requirements for reporting compromises
This requirement can be met with
corporate policies, procedures, and
documentation.
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
59
PCI DSS 3.0 Requirement XYPRO Remarks
- Coverage and responses of all critical system components - Reference or inclusion of incident response procedures from the payment brands.
12.10.2 Test the plan at least annually. This requirement can be met with
corporate policies, procedures, and
documentation.
12.10.3 Designate specific personnel to be available on a 24/7 basis to respond to alerts.
This requirement can be met with
corporate policies, procedures, and
documentation.
12.10.4 Provide appropriate training to staff with security breach response responsibilities.
This requirement can be met with
corporate policies, procedures, and
documentation.
12.10.5 Include alerts from security monitoring systems,
including but not limited to intrusion-detection, intrusion-prevention, firewalls, and file-integrity monitoring systems.
XMA and XEM can be used.
12.10.6 Develop a process to modify and evolve the incident response plan according to lessons learned and to incorporate industry developments.
This requirement can be met with
corporate policies, procedures, and
documentation.
A.1: Shared hosting providers must protect the cardholder data environment
All XYGATE products.
A.1 Protect each entity’s (that is, merchant, service
provider, or other entity) hosted environment and data, per A.1.1 through A.1.4: A hosting provider must fulfill these requirements as well as all other relevant sections of the PCI DSS. Note: Even though a hosting provider may meet these requirements, the compliance of the entity that uses the hosting provider is not guaranteed. Each entity must comply with the PCI DSS and validate compliance as applicable.
All XYGATE products.
A.1.1 Ensure that each entity only runs processes that
have access to that entity’s cardholder data environment.
XAC can be used.
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
60
PCI DSS 3.0 Requirement XYPRO Remarks
A.1.2 Restrict each entity’s access and privileges to its own cardholder data environment only.
XOS can be used.
A.1.3 Ensure logging and audit trails are enabled and
unique to each entity’s cardholder data environment and consistent with PCI DSS Requirement 10.
This requirement can be met with
corporate policies, procedures, and
documentation.
A.1.4 Enable processes to provide for timely forensic
investigation in the event of a compromise to any hosted merchant or service provider.
This requirement can be met with
corporate policies, procedures, and
documentation.
XYPRO Technology Corporation PCI Compliance and the HP NonStop™ Server Enterprise
Get Connected March 2015 Version 3.0
61
THE LEADER IN NONSTOP SECURITY
XYPRO Technology offers over three decades of knowledge, experience and success in providing HP
NonStop™ information systems solutions and services. These solutions meet the strict requirements of
companies who manage, access and transport sensitive data using heterogeneous hardware platforms and
multiple communications media. By delivering products and services that improve the HP NonStop™
server environment, XYPRO ultimately helps professionals enhance their daily jobs while helping
businesses gain optimum efficiency. Collectively, this has made XYPRO the undeniable leader in HP
NonStop™ server security and encryption solutions.
XYPRO
4100 Guardian St. Suite 100
Simi Valley, Ca. 93063
www.xypro.com
USA & Canada Sales & Support
+1 805 583 2874
XYPRO Technology Pty Ltd.
Asia Pacific Sales & Support:
+61 3 9008 4283
EMEA:
+44 (0) 7967 662294
Ibero América:
+52 55 5651 9052 / +52 1 449 128
7202
Japan:
0066 33 821682
www.xypro.com