White Paper - PCI Compliance

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
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.
2
Get Connected
March 2015 Version 3.0
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
PROTECT CARDHOLDER DATA ........................................................................................................... 14
Requirement 3: Protect stored cardholder data (data at rest)............................................................................ 14

PCI DSS 3.0 ....................................................................................................................................................... 14
Discussion .......................................................................................................................................................... 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
Requirement 5: Protect all systems against malware and regularly update anti-virus software or programs 17
PCI DSS 3.0 ....................................................................................................................................................... 17
Discussion .......................................................................................................................................................... 17
Requirement 6: Develop and maintain secure systems and applications .......................................................... 18

PCI DSS 3.0 ....................................................................................................................................................... 18
Discussion .......................................................................................................................................................... 18
3
Get Connected
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
Requirement 8: Assign a unique ID to each person with computer access ....................................................... 20

PCI DSS 3.0 ....................................................................................................................................................... 20
Discussion .......................................................................................................................................................... 20
Requirement 9: Restrict physical access to cardholder data ............................................................................. 22

PCI DSS 3.0 ....................................................................................................................................................... 22
Discussion .......................................................................................................................................................... 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
Requirement 11: Regularly test security systems and processes ....................................................................... 24

PCI DSS 3.0 ....................................................................................................................................................... 24
Discussion .......................................................................................................................................................... 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
PCI DSS 3.0 REQUIREMENTS SUMMARY ............................................................................................ 26
THE LEADER IN NONSTOP SECURITY ................................................................................................. 61
4
Get Connected
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.
5
Get Connected
XYPRO
PCI Compliance and the HP Nonstop™ Server Enterprise
INTRODUCTION
“XYGATE is indispensable PCI requirements are imposed by the payment card
with regard to audit- organizations. Businesses that want to offer the ability to pay
compliance control, with a credit or debit card have no recourse except
monitoring and reporting.” compliance with PCI standards. Fortunately for businesses
that use the HP NonStopTM server, compliance becomes
Major International Credit easier with the use of XYGATE products.
Card Company
The Payment Card Industry Data Security Standard (PCI
"I have evaluated/used many DSS) is a standard based on the Visa Account Information
security products throughout Security (AIS) program and Cardholder Information Security
my over 30 year career and Program (CISP), MasterCard Site Data Protection (SDP)
XYGATE is my favorite." program, American Express Data Security Operating Policy
(DSOP), Discover Information Security and Compliance
Top 5 U.S. Banking (DISC), and JCB International Credit Card security
Institution standards. All of these companies worked together to merge
their standards into a single standard that is much easier to
"We rely heavily upon
implement for companies that accept payment card
XYGATE for our daily
transactions. The entire PCI DSS can be found at
security management." https://www.pcisecuritystandards.org/.
Top 10 Payments
This white paper shows where PCI DSS Version 3.0 is
Processor
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.
6
Get Connected
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 Self-Assessment Quarterly Network

Onsite Assessment
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
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
American Express Service Yes No ASV

Provider
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.
2
ASV means that only a company that has been certified as an Approved Scanning Vendor can perform the quarterly network
assessment.
7
Get Connected
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 1 Firewalls

Network
Build and Maintain A Secure 2 Eliminate vendor defaults

Network
Protect Cardholder Data 3 Protect stored data
Protect Cardholder Data 4 Encrypt data during transmission
Maintain A Vulnerability 5 Use and update anti-virus software

Management Program
Maintain A Vulnerability 6 Develop and maintain secure systems and applications

Management Program
Implement Strong Access 7 Restrict access by need-to-know

Control Measures
Implement Strong Access 8 Assign a unique ID to each user who has access
Control Measures
Implement Strong Access 9 Restrict physical access to cardholder data

Control Measures
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 12 Maintain a policy that addresses information security

Security Policy
8
Get Connected
Because standards have to apply to a diverse array of

WE WROTE THE merchants and service providers, which can range from
BOOK-- TWICE 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.
9
Get Connected
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
10
Get Connected
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.
11
Get Connected
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.
12
Get Connected
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.

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.
13
Get Connected
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
14
Get Connected
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.

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
15
Get Connected
(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.

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
16
Get Connected
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.

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.
17
Get Connected
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 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
18
Get Connected
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.

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.
19
Get Connected
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
20
Get Connected
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.

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.
21
Get Connected
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.

Not applicable.
22
Get Connected
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.

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.
23
Get Connected
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.

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.
24
Get Connected
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 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.
25
Get Connected
PCI DSS 3.0 REQUIREMENTS SUMMARY
PCI DSS 3.0 Requirement XYPRO Remarks
1: Install and maintain a firewall configuration to This requirement can be met with
protect cardholder data corporate policies, procedures, and
documentation.
1.1 Establish and implement firewall and router This requirement can be met with
configuration standards that include the following: corporate policies, procedures, and
documentation.
1.1.1 A formal process for approving and testing all network This requirement can be met with
connections and changes to the firewall and router corporate policies, procedures, and
configurations
documentation.
1.1.2 Current network diagram that identifies all This requirement can be met with
connections between the cardholder data environment and corporate policies, procedures, and
other networks, including any wireless networks
documentation.
1.1.3 Current diagram that shows all cardholder data flows This requirement can be met with
across systems and networks corporate policies, procedures, and
documentation.
1.1.4 Requirements for a firewall at each Internet This requirement can be met with
connection and between any demilitarized zone (DMZ) and corporate policies, procedures, and
the internal network zone
documentation.
1.1.5 Description of groups, roles, and responsibilities for This requirement can be met with
management of network components corporate policies, procedures, and
documentation.
1.1.6 Documentation and business justification for use of all This requirement can be met with
services, protocols, and ports allowed, including corporate policies, procedures, and
documentation of security features implemented for those
documentation.
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.
1.1.7 Requirement to review firewall and router rule sets at This requirement can be met with
least every six months corporate policies, procedures, and
documentation.
26
Get Connected
1.2 Build firewall and router configurations that restrict This requirement involves network
connections between untrusted networks and any system configuration external to the NonStop
components in the cardholder data environment.
server.
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.
1.2.1 Restrict inbound and outbound traffic to that which is This requirement involves network
necessary for the cardholder data environment, and configuration external to the NonStop
specifically deny all other traffic.
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 This requirement involves network
networks and the cardholder data environment, and configuration external to the NonStop
configure these firewalls to deny or, if traffic is necessary
server.
for business purposes, permit only authorized traffic
between the wireless environment and the cardholder data
environment.
1.3 Prohibit direct public access between the Internet and This requirement involves network
any system component in the cardholder data environment. configuration external to the NonStop
server.
1.3.1 Implement a DMZ to limit inbound traffic to only This requirement involves network
system components that provide authorized publicly configuration external to the NonStop
accessible services, protocols, and ports.
server.
1.3.2 Limit inbound Internet traffic to IP addresses within This requirement involves network
the DMZ. configuration external to the NonStop
server.
1.3.3 Do not allow any direct connections inbound or This requirement involves network
outbound for traffic between the Internet and the cardholder configuration external to the NonStop
data environment.
server.
1.3.4 Implement anti-spoofing measures to detect and This requirement involves network
block forged source IP addresses from entering the configuration external to the NonStop
network.
server.
27
Get Connected
(For example, block traffic originating from the Internet with

an internal source address.)
1.3.5 Do not allow unauthorized outbound traffic from the This requirement involves network
cardholder data environment to the Internet. configuration external to the NonStop
server.
1.3.6 Implement stateful inspection, also known as dynamic This requirement involves network
packet filtering. (That is, only “established” connections are configuration external to the NonStop
allowed into the network.)
server.
1.3.7 Place system components that store cardholder data This requirement involves network
(such as a database) in an internal network zone, configuration external to the NonStop
segregated from the DMZ and other untrusted networks.
server.
1.3.8 Do not disclose private IP addresses and routing This requirement involves network
information to unauthorized parties. configuration external to the NonStop
server.
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.
1.4 Install personal firewall software on any mobile and/or This requirement involves network
employee-owned devices that connect to the Internet when configuration external to the NonStop
outside the network (for example, laptops used by
server.
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.
1.5 Ensure that security policies and operational This requirement involves network
procedures for managing firewalls are documented, in use, configuration external to the NonStop
and known to all affected parties.
server.
28
Get Connected
2: Do not use vendor-supplied defaults for system All XYGATE modules.

passwords and other security parameters
2.1 Always change vendor-supplied defaults and remove or XSW can be used to monitor for HP-
disable unnecessary default accounts before installing a supplied accounts.
system on the network.
This applies to ALL default passwords, including but not

limited to those used by operating systems, software that XPQ can be used to force system
provides security services, application and system passwords to change.
accounts, point-of-sale (POS) terminals, Simple Network
Management Protocol (SNMP) community strings, etc.).
2.1.1 For wireless environments connected to the This requirement involves network
cardholder data environment or transmitting cardholder configuration external to the NonStop
data, change ALL wireless vendor defaults at installation,
server.
including but not limited to default wireless encryption keys,
passwords, and SNMP community strings.
2.2 Develop configuration standards for all system XSW can be used to compare NonStop
components. Assure that these standards address all server security to Best Practices as
known security vulnerabilities and are consistent with
defined in the books “Securing Your HP
industry-accepted system hardening standards.
NonStop Server: A Practical Handbook”
Sources of industry-accepted system hardening standards (ISBN: 978-1555583149) and “Securing
may include, but are not limited to: 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 This requirement can be met with
prevent functions that require different security levels from corporate policies, procedures, and
co-existing on the same server. (For example, web servers,
documentation.
database servers, and DNS should be implemented on
separate servers.)
Note: Where virtualization technologies are in use,

XSW can be used for monitoring.
implement only one primary function per virtual system
component.
2.2.2 Enable only necessary services, protocols, daemons, XSW can be used for monitoring.
etc., as required for the function of the system.
29
Get Connected
2.2.3 Implement additional security features for any XHE, XSH, XSC, and XEL can be used.
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
2.2.4 Configure system security parameters to prevent All XYGATE modules.
misuse.
2.2.5 Remove all unnecessary functionality, such as Use XSW to identify this unnecessary
scripts, drivers, features, subsystems, file systems, and functionality.
unnecessary web servers
2.3 Encrypt all non-console administrative access using Use XHE, XSH, XSC, and XEL for this
strong cryptography. Use technologies such as SSH, VPN, encryption.
or SSL/TLS for web-based management and other non-
console administrative access.
2.4 Maintain an inventory of system components that are in This requirement can be met with
scope for PCI DSS. corporate policies, procedures, and
documentation.
2.5 Ensure that security policies and operational This requirement can be met with
procedures for managing vendor defaults and other corporate policies, procedures, and
security parameters are documented, in use, and known to
documentation.
all affected parties.
2.6 Shared hosting providers must protect each entity’s All XYGATE modules.
hosted environment and cardholder data. These providers
must meet specific requirements as detailed in Appendix A:
Additional PCI DSS Requirements for Shared Hosting
Providers.
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.
30
Get Connected
3.1 Keep cardholder data storage to a minimum by This requirement can be met with
implementing data retention and disposal policies, corporate policies, procedures, and
procedures and processes that include at least the
documentation.
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.
3.2 Do not store sensitive authentication data after This requirement can be met with
authorization (even if encrypted). If sensitive authentication corporate policies, procedures, and
data is received, render all data unrecoverable upon
documentation.
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:
3.2.1 Do not store the full contents of any track (from the This requirement can be met with
magnetic stripe located on the back of a card, equivalent corporate policies, procedures, and
data contained on a chip, or elsewhere). This data is
documentation.
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.
3.2.2 Do not store the card verification code or value (three- This requirement can be met with
digit or four-digit number printed on the front or back of a corporate policies, procedures, and
payment card) used to verify card-not-present transactions.
documentation.
3.2.3 Do not store the personal identification number (PIN) This requirement can be met with
or the encrypted PIN block. corporate policies, procedures, and
documentation.
31
Get Connected
3.3 Mask PAN when displayed (the first six and last four This requirement can be met with
digits are the maximum number of digits to be displayed), corporate policies, procedures, and
such that only personnel with a legitimate business need
documentation.
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.
3.4 Render PAN unreadable anywhere it is stored XDP can be used in conjunction with
(including on portable digital media, backup media, and in Voltage security software to provide
logs) by using any of the following approaches:
Format Preserving Encryption (FPE) or
- One-way hashes based on strong cryptography, (hash
must be of the entire PAN) Secure-Stateless-Tokenization (SST) for
- Truncation (hashing cannot be used to replace the PAN and other sensitive data without
truncated segment of PAN) application or database changes.
- Index tokens and pads (pads must be securely stored)
- Strong cryptography with associated key-management
processes and procedures.
XEL can be used to provide strong
Note: It is a relatively trivial effort for a malicious individual
to reconstruct original PAN data if they have access to both cryptography with associated key
the truncated and hashed version of a PAN. Where hashed management processes. XEL provides
and truncated versions of the same PAN are present in an tools to be included in any in-house
entity’s environment, additional controls should be in place
development.
to ensure that the hashed and truncated versions cannot be
correlated to reconstruct the original PAN.
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- Volume Level Encryption (VLE) is
level database encryption), logical access must be available from HP for this purpose.
managed separately and independently of native operating
However, using VLE as the sole means of
system authentication and access control mechanisms (for
example, by not using local user account databases or protecting cardholder data is not
general network login credentials). Decryption keys must recommended since VLE only protects a
not be associated with user accounts. disk after it has been removed from the
system.
32
Get Connected
3.5 Document and implement procedures to protect keys This requirement can be met with
used to secure stored cardholder data against disclosure corporate policies, procedures, and
and misuse:
documentation.
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.
3.5.1 Restrict access to cryptographic keys to the fewest XOS can be used to protect cryptographic
number of custodians necessary. 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 XOS can be used to protect cryptographic
cardholder data in one (or more) of the following forms at keys at the resource level.
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- integrate encryption into the application.
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.
3.5.3 Store cryptographic keys in the fewest possible XDP, XKM, and XEL can be used to
locations. integrate encryption into the application.
3.6 Fully document and implement all key-management This requirement can be met with
processes and procedures for cryptographic keys used for corporate policies, procedures, and
encryption of cardholder data, including the following:
documentation.
Note: Numerous industry standards for key management

are available from various resources including NIST, which
can be found at http://csrc.nist.gov.
3.6.1 Generation of strong cryptographic keys XDP, XKM, and XEL can be used to
33
Get Connected
3.6.2 Secure cryptographic key distribution XDP, XKM, and XEL can be used to
3.6.3 Secure cryptographic key storage XDP, XKM, and XEL can be used to
3.6.4 Cryptographic key changes for keys that have This requirement can be met with
reached the end of their crypto-period (for example, after a corporate policies, procedures, and
defined period of time has passed and/or after a certain
documentation.
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).
3.6.5 Retirement or replacement (for example, archiving, The required solution is not included in the
destruction, and/or revocation) of keys as deemed XYGATE product offering.
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.
3.6.6 If manual clear-text cryptographic key-management XDP, XKM, and XEL can be used to
operations are used, these operations must be managed integrate encryption into the application.
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.
3.6.7 Prevention of unauthorized substitution of XDP, XKM, and XEL can be used to
cryptographic keys. integrate encryption into the application.
3.6.8 Requirement for cryptographic key custodians to XDP, XKM, and XEL can be used to
formally acknowledge that they understand and accept their integrate encryption into the application.
key-custodian responsibilities.
procedures for protecting stored cardholder data are corporate policies, procedures, and
documented, in use, and known to all affected parties.
documentation.
4: Encrypt transmission of cardholder data across XHE, XSH and XFE can be used to
open, public networks encrypt all varieties of data transmission.
34
Get Connected

XSC can be used to provide the

encryption component for the PC.
4.1 Use strong cryptography and security protocols (for XHE, XSH and XFE can be used to
example, SSL/TLS, IPSEC, SSH, etc.) to safeguard encrypt all varieties of data transmission.
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: XSC can be used to provide the
- The Internet encryption component for the PC.
- 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.
4.1.1 Ensure wireless networks transmitting cardholder This requirement involves network
data or connected to the cardholder data environment, use configuration external to the NonStop
industry best practices (for example, IEEE 802.11i) to
server.
implement strong encryption for authentication and
transmission.
Note: The use of WEP as a security control is prohibited.
4.2 Never send unprotected PANs by end-user messaging This requirement can be met with
technologies (for example, e-mail, instant messaging, chat, corporate policies, procedures, and
etc.).
documentation.
procedures for encrypting transmissions of cardholder data corporate policies, procedures, and
are documented, in use, and known to all affected parties.
documentation.
5: Protect all systems against malware and regularly Traditional consumer anti-virus is not
update anti-virus software or programs applicable to the HP NonStop server.
35
Get Connected
5.1 Deploy anti-virus software on all systems commonly XSW can be used for file integrity
affected by malicious software (particularly personal checking to provide object file validation
computers and servers).
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 XSW can be used for file integrity
detecting, removing, and protecting against all known types checking to protect against Trojan Horses.
of malicious software.
5.1.2 For systems considered to be not commonly affected XSW can be used for file integrity
by malicious software, perform periodic evaluations to checking.
identify and evaluate evolving malware threats in order to
confirm whether such systems continue to not require anti-
virus software.
5.2 Ensure that all anti-virus mechanisms are maintained XSW can be used for file integrity
as follows: checking.
- Are kept current,
- Perform periodic scans
- Generate audit logs which are retained per PCI DSS
Requirement 10.7.
5.3 Ensure that anti-virus mechanisms are actively running XSW can be used for file integrity
and cannot be disabled or altered by users, unless checking.
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.
procedures for protecting systems against malware are corporate policies, procedures, and
documentation.
6: Develop and maintain secure systems and This requirement can be met with
applications corporate policies, procedures and
documentation.
6.1 Establish a process to identify security vulnerabilities, This requirement can be met with
using reputable outside sources for security vulnerability corporate policies, procedures, and
information, and assign a risk ranking (for example, as
documentation.
“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
36
Get Connected
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 This requirement can be met with
protected from known vulnerabilities by installing applicable corporate policies, procedures, and
vendor-supplied security patches. Install critical security
documentation.
patches within one month of release.
Note: Critical security patches should be identified

according to the risk ranking process defined in
Requirement 6.1.
6.3 Develop internal and external software applications This requirement can be met with
(including web-based administrative access to applications) corporate policies, procedures, and
securely, as follows:
documentation.
- 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 XDP, XKM, and XEL can be used to
Note: this applies to all software developed internally as
well as bespoke or custom software developed by a third
party.
6.3.1 Remove development, test and/or custom application This requirement can be met with
accounts, user IDs, and passwords before applications corporate policies, procedures, and
become active or are released to customers.
documentation.
37
Get Connected
6.3.2 Review custom code prior to release to production or XOS can be used to provide strong object
customers in order to identify any potential coding separation.
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
XCM can be used to control execution in
about code-review techniques and secure coding practices.
- Code reviews ensure code is developed according to CPU resources.
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.
6.4 Follow change control processes and procedures for all This requirement can be met with
changes to system components. The processes must corporate policies, procedures, and
include the following:
documentation.
6.4.1 Separate development/test environments from This requirement can be met with
production environments, and enforce the separation with corporate policies, procedures, and
access controls.
documentation.
XYGATE products can be used to enforce

separation of duties.
6.4.2 Separation of duties between development/test and This requirement can be met with
production environments corporate policies, procedures, and
documentation.
XYGATE products can be used to enforce

separation of duties.
38
Get Connected
6.4.3 Production data (live PANs) are not used for testing This requirement can be met with
or development corporate policies, procedures, and
documentation.
6.4.4 Removal of test data and accounts before production This requirement can be met with
systems become active
corporate policies, procedures, and
documentation.
6.4.5 Change control procedures for the implementation of This requirement can be met with
security patches and software modifications must include corporate policies, procedures, and
the following:
documentation.
6.4.5.1 Documentation of impact. This requirement can be met with

documentation.
6.4.5.2 Documented change approval by authorized This requirement can be met with
parties. corporate policies, procedures, and
documentation.
6.4.5.3 Functionality testing to verify that the change does This requirement can be met with
not adversely impact the security of the system. corporate policies, procedures, and
documentation.
6.4.5.4 Back-out procedures. This requirement can be met with

documentation.
6.5 Address common coding vulnerabilities in software- This requirement can be met with
development processes as follows: corporate policies, procedures, and
- Train developers in secure coding techniques, including
documentation.
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.
6.5.1 Injection flaws, particularly SQL injection. Also This requirement can be met with
consider OS Command Injection, LDAP and XPath corporate policies, procedures, and
injection flaws as well as other injection flaws.
documentation.
39
Get Connected
6.5.2 Buffer overflows This requirement can be met with

documentation.
6.5.3 Insecure cryptographic storage This requirement can be met with

documentation.
6.5.4 Insecure communications This requirement can be met with

documentation.
6.5.5 Improper error handling This requirement can be met with

documentation.
6.5.6 All “high risk” vulnerabilities identified in the This requirement can be met with
vulnerability identification process (as defined in PCI DSS corporate policies, procedures, and
Requirement 6.1).
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

documentation.
6.5.8 Improper access control (such as insecure direct This requirement can be met with
object references, failure to restrict URL access, directory corporate policies, procedures, and
traversal, and failure to restrict user access to functions).
documentation.
6.5.9 Cross-site request forgery (CSRF) This requirement can be met with
documentation.
6.5.10 Broken authentication and session management This requirement can be met with
documentation.
Note: Requirement 6.5.10 is a best practice until June 30,
2015, after
40
Get Connected
6.6 For public-facing web applications, address new threats The required solution is not included in the
and vulnerabilities on an ongoing basis and ensure these XYGATE product offering.
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.
procedures for developing and maintaining secure systems corporate policies, procedures, and
and applications are documented, in use, and known to all
documentation.
affected parties.
7: Restrict access to cardholder data by business need All XYGATE modules.

to know
7.1 Limit access to system components and cardholder XAC and XOS can be used to provide
data to only those individuals whose job requires such action control and object control to
access.
authorized individuals only.
7.1.1 Define access needs for each role, including: XAC and XOS can be used to provide
- System components and data resources that each role action control and object control to
needs to access for their job function
- Level of privilege required (for example, user,
administrator, etc.) for accessing resources.
7.1.2 Restrict access to privileged user IDs to least XAC and XOS can be used to provide
privileges necessary to perform job responsibilities. action control and object control to
7.1.3 Assign access based on individual personnel’s job XAC and XOS can be used to provide
classification and function. action control and object control to
7.1.4 Require documented approval by authorized parties This requirement can be met with
specifying required privileges. corporate policies, procedures, and
documentation.
41
Get Connected
7.2 Establish an access control system for systems XAC, XCM, and XOS can be used.
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:
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 XAC, XCM, and XOS can be used.
classification and function.
7.2.3 Default “deny-all” setting. XAC, XCM, and XOS can be used.
procedures for restricting access to cardholder data are corporate policies, procedures, and
documentation.
8: Identify and authenticate access to system XAC can be used to support the functional
components use of unique userids.
XSM can be used to create userids.
8.1 Define and implement policies and procedures to This requirement can be met with
ensure proper user identification management for non- corporate policies, procedures, and
consumer users and administrators on all system
documentation.
components as follows:
8.1.1 Assign all users a unique ID before allowing them to XUA, XCM, and XSM can be used.
access system components or cardholder data.
8.1.2 Control addition, deletion, and modification of user All XYGATE modules.
IDs, credentials, and other identifier objects.
8.1.3 Immediately revoke access for any terminated users. All XYGATE modules.
8.1.4 Remove/disable inactive user accounts at least every XSW can be used to regularly identify
90 days. inactive user accounts.
42
Get Connected
XSM can be used to remove/disable

inactive user accounts.
8.1.5 Manage IDs used by vendors to access, support, or XSM, XAC, XCM, and XUA can be used.
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.
8.1.6 Limit repeated access attempts by locking out the This requirement can be met with
user ID after not more than six attempts. corporate policies, procedures, and
documentation.
8.1.7 Set the lockout duration to a minimum of 30 minutes XUA can be used.
or until an administrator enables the user ID.
8.1.8 If a session has been idle for more than 15 minutes, XAC can be used.
require the user to re-authenticate to re-activate the
terminal or session.
8.2 In addition to assigning a unique ID, ensure proper XUA and/or XPQ can be used.
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.
8.2.1 Using strong cryptography, render all authentication XPQ can be used.
credentials (such as passwords/phrases) unreadable
during transmission and storage on all system components.
8.2.2 Verify user identity before modifying any XUA can be used.
authentication credential—for example, performing
password resets, provisioning new tokens, or generating
new keys.
8.2.3 Passwords/phrases must meet the following: XPQ can be used.
- 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.
8.2.4 Change user passwords/passphrases at least every XUA can be used.

90 days.
8.2.5 Do not allow an individual to submit a new XUA can be used.
password/phrase that is the same as any of the last four
passwords/phrases he or she has used.
43
Get Connected
8.2.6 Set passwords/phrases for first-time use and upon XUA and XPQ can be used.
reset to a unique value for each user, and change
immediately after the first use.
8.3 Incorporate two-factor authentication for remote XUA can be used.

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.
8.4 Document and communicate authentication procedures This requirement can be met with
and policies to all users including: corporate policies, procedures, and
- Guidance on selecting strong authentication credentials
documentation.
- 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.
8.5 Do not use group, shared, or generic IDs, passwords, This requirement can be met with
or other authentication methods as follows: corporate policies, procedures, and
- Generic user IDs are disabled or removed.
documentation.
- 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.
8.5.1 Additional requirement for service providers: This requirement can be met with
Service providers with remote access to customer premises corporate policies, procedures, and
(for example, for support of POS systems or servers) must
documentation.
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.
8.6 Where other authentication mechanisms are used (for This requirement can be met with
example, physical or logical security tokens, smart cards, corporate policies, procedures, and
certificates, etc.), use of these mechanisms must be
assigned as follows:
44
Get Connected
- Authentication mechanisms must be assigned to an documentation.

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.
8.7 All access to any database containing cardholder data XAC and XOS can be used to provide
(including access by applications, administrators, and all action control and object control to
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 XDP, XKM, and XEL can be used to
used by the applications (and not by individual users or integrate encryption into the application.
other non-application processes).
procedures for identification and authentication are 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 This requirement can be met with
monitor physical access to systems in the cardholder data corporate policies, procedures, and
environment.
documentation.
9.1.1 Use video cameras and/or access control This requirement can be met with
mechanisms to monitor individual physical access to corporate policies, procedures, and
sensitive areas. Review collected data and correlate with
documentation.
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.
9.1.2 Implement physical and/or logical controls to restrict This requirement can be met with
access to publicly accessible network jacks. corporate policies, procedures, and
documentation.
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.
45
Get Connected
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, This requirement can be met with
gateways, handheld devices, networking/communications corporate policies, procedures, and
hardware, and telecommunication lines.
documentation.
9.2 Develop procedures to easily distinguish between onsite This requirement can be met with
personnel and visitors, to include:
- Identifying new onsite personnel or visitors (for example,
assigning badges) documentation.
- Changes to access requirements
- Revoking or terminating onsite personnel and expired visitor
identification (such as ID badges).
9.3 Control physical access for onsite personnel to the sensitive This requirement can be met with
areas as follows:
- Access must be authorized and based on individual job function.
- Access is revoked immediately upon termination, and all documentation.
physical access mechanisms, such as keys, access cards, etc.,
are returned or disabled.
9.4 Implement procedures to identify and authorize visitors. This requirement can be met with
Procedures should include the following:
documentation.
9.4.1 Visitors are authorized before entering, and escorted This requirement can be met with
at all times within, areas where cardholder data is corporate policies, procedures, and
processed or maintained.
documentation.
9.4.2 Visitors are identified and given a badge or other This requirement can be met with
identification that expires and that visibly distinguishes the corporate policies, procedures, and
visitors from onsite personnel.
documentation.
9.4.3 Visitors are asked to surrender the badge or This requirement can be met with
identification before leaving the facility or at the date of corporate policies, procedures, and
expiration.
documentation.
9.4.4 A visitor log is used to maintain a physical audit trail This requirement can be met with
of visitor activity to the facility as well as computer rooms corporate policies, procedures, and
and data centers where cardholder data is stored or
documentation.
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.
46
Get Connected
9.5 Physically secure all media. This requirement can be met with
documentation.
9.5.1 Store media backups in a secure location, preferably This requirement can be met with
an off-site facility, such as an alternate or backup site, or a corporate policies, procedures, and
commercial storage facility. Review the location’s security
documentation.
at least annually.
9.6 Maintain strict control over the internal or external This requirement can be met with
distribution of any kind of media, including the following: corporate policies, procedures, and
documentation.
9.6.1 Classify media so the sensitivity of the data can be This requirement can be met with
determined. corporate policies, procedures, and
documentation.
9.6.2 Send the media by secured courier or other delivery This requirement can be met with
method that can be accurately tracked. corporate policies, procedures, and
documentation.
9.6.3 Ensure management approves any and all media that This requirement can be met with
is moved from a secured area (including when media is corporate policies, procedures, and
distributed to individuals).
documentation.
9.7 Maintain strict control over the storage and accessibility This requirement can be met with
of media. corporate policies, procedures, and
documentation.
9.7.1 Properly maintain inventory logs of all media and This requirement can be met with
conduct media inventories at least annually. corporate policies, procedures, and
documentation.
9.8 Destroy media when it is no longer needed for business This requirement can be met with
or legal reasons as follows: corporate policies, procedures, and
documentation.
9.8.1 Shred, incinerate, or pulp hard-copy materials so that This requirement can be met with
cardholder data cannot be reconstructed. Secure storage corporate policies, procedures, and
containers used for materials that are to be destroyed.
documentation.
9.8.2 Render cardholder data on electronic media This requirement can be met with
unrecoverable so that cardholder data cannot be corporate policies, procedures, and
reconstructed.
documentation.
47
Get Connected
9.9 Protect devices that capture payment card data via This requirement can be met with
direct physical interaction with the card from tampering and corporate policies, procedures, and
substitution.
documentation.
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,

9.9.1 Maintain an up-to-date list of devices. The list should include This requirement can be met with
the following:
- Make, model of device
- Location of device (for example, the address of the site or facility documentation.
where the device is located)
- Device serial number or other method of unique identification.
9.9.2 Periodically inspect device surfaces to detect This requirement can be met with
tampering (for example, addition of card skimmers to corporate policies, procedures, and
devices), or substitution (for example, by checking the
documentation.
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.
9.9.3 Provide training for personnel to be aware of This requirement can be met with
attempted tampering or replacement of devices. Training corporate policies, procedures, and
should include the following:
documentation.
- 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).
procedures for restricting physical access to cardholder corporate policies, procedures, and
data are documented, in use, and known to all affected
documentation.
parties.
10: Track and monitor all access to network resources All XYGATE modules.
and cardholder data
48
Get Connected
10.1 Implement audit trails to link all access to system All XYGATE modules.
components to each individual user.
10.2 Implement automated audit trails for all system All XYGATE modules.
components to reconstruct the following events:
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 All XYGATE modules.
administrative privileges
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 All XYGATE modules.

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
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 All XYGATE modules.
system components for each event:
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 All XYGATE modules.

component, or resource.
10.4 Using time-synchronization technology, synchronize The required solution is not included in the
all critical system clocks and times and ensure that the XYGATE product offering.
following is implemented for acquiring, distributing, and
storing time.
Note: One example of time synchronization technology is

Network Time Protocol (NTP).
10.4.1 Critical systems have the correct and consistent XOS, XRM, XMA, and XEM can be used.
time.
49
Get Connected
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 XOS, XRM, XMA, and XEM can be used.
time sources.
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- XOS, XRM, XMA, and XEM can be used.
related need.
10.5.2 Protect audit trail files from unauthorized XOS can be used.
modifications.
10.5.3 Promptly back up audit trail files to a centralized log XMA can be used.
server or media that is difficult to alter.
10.5.4 Write logs for external-facing technologies onto a This requirement involves network
secure, centralized, internal log server or media device. configuration external to the NonStop
server.
10.5.5 Use file-integrity monitoring or change-detection XOS and XMA can be used.
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).
10.6 Review logs and security events for all system XRM, XMA, and XEM can be used.
components to identify anomalies or suspicious activity.
Note: Log harvesting, parsing, and alerting tools may be

used to meet this Requirement.
10.6.1 Review the following at least daily: XMA can be used.

- 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.).
10.6.2 Review logs of all other system components This requirement can be met with
periodically based on the organization’s policies and risk corporate policies, procedures, and
management strategy, as determined by the organization’s
documentation.
annual risk assessment.
10.6.3 Follow up exceptions and anomalies identified This requirement can be met with
during the review process. corporate policies, procedures, and
documentation.
50
Get Connected
10.7 Retain audit trail history for at least one year, with a This requirement can be met with
minimum of three months immediately available for corporate policies, procedures, and
analysis (for example, online, archived, or restorable from
documentation.
backup).
procedures for monitoring all access to network resources corporate policies, procedures, and
and cardholder data are documented, in use, and known to
documentation.
all affected parties.
11: Regularly test security systems and processes XSW and XMA can be used.
11.1 Implement processes to test for the presence of This requirement can be met with
wireless access points (802.11), and detect and identify all corporate policies, procedures, and
authorized and unauthorized wireless access points on a
documentation.
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.
11.1.1 Maintain an inventory of authorized wireless access This requirement can be met with
points including a documented business justification. corporate policies, procedures, and
documentation.
11.1.2 Implement incident response procedures in the This requirement can be met with
event unauthorized wireless access points are detected. corporate policies, procedures, and
documentation.
11.2 Run internal and external network vulnerability scans The required solution is not included in the
at least quarterly and after any significant change in the XYGATE product offering.
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.
51
Get Connected
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 The required solution is not included in the
rescans as needed, until all “high-risk” vulnerabilities (as XYGATE product offering.
identified in Requirement 6.1) are resolved. Scans must be
performed by qualified personnel.
11.2.2 Perform quarterly external vulnerability scans, via an The required solution is not included in the
Approved Scanning Vendor (ASV) approved by the XYGATE product offering.
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.
11.2.3 Perform internal and external scans, and rescans as The required solution is not included in the
needed, after any significant change. Scans must be XYGATE product offering.
performed by qualified personnel.
11.3 Implement a methodology for penetration testing that The required solution is not included in the
includes the following: XYGATE product offering.
- 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
52
Get Connected
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 The required solution is not included in the
annually and after any significant infrastructure or XYGATE product offering.
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).
11.3.2 Perform internal penetration testing at least annually XMA can be used to report and alert on
and after any significant infrastructure or application system activity.
upgrade or modification (such as an operating system
upgrade, a sub-network added to the environment, or a
web server added to the environment).
11.3.3 Exploitable vulnerabilities found during penetration XSW can be used for file integrity
testing are corrected and testing is repeated to verify the checking.
corrections.
11.3.4 If segmentation is used to isolate the CDE from The required solution is not included in the
other networks, perform penetration tests at least annually XYGATE product offering.
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.
11.4 Use intrusion-detection and/or intrusion-prevention XMA can be used to report and alert on
techniques to detect and/or prevent intrusions into the system activity.
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.
11.5 Deploy a change-detection mechanism (for example, XSW can be used for file integrity
file-integrity monitoring tools) to alert personnel to checking.
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
53
Get Connected
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 This requirement can be met with
generated by the change-detection solution. corporate policies, procedures, and
documentation.
procedures for security monitoring and testing are corporate policies, procedures, and
documentation.
12: Maintain a policy that addresses information XSW can be used for file integrity
security for all personnel checking.
12.1 Establish, publish, maintain, and disseminate a This requirement can be met with
security policy. corporate policies, procedures, and
documentation.
12.1.1 Review the security policy at least annually and This requirement can be met with
update the policy when the environment changes. corporate policies, procedures, and
documentation.
12.2 Implement a risk-assessment process that: This requirement can be met with
- Is performed at least annually and upon significant corporate policies, procedures, and
changes to the environment (for example, acquisition,
documentation.
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.
12.3 Develop usage policies for critical technologies and This requirement can be met with
define proper use of these technologies. corporate policies, procedures, and
documentation.
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.
54
Get Connected
Ensure these usage policies require the following:
12.3.1 Explicit approval by authorized parties This requirement can be met with
documentation.
12.3.2 Authentication for use of the technology This requirement can be met with
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 This requirement can be met with
owner, contact information, and purpose (for example, corporate policies, procedures, and
labeling, coding, and/or inventorying of devices)
documentation.
12.3.5 Acceptable uses of the technology This requirement can be met with
documentation.
12.3.6 Acceptable network locations for the technologies This requirement can be met with
documentation.
12.3.7 List of company-approved products This requirement can be met with

documentation.
12.3.8 Automatic disconnect of sessions for remote-access XAC can be used for disconnecting
technologies after a specific period of inactivity remote access technologies sessions.
12.3.9 Activation of remote-access technologies for XAC can be used for remote access
vendors and business partners only when needed by technology disconnects.
vendors and business partners, with immediate
deactivation after use
XCM, XHE, and XUA can be used for port

protection in general
55
Get Connected
12.3.10 For personnel accessing cardholder data via This requirement can be met with
remote-access technologies, prohibit the copying, moving, corporate policies, procedures, and
and storage of cardholder data onto local hard drives and
documentation.
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.
12.4 Ensure that the security policy and procedures clearly This requirement can be met with
define information security responsibilities for all personnel. corporate policies, procedures, and
documentation.
12.5 Assign to an individual or team the following This requirement can be met with
information security management responsibilities: corporate policies, procedures, and
documentation.
12.5.1 Establish, document, and distribute security policies This requirement can be met with
and procedures. corporate policies, procedures, and
documentation.
12.5.2 Monitor and analyze security alerts and information, XSW and XMA can be used to facilitate
and distribute to appropriate personnel. monitoring and alerting.
12.5.3 Establish, document, and distribute security incident This requirement can be met with
response and escalation procedures to ensure timely and corporate policies, procedures, and
effective handling of all situations.
documentation.
12.5.4 Administer user accounts, including additions, XSM can be used to administer userids.
deletions, and modifications.
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.
56
Get Connected
12.6 Implement a formal security awareness program to This requirement can be met with
make all personnel aware of the importance of cardholder corporate policies, procedures, and
data security.
documentation.
12.6.1 Educate personnel upon hire and at least annually. This requirement can be met with
documentation.
Note: Methods can vary depending on the role of the
personnel and their level of access to the cardholder data.
12.6.2 Require personnel to acknowledge at least annually This requirement can be met with
that they have read and understood the security policy and corporate policies, procedures, and
procedures.
documentation.
12.7 Screen potential personnel prior to hire to minimize This requirement can be met with
the risk of attacks from internal sources. (Examples of corporate policies, procedures, and
background checks include previous employment history,
documentation.
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.
12.8 Maintain and implement policies and procedures to This requirement can be met with
manage service providers with whom cardholder data is corporate policies, procedures, and
shared, or that could affect the security of cardholder data,
documentation.
as follows:
12.8.1 Maintain a list of service providers. This requirement can be met with
documentation.
12.8.2 Maintain a written agreement that includes an This requirement can be met with
acknowledgement that the service providers are corporate policies, procedures, and
responsible for the security of cardholder data the service
documentation.
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
57
Get Connected
wording provided in this requirement.
12.8.3 Ensure there is an established process for engaging This requirement can be met with
service providers including proper due diligence prior to corporate policies, procedures, and
engagement.
documentation.
12.8.4 Maintain a program to monitor service providers’ PCI This requirement can be met with
DSS compliance status at least annually. corporate policies, procedures, and
documentation.
12.8.5 Maintain information about which PCI DSS This requirement can be met with
requirements are managed by each service provider, and corporate policies, procedures, and
which are managed by the entity.
documentation.
12.9 Additional requirement for service providers: This requirement can be met with
Service providers acknowledge in writing to customers that corporate policies, procedures, and
they are responsible for the security of cardholder data the
documentation.
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,

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.
12.10 Implement an incident response plan. Be prepared to This requirement can be met with
respond immediately to a system breach. corporate policies, procedures, and
documentation.
12.10.1 Create the incident response plan to be This requirement can be met with
implemented in the event of system breach. Ensure the corporate policies, procedures, and
plan addresses the following, at a minimum:
documentation.
- 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
58
Get Connected
- 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
documentation.
12.10.3 Designate specific personnel to be available on a This requirement can be met with
24/7 basis to respond to alerts. corporate policies, procedures, and
documentation.
12.10.4 Provide appropriate training to staff with security This requirement can be met with
breach response responsibilities. corporate policies, procedures, and
documentation.
12.10.5 Include alerts from security monitoring systems, XMA and XEM can be used.
including but not limited to intrusion-detection, intrusion-
prevention, firewalls, and file-integrity monitoring systems.
12.10.6 Develop a process to modify and evolve the This requirement can be met with
incident response plan according to lessons learned and to corporate policies, procedures, and
incorporate industry developments.
documentation.
A.1: Shared hosting providers must protect the All XYGATE products.
cardholder data environment
A.1 Protect each entity’s (that is, merchant, service All XYGATE products.
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.
A.1.1 Ensure that each entity only runs processes that XAC can be used.
have access to that entity’s cardholder data environment.
59
Get Connected
A.1.2 Restrict each entity’s access and privileges to its own XOS can be used.
cardholder data environment only.
A.1.3 Ensure logging and audit trails are enabled and This requirement can be met with
unique to each entity’s cardholder data environment and corporate policies, procedures, and
consistent with PCI DSS Requirement 10.
documentation.
A.1.4 Enable processes to provide for timely forensic This requirement can be met with
investigation in the event of a compromise to any hosted corporate policies, procedures, and
merchant or service provider.
documentation.
60
Get Connected
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
61
Get Connected

White Paper - PCI Compliance

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

White Paper - PCI Compliance

Uploaded by

Copyright:

Available Formats

XYGATE® & PCI COMPLIANCE

PCI DSS VERSION 3.0

XYPRO TECHNOLOGY CORPORATION

4100 GUARDIAN STREET, SUITE 100

Copyright - ©XYPRO Technology Corporation, 2015. All rights reserved.

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

PROTECT CARDHOLDER DATA ........................................................................................................... 14

Requirement 3: Protect stored cardholder data (data at rest)............................................................................ 14

MAINTAIN A VULNERABILITY MANAGEMENT PROGRAM................................................................. 16

Requirement 6: Develop and maintain secure systems and applications .......................................................... 18

IMPLEMENT STRONG ACCESS CONTROL MEASURES ..................................................................... 19

Requirement 7: Restrict access to cardholder data by business need-to-know................................................. 19

Requirement 8: Assign a unique ID to each person with computer access ....................................................... 20

Requirement 9: Restrict physical access to cardholder data ............................................................................. 22

REGULARLY MONITOR AND TEST NETWORKS ................................................................................. 23

Requirement 11: Regularly test security systems and processes ....................................................................... 24

MAINTAIN AN INFORMATION SECURITY POLICY ............................................................................... 24

PCI DSS 3.0 REQUIREMENTS SUMMARY ............................................................................................ 26

THE LEADER IN NONSTOP SECURITY ................................................................................................. 61

A summary of the PCI requirements is provided that explains

Payment Card Level Annual Self-Assessment Quarterly Network

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 Yes No ASV

American Express Merchant 1 Yes No ASV

American Express Merchant 2 No No ASV

American Express Merchant 3 No No Recommended

PCI Application to HP NonStop™ Server Systems

Area Requirement Title

Build and Maintain A Secure 1 Firewalls

Build and Maintain A Secure 2 Eliminate vendor defaults

Protect Cardholder Data 3 Protect stored data

Protect Cardholder Data 4 Encrypt data during transmission

Maintain A Vulnerability 5 Use and update anti-virus software

Maintain A Vulnerability 6 Develop and maintain secure systems and applications

Implement Strong Access 7 Restrict access by need-to-know

Implement Strong Access 9 Restrict physical access to cardholder data

Maintain an Information 12 Maintain a policy that addresses information security

Because standards have to apply to a diverse array of

One first step that any organization using HP NonStop™

Securing Your HP NonStop™ Server: A Practical Handbook (ISBN:

A second step would be to use XYPRO’s XYGATE

XYGATE Product Description

Data Protection (XDP) XDP provides application-based, Format-Preserving Encryption (FPE)

Event Monitor (XEM) XEM is a MS Windows-based application that connects via a

File Encryption (XFE) XFE provides file encryption, decryption, compression,

PCI DSS 3.0 REQUIREMENTS

BUILD AND MAINTAIN A SECURE NETWORK AND SYSTEMS