PCI SSS

PCI SSS is the revised version for the previous PA DSS standard The new standard is coupled with PCI SLC to form PCI SSF altogether. The standard applies to the security characteristics, controls,features, and functionalities that payment software must possess and maintain throughout its lifecycle.

Secure Software Standards consist of two parts,

  • Secure Software Core Requirements

  • Module A Account Data Protection.


The standard focuses on ensuring that applications are maintained in a manner that protects payment transactions and data, minimizing the vulnerabilities, and defending itself from any security attacks.

Validation against PCI SSS helps assure that Payment Software is developed with security to protect the integrity of the software and the confidentiality of sensitive data it captures, stores, processes, and transmits. Adhering to PCI SSS will ease the organization to verify the software is properly configured and meets applicable PCI DSS requirements.

What We Offer

The key to implementing robust security controls lies in identifying the right scope, recognizing the difference between compliance and security and in sustaining compliance after successful control implementation.

Business Understanding

Evaluating business process and environment to understand the in-scope elements

Scope Finalization

Finalize the scope elements and prepare the requirement documentation

Readiness Assessment

Identify the potential challenges that might arise during requirement implementation

Risk Assessment

Identifying and analyzing the risks in the information security posture.

Secure Code Review

Conduct code review with automated & manual approach to identify system vulnerabilities

PCI SSS Documentation Support

Assist you with list of policy and procedure to help you in validation or evidence collection

Remediation Support

Support you by recommending solutions to compliance challenges

Awareness Training

Conduct awareness sessions for your Team and personnel involved in the scope

Scans And Testing

Identify critical vulnerabilities in your system with a robust testing approach

Evidence Review

Review of the evidence collected to assess their maturity, in line with the compliance

Final Assessment and Attestation

Post successful assessment, we get you attested for compliance with our audit team

Continuous Compliance Support

Support you in maintaining compliance by providing guidelines

frequently asked questions

The Secure Software Standard is intended for payment software/applications that are sold, distributed, or licensed to third parties. This includes payment software intended to be installed on customer systems as well as payment software deployed to customers ”as a service” over the Internet.

The exceptions to Secure Software Standard, include the applications developed in-house for the sole use of the company that developed the software. Also, the softwares that are developed and sold to a single customer for the sole use of that customer fall in the exception.

Payment software validations for PCI Secure Software Standard have a three-year expiration. For more information on revalidations and the process for managing changes, details can be found here . 
https://www.pcisecuritystandards.org/documents/Secure-Software-Program-Guide-v1.pdf

Alert boxes are used quite often to stand out the information that requires immediate attention of the end users such as warning, error or confirmation messages.
Alert boxes are used quite often to stand out the information that requires immediate attention of the end users such as warning, error or confirmation messages.
Alert boxes are used quite often to stand out the information that requires immediate attention of the end users such as warning, error or confirmation messages.

A Validation or qualification under the PCI Software Security Framework does not imply or result in validation to any other PCI standard. However, elements of other PCI standards and programs may be incorporated under the PCI Software Security Framework at some point in the future. If and when that will occur will be communicated well in advance of any transition from an existing or future standard or program to the PCI Software Security Framework.

A PA-DSS validated applications are moved to the “Acceptable Only for Pre-Existing Deployment” when the validation expires. For applications validated to PA-DSS version 3.2 this will occur at the end of October 2022 and the PA-DSS program will close. See FAQ 1195 for further information about applications listed as “Acceptable Only for Pre-Existing Deployment”

Related Updates




LinkedIn Facebook Twitter Youtube

We use cookies to enhance your user experience. By continuing to browse, you hereby agree to the use of cookies. To know more; visit our Privacy Policy & Cookies Policy.

X