PCI DSS Compliance
Every organization dealing with payment card transactions must adhere to the Payment Card Industry–Data Security Standard (PCI DSS), the standard that calls for a broad range of security measures, but beyond the use of firewalls, intrusion protection systems and anti-virus software, the understanding of the requirements and responsibilities of the merchant can seem complicated, confusing and expensive.
But it doesn’t have to be that way. NNT makes PCI DSS compliance simple, combining Device Hardening, Event Log Management, Change and Configuration Management and File Integrity Monitoring (FIM) into one, easy-to-use solution.
Did you know? NNT is a CIS Certified Software Vendor
"PCI DSS Requirement 2.2 Develop configuration standards for all systems components...[to] address all known security vulnerabilities ...consistent with industry-accepted system hardening standards...[which] may include, but are not limited to Center for Internet Security (CIS)"
NNT Change Tracker™ de-mystifies PCI compliance and makes the process straightforward. Included as standard is a step-by-step approach to PCI compliance – starting with a Step#1 PCI Compliance template, you can report on how far adrift your servers, databases, firewalls and network devices are from being compliant, before progressing through the Step#2 and Step#3 report.
Our solution will provide:
- Fast and efficient auditing of all devices via hardening templates for all security and governance policies
- Out of the Box auditing and monitoring reports and templates, including an Advanced PCI Compliance report suitable for Level 1 Merchants and Payment Processors/Acquiring Banks
- Details of all security incidents and key events correlated and alerted
- Any breach of compliance rules reported including file integrity changes, registry, installed programs and updates, process lists and service states, security and audit policies, user account and password policies, plus any 3rd party configuration files can be monitored for changes and tracked for compliance with your build standards
- Planned vs unplanned changes detected, showing who made the change
PCI V3.2 Compliance Controls
Learn how NNT Addresses PCI V3.2 Compliance Requirements
Requirement 1 & 2: Build and Maintain a Secure Network & Systems
| PCI DSS 3.2 |
Requirement |
NNT Solution |
|
Requirement 1:
1.1, 1.2, 1.3
|
Install and maintain a firewall configuration to protect cardholder data
|
Use NNT Change Tracker to apply a configuration baseline – NNT provide CIS Benchmark Checklists to ensure the most secure and effective configuration settings are used for firewalls.
Apply File Integrity Monitoring to firewall rules and other security configuration settings for tight change management, plus collect logs from firewalls to detect security incidents in advance of any breach
|
|
Requirement 2:
2.1, 2.2, 2.3
|
Do not use vendor-supplied defaults for system passwords and other security parameters
|
Prebuilt device hardening templates derived from CIS Benchmarks are used to audit for any vulnerabilities present: database systems, servers, and network devices are then continuously monitored for any drift from the desired, hardened state
Note: CIS Benchmarks are the primary recommended source of hardening checklists and NNT Change Tracker is one of only a select few CIS Certified Vendors see http://www.newnettechnologies.com/cis-benchmark.html
|
Requirment 3 & 4: Protect Cardholder Data
| PCI DSS 3.2 |
Requirement |
NNT Solution |
|
Requirement 3:
3.5, 3.6
|
Protect stored cardholder data
|
File Integrity Monitoring technology ensures access to Cryptographic Keys is restricted, and any attempted unauthorized access is logged and alerted, including changes of accounts, privileges, and permissions
|
|
Requirement 4:
4.1
|
Encrypt transmission of cardholder data across open, public networks
|
Use Device Vulnerability Reports to pre-audit for the use of non-encrypted console access methods being enabled, thereafter monitor for any configuration change affecting the devices' hardened state
|
Requirement 5 & 6: Maintain a Vulnerability Management Program
| PCI DSS 3.2 |
Requirement |
NNT Solution |
|
Requirement 5:
5.2
|
Use and regularly update anti-virus software or programs
|
NNT Change Tracker will check that AV services are activated and running, Log Tracker will alert on all significant AV events
|
|
Requirement 6:
6.1, 6.4
|
Develop and maintain secure systems and applications
|
Change Tracker will maintain host and application security settings, even for bespoke applications, and record all software and patch updates. Log Tracker will provide a complete audit trail of application and host access attempts.
|
Requirement 7 & 8: Implement Strong Access Control Measures
| PCI DSS 3.2 |
Requirement |
NNT Solution |
|
Requirement 7:
7.1, 7.2
|
Restrict access to cardholder data by business need to know
|
At all times, NNT Log Tracker will provide a 'checks and balances' audit trail of all account and privilege changes
|
|
Requirement 8:
8.1, 8.2, 8.5,
|
Assign a unique ID to each person with computer access
|
Initial hardening audit will verify correct password and authentication policies are in use, with all subsequent account and privilege changes audited
|
Requirement 10 & 11: Regularly Monitor and Test Networks
| PCI DSS 3.2 |
Requirement |
NNT Solution |
|
Requirement 10: 10.1, 10.2, 10.3, 10.5, 10.6, 10.7
|
Track and monitor all access to network resources and cardholder data
|
Audit trails are constructed automatically using predefined Log Tracker templates for PCI DSS V3.1, including default alerts for security threats
|
|
Requirement 11: 11.1, 11.4, 11.5
|
Regularly test security systems and processes
|
File Integrity Monitoring across all platforms and devices is an essential defense against malware and any 'inside man' threat to card and customer data - built-in templates for PCI DSS V3.1 are provided and can be customised, leveraging CIS Benchmark checklists to highlight system vulnerabilities. NNT Change Tracker shows 'who made the change' with continuous and real-time detection of any changes
|
Requirement 12: Maintain an Information Security Policy
| PCI DSS 3.2 |
Requirement |
NNT Solution |
|
Requirement 12: 12.2, 12.3, 12.5, 12.9
|
Maintain a policy that addresses information security for all personel
|
Security Management procedures can be automated and audited using built-in intelligent alerting and reporting
|
NO WONDER SECURE COMPUTING MAGAZINE RECENTLY AWARDED NNT CHANGE TRACKER THEIR HIGHEST AWARD OF 5 STARS FOR ‘FEATURES, EASE OF USE, PERFORMANCE AND VALUE FOR THE MONEY’.
PCI DSS Reports
“The PCI DSS is a multifaceted security standard that includes requirements for security management, policies, procedures, network architecture, software design and other critical protective measures. This comprehensive standard is intended to help organizations proactively protect customer account data”
source https://www.pcisecuritystandards.org/security_standards/documents.php
