|
Data Security
 The
Payment Card Industry (PCI) Data Security Standard was created
by major credit card companies to safeguard consumer information. Visa, MasterCard, American Express, and other
credit card associations mandate that merchants and service
providers who accept credit cards meet certain minimum standards of security when they
store, process and transmit cardholder data.
It is the customer's responsibility to comply with the PCI laws;
however, Abacus feels that it should be proactive in helping its
customers meet these new, more stringent standards.
PCI compliance depends on three components:
»
Software Version
»
Settings within the software
»
Infrastructure and security of the network
Verify
that your software version and software settings are PCI DSS
compliant. Please remember the infrastructure and security of
your network is your responsibility, but Abacus can also provide
services to assist you with the security of your network if you
would like.
Secure Network
1- Install and maintain firewall
2- Remove Default accounts
|
Protect Cardholder Data
3- Protect stored data
4- Encrypt transmission on open networks
|
Vulnerability Management
5- Use up-to-date Antivirus
6- Maintain secure systems
|
Strong Access Controls
7- Restrict access to need-to-know basis
8- Assign unique identification
9- Restrict physical access
|
Monitor and Test Networks
10- Track and monitor access
11- Regularly test systems
|
Security Policies
12 - Maintain information security policy for all personnel
|
PCI DSS
Compliant Versions
These versions have been validated as
conforming to the PA DSS requirements.
POS version
number: |
Validated against
PABP/PA DSS
version:
|
Deployment notes:
|
Current
validation
expires on: |
Aloha v7.0
|
PA DSS v2.0
|
Acceptable for new
deployments *General release targeted Q3/Q4 2012*
|
October
28, 2016
|
Aloha
v6.7
|
PA
DSS v1.2.7.0
|
Acceptable
for new deployments
|
October
28, 2013
|
Aloha
v6.5
|
PABP
v1.2
|
Acceptable
for new deployments
|
October
28, 2013
|
Aloha
v6.4
|
PA
DSS v1.2
|
Acceptable
for new deployments
|
October
28, 2013
|
Aloha
v6.2
|
PABP
v1.4
|
Not
recommended for new deployments
|
December
2, 2010
|
Aloha
v6.1
|
PABP
v1.3
|
Not
recommended for new deployments
|
June
2, 2010
|
Version
Expiration
Check to see if your
software is up to date or about to expire.
Here's why you should
upgrade.
Radiant expects these versions to appear on the list of
validated payment applications published by the Payment Card
Industry Security Standards Council (PCS SSC) in late June or
early July.
Abacus strongly encourages customers to adopt the most recent
market ready Aloha releases as they become available.
If your version is no longer PCI DSS compliant, Abacus strongly
recommends that you call us at (727) 524-017 to assist you in upgrading your version of
Aloha.
To
contact us please email DataSecurity@abacuspos.com,
or to leave a message call 727-524-0177 ext.430 and
a representative will call you back within 24 hours.
Abacus. You can count on us.
|
