Document Comparison
Secure-Software-Program-Guide-v1.pdf
→
Secure-Software-Program-Guide-v1.0.1.pdf
98% similar
46 → 46
Pages
13944 → 13993
Words
6
Content Changes
Content Changes
6 content changes. 37 administrative changes (dates, page numbers) hidden.
Added
p. 2
July 2020 1.0.1 Aligned language (regarding use of wildcards) in Appendix B "Payments Software Versioning Methodology" and section 3.1 "Vendors" with language in the Secure Software Report on Validation (ROV) report template.
Modified
p. 8
• Providing their customers (directly or indirectly through their integrators and resellers) with a copy of the applicable Security Guidance. This includes applicable mapping of internally used version numbers to those that have been published (including but not limited to use of wildcards) on the Website, and any subsequent updates to the Security Guidance that may result from changes to the Validated Payment Software over time;
• Providing their customers (directly or indirectly through their integrators and resellers) with a copy of the applicable Security Guidance. This includes applicable mapping of internally used version numbers to those that have been published on the Website, and any subsequent updates to the Security Guidance that may result from changes to the Validated Payment Software over time;
Modified
p. 30
• Secure Software Implementation Guidance
• Vendor Release Agreement (one per Vendor) *
• Vendor Release Agreement (one per Vendor) *
• Secure Software Implementation Guidance
• Vendor Release Agreement (one per Vendor) * • Fee*
• Vendor Release Agreement (one per Vendor) * • Fee*
Removed
p. 42
• The definition of elements that indicate any use of wildcards
Modified
p. 42
• The specific details of how wildcards are used in the versioning methodology B.2 Version Number Usage All changes to a given Validated Payment Software product or application must result in a new Payment Software version number. However, whether this affects the version number listed on the Website depends on the nature of the change and the Vendor’s published versioning methodology. All changes that impact security functionality and/or any Secure Software Requirement must result in a change to the version …
• Type of change: High, Low, Admin B.2 Version Number Usage All changes to a given Validated Payment Software product or application must result in a new Payment Software version number. However, whether this affects the version number listed on the Website depends on the nature of the change and the Vendor’s published versioning methodology. All changes that impact security functionality and/or any Secure Software Requirement must result in a change to the version number listed on the Website; use …
Modified
p. 42
• Types of changes made to the Payment Software
•e.g., major release, minor release, maintenance release,wildcard, etc.
•e.g., major release, minor release, maintenance release,
• Types of changes made to the Payment Software
•e.g., major release, minor release, maintenance release, etc.
•e.g., major release, minor release, maintenance release, etc.