Windward Software Inc

• PA-DSS is the standard against which System Five has been tested, assessed, and validated.
• PCI-DSS Compliance is obtained by the merchant, and is an assessment of your actual server (or hosting) environment.

• “PCI DSS Compliance” is the responsibility of the merchant and their hosting provider, working together, using PCI compliant server architecture with proper hardware & software configurations and access control procedures.
• PA-DSS Validation is intended to ensure that System Five will help you achieve and maintain PCI Compliance with respect to how System Five handles user accounts, passwords, encryption, and other payment data related information.
• Payment Card Industry (PCI) has developed security standards for handling card holder information in a published standard called the PCI Data Security Standard (DSS). The security requirements defined in the DSS apply to all members, merchants, and service providers that store, process or transmit card holder data.
• The PCI DSS requirements apply to all system components within the payment application environment which is defined as any network device, host, or application included in, or connected to, a network segment where card holder data is stored, processed or transmitted

Build and Maintain a Secure Network
1. Install and maintain a firewall configuration to protect data
2. Do not use vendor-supplied defaults for system passwords and other security parameters

Protect Card holder Data
3. Protect Stored Data
4. Encrypt transmission of card holder data and sensitive information across public networks

Maintain a Vulnerability Management Program
5. Use and regularly update anti-virus software
6. Develop and maintain secure systems and applications

Implement Strong Access Control Measures
7. Restrict access to data by business need-to-know
8. Assign a unique Id to each person with computer access
9. Restrict physical access to card holder data

Regularly Monitor and Test Networks
10. Track and monitor all access to network resources and card holder data
11. Regularly test security systems and processes

Maintain an Information Security Policy
12. Maintain a policy that addresses information security

Keep in mind the following guidelines when dealing with sensitive Credit Card data:

• Collect card holder data only when needed to solve a specific problem.
• Store such data only in specific, known locations with limited access.
• Collect only the limited amount of data needed to solve a specific problem.
• Encrypt card holder data while stored.
• Securely delete such data immediately after use.
• Never collect or store sensitive data (MSR track 2,PIN,CVV)
• Sensitive Data

This data can not be stored

• Track 2 – the magnetic track data from the credit card
• CVV or CVV2 – 3 or 4 digit number from the back of the card
• PIN and PIN Block – the pin number or pin block from the PIN Pad
• Cardholder data

Cardholder data requires encryption

• System Five uses AES256 encryption
• Credit Card PAN (primary access number)
• Expiry date
• Card holder name
• Also user passwords must be encrypted.