14 © Hypercom EMEA Ltd. 2011 Important information
4. Develop secure payment applications
The Hypercom terminal and its software applications have been de-
signed in line with PCI DSS and Industry best practices. You need take
no further action to ensure your PCI DSS compliant environment meet
this specific requirement.
5. Protect wireless transmissions
The Hypercom T/M4200 range does not use Wi-Fi wireless transmis-
sions. If you use Wi-Fi technology in your own network installation,
you must implement it in accordance with PCI DSS and industry best
practices.
6. Test payment applications to address vulnerabilities
Hypercom have a process to identify newly discovered security vulner-
abilities and have timely development and deployment of security
patches and upgrades. You need take no further action to ensure your
PCI DSS compliant environment meet this specific requirement.
8. Facilitate secure network implementation
The payment application operates in the T/M4200 hardware environ-
ment and does not need to log application activity.
9. Cardholder data must never be stored on a server connected to the In-
ternet
If you are using the Hypercom T/M4200 device on a Local Area Net-
work for the payment transaction interface, and you are using a local
server to store and forward the transaction data, then you must take
steps to protect the transaction data in accordance with DSS require-
ments.
10. Facilitate secure remote software updates
When your terminal needs a software update, this will be carried out
by the Hypercom software downloading system; this system ensures
that only authenticated payment software is loaded onto your termi-
nal.
11. Facilitate secure remote access to payment application
There is no remote access to the payment application.
continued...
To Next Page
Loading...