PCI DSS compliance requires any organization that handles credit cardholder data to implement certain technical, administrative and physical security services. The following PCI compliant services can be used to strengthen the security framework of your systems and minimize your overall risk of data loss.
Need PCI hosting services, or have questions? Request a quote, contact or chat with us now.
All of these components are required to meet PCI DSS compliance:
|
PCI Requirements |
PCI Compliant Services |
|
10.6: Review logs for all system components at least daily. 10.3: Record at least the following audit trail entries for all system components for each event - including user ID, type of event, data and time, success or failure indication, etc. 10.7: Retain audit trail history for at least one year, with a min. of three months immediately available for analysis (online, archived, or restorable from back-up). |
Monitoring and analyzing user and system activity can help detect patterns of normal use and potentially malicious users. Daily log review is the process of regularly reviewing and reporting on log activity. While some providers may offer logging (tracking user activity, transporting and storing log events), Online Tech provides the complete logging experience with daily log review, analysis, and monthly reporting. |
|
10.5.5: Use file-integrity monitoring or change-detection software on logs to ensure that existing log data cannot be changed without generating alerts. 11: Deploy file integrity monitoring tools to alert personnel to unauthorized modification of critical system files, configuration files or content files. Configure the software to perform critical file comparisons at least weekly. |
|
|
6.6: For public-facing web applications, ensure: Verify that public-facing web applications are reviewed (using either manual or automated vulnerability security assessment tools or methods), as follows:
Verify that a web-application firewall is in front of public-facing web applications to detect and prevent web-based attacks. |
|
|
8.3: Incorporate two-factor authentication for remote access (network-level access originating from outside the network) to the network by employees, administrators, and third parties. (For example, remote authentication and dial-in service (RADIUS) with tokens; or other technologies that facilitate two-factor authentication. |
|
| 11.2: Run internal and external network vulnerability scans at least quarterly and after any significant change in the network (such as new system component installations, changes in network topology, firewall rule modifications, product upgrades). |
|
| 6.1: Ensure that all system components and software are protected from known vulnerabilities by having the latest vendor-supplied security patches installed. Install critical security patches within one month of release. |
|
|
5.1: Deploy anti-virus software on all 5.2: Ensure that all anti-virus mechanisms |
|
|
4.1: Use strong cryptography and security |
|














