PCI DSS & PA DSS

S4 rapidly identifies threats against cardholder data


Compliance requirement

s4 control

 
checklist (1).png

Penetration Testing

Implement additional security features for any insecure, required services (PCI DSS 2.2.3)

tick (1).png

Performs Penetration Testing

S4 uses smart fuzzing to perform automated penetration testing

 
medal.png

Compliance Demonstration

Ensure security policies are documented, in use, and known to all affected parties (PCI DSS 2.5)

tick (1).png

Provides Comprehensive Overview

S4 security checks can be used to demonstrate data protection compliance

 
login.png

User Accounts

Shared hosting providers must protect each entity’s cardholder data (PCI DSS 2.6)

tick (1).png

Examines Account Configurations

S4 identifies duplicate user accounts and other security configurations (password policies, etc.)

 
loupe (1).png

Access Control

Do not store the full contents of any track after authorization (PCI DSS 3.2.1)

tick (1).png

Audits Data Access

S4 can audit access to cardholder data in Salesforce

 
transmission-tower (1).png

Transmission Security

Ensure wireless networks transmitting cardholder data use industry best practices (PCI DSS 4.1.1)

tick (1).png

Audits Transmission Settings

S4 audits transmission settings on integrations and seeks out areas of concern

 
gears.png

Secure Development and Maintenance

Establish a process to identify vulnerabilities using reputable outside sources (PCI DSS 6.1)

tick (1).png

Identifies Security Vulnerabilities

S4 identifies vulnerabilities to cardholder data and uses code auditing and scanning

 
 
 
isv.png