PCI DSS and SAD Standards
As an IT professional or MSP, are you able to follow PCI SAD privacy compliances? In accordance to the Payment Card Industry Data Security Standard (DSS), merchants are strongly encouraged not to store cardholder information after authentication — so it's important to make sure that your clients' systems strictly abide by these security compliances for the credibility of their businesses and customers.
Remote management software from SolarWinds MSP (formerly LOGICnow) highlights the importance of security to your customers, which is why our security features exceed the privacy compliances of PCI DSS.
What Does SAD Mean in Accordance with PCI DSS?
Sensitive Authentication Data (SAD) is the information on a card used for authentication at the time of a purchase. This includes data from:
- Full magnetic strip
- Card security code (CSC, CVV2, CID, CAV2)
- PIN and/or PIN block
While this information is necessary when making a purchase by card, the merchant must comply with the PCI DSS standards and remove this information from the merchant's system. SAD cannot even be stored in any encrypted format; it must be deleted as soon as the purchase has been made.
These standards were set to reduce the risk of theft or fraud on an individual's credit card transaction.
Exceed PCI DSS Compliance Standards with SolarWinds MSP
While SolarWinds MSP solutions do not feature payment methods, our superior security software protects sensitive user data as it is stored and transferred between servers. In exceeding PCI DSS compliance, we surpass formal security compliances by:
- Encrypting all data shared between customers and SolarWinds MSP solutions
- Requiring a unique user ID and password in order to access systems
- Enabling two-factor authentication and IP whitelisting
- Logging all application activity to provide an audit trail
- Logging out all accounts with idle dashboards
Start a risk-free, 30-day trial of our software today to see how our security standards will benefit you and your clients today!