PCI Software Security Framework
PCI Secure Software and Secure Software Lifecycle standards
Check whether the payment software, the vendor’s lifecycle, or both need security validation.
Who it applies to
Software vendors and assessors evaluating payment software or related lifecycle practices under the PCI Software Security Framework.
What you’ll produce
The relevant product validation or vendor qualification and listing when program conditions are met.
A software validation does not cover a merchant’s full PCI DSS environment. Version changes can also affect how a listing or validation may be used.
Run the project
Go to the roadmapDecisions for leadership
- Who accepts proof, and what do they expect?
- Check the customer, contract or industry program for the standard version, scope, evidence or validation format and due date. Reserve testing and remediation time.
- Who will do the work and who can sign?
- Appoint a sponsor, a day-to-day lead and a named owner for every workstream. Set aside their time and decide who can approve the outcome, accept remaining risk or authorize a filing.
- Which deadlines can we promise?
- Separate fixed external dates from internal targets. Confirm dependencies such as a vendor, test lab or assessor, and approve a backup plan if their dates slip.
How to spend the first week
- Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work.
- Map one in-scope service or transaction, including providers and supporting systems. Check real evidence against the requirements and confirm whose responsibility each check is.
- Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
What to review each week
Monitor validation gaps, expired provider evidence and service changes that affect compliance.
Kickoff brief to share with your team
Fill this in with your sponsor and send it to the people who own the work.
PCI Software Security Framework kickoff brief Business reason and required outcome [Contract, obligation or approval] Scope and exclusions [Entities, systems or activities, and reasons] Fixed deadlines and internal milestones [Date, source and owner] Executive sponsor and authorized signer [Names] Project lead and backup [Names] First workstream Choose the scheme and scope · Payment product lead + qualified assessor [Name and due date] People, effort and external costs [Estimate, owner and contingency] Evidence folder and reviewer access [Location, access owner and review date] Decisions and blockers [Item, options, owner and decision date] First week 1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work. 2. Map one in-scope service or transaction, including providers and supporting systems. Check real evidence against the requirements and confirm whose responsibility each check is. 3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
How to hand off evidence
- Record the requirement or claim, the person responsible, the period and the result. Link to the original report, configuration, test or case record.
- Include the version, system or product, date, and how you gathered the record. When a report covers a group of items, retain its filters and reconcile the count to the source.
- Ask the reviewer to open the evidence and reproduce the key check. Record their decision and date. Keep missing items or failures visible with an owner, a due date and a retest when needed.
- Share through the agreed channel. Keep sensitive originals in a restricted location and link any redacted copies to the corresponding originals.
How this works in practice
Two questions to check scope
- Is the request for the specific payment software product, the vendor’s lifecycle practices or both?
- Which product versions and deployment model will customers rely on?
Worked scenario
A payment software vendor rewrites its transaction component. It checks what assessment or validation maintenance applies before updating customer-facing claims and saves evidence showing how code changes were tested.
What to read next
- PCI DSS
Confirm the separate responsibilities for merchants and service providers operating card data environments.
- 01Choose the scheme and scopePayment product lead + qualified assessor · ~21 days
- 02Map product and lifecycle controlsSecure development + application security · ~42 days
- 03Collect evidence and support assessmentDevelopers + assessor · ~42 days
- 04Track versions and listing commitmentsRelease lead + compliance · ~21 days
Step by step
Checklist, instructions and 11 templates.
View plan as a table
| Step | Owner | When to act | Estimated target | Deliverables | Status |
|---|---|---|---|---|---|
| Choose the scheme and scope | Payment product lead + qualified assessor | Before collecting evidence | Set a start date | Coverage memo; System boundary | Open |
| Map product and lifecycle controls | Secure development + application security | Before fieldwork | Set a start date | Data-flow diagram; Control matrix; Testing matrix | Open |
| Collect evidence and support assessment | Developers + assessor | During the assessment | Set a start date | Assessment evidence; Remediation tracker; Submission package | Open |
| Track versions and listing commitments | Release lead + compliance | At releases and on the program cadence | Set a start date | Change log; Decision and listing details; Renewal calendar | Open |
Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.
- 01
Choose the scheme and scope
Check product eligibility, software versions and vendor objectives. Confirm the applicable standard version and assessment route.
What to produce
Coverage memoMemo
Gather first
- Service inventory and architecture
- Customer commitments and contracts
- Applicable criteria or legal text
How to prepare it
- Write the exact decision this memo supports. Name the legal entity, service, environments and dates. Attach a boundary diagram and state which people, vendors and processes can affect the scope.
- List the exclusions next to the inclusion list. Give a reason for each one and describe any shared service that crosses the boundary.
- Review the draft with service owners and the person making the decision. Freeze the approved version and add a review date or trigger for changes.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Decision
- Cover the hosted billing service for the April to June review.
- In scope
- Production billing API, hosting, releases and production access.
- Excluded and why
- Internal HR tool. It has no access to billing systems or data.
- Dependencies
- Cloud hosting and corporate identity provider.
- Approval
- Service owner approves after checking the architecture and contract.
Check before handing it over
A reviewer can use the memo to classify a named system and see how shared dependencies are handled.
Give the approved scope and any open questions to whoever will map requirements, select samples or review the engagement.
System boundaryMemo
Gather first
- Service inventory and architecture
- Customer commitments and contracts
- Applicable criteria or legal text
How to prepare it
- Write the exact decision this memo supports. Name the legal entity, service, environments and dates. Attach a boundary diagram and state which people, vendors and processes can affect the scope.
- List the exclusions next to the inclusion list. Give a reason for each one and describe any shared service that crosses the boundary.
- Review the draft with service owners and the person making the decision. Freeze the approved version and add a review date or trigger for changes.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Decision
- Cover the hosted billing service for the April to June review.
- In scope
- Production billing API, hosting, releases and production access.
- Excluded and why
- Internal HR tool. It has no access to billing systems or data.
- Dependencies
- Cloud hosting and corporate identity provider.
- Approval
- Service owner approves after checking the architecture and contract.
Check before handing it over
A reviewer can use the memo to classify a named system and see how shared dependencies are handled.
Give the approved scope and any open questions to whoever will map requirements, select samples or review the engagement.
- 02
Map product and lifecycle controls
Trace data flow, threat analysis, build protection, software integrity, access and release controls to the applicable criteria.
What to produce
Data-flow diagramDiagram worksheet
Gather first
- System and vendor inventory
- Examples of live transactions or data events
- Approved boundaries and information categories
How to prepare it
- Sketch an entry point, storage location, processing system and recipient for each flow. Label arrows with what moves and in which direction.
- Show trust boundaries, geographic locations, contracts or interconnections that matter. Include administrative access, backups and deletion paths where relevant.
- Walk through a real end-to-end transaction with engineering and operations. Save an accessible diagram and keep the reviewed flow register beside it.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Source
- Web checkout
- Destination
- Billing API in EU region
- Data and purpose
- Order reference and billing email to send the receipt
- Protocol and boundary
- HTTPS, crosses from public network into hosted production
- Owner and validation
- Billing owner, validated against request logs on 2026-11-12
Check before handing it over
An engineer can trace collection to deletion, and a reviewer can see every crossing or third-party handoff.
Use the worksheet to design the diagram. Share the diagram with the people confirming scope, transfers or controls.
Control matrixSpreadsheet
Gather first
- Applicable criteria, requirements or risk decisions
- Current procedures and configurations
- Names of people operating or reviewing each control
How to prepare it
- Give each requirement and implemented control an ID. Write a short control statement naming who does what, when and in which system.
- Record the evidence the control produces and how it could be tested. For a shared or inherited control, state who owns each part.
- Walk through one control with its operator. Check a real recent run, record gaps and obtain approval for exclusions or alternate controls.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Requirement
- Production access is reviewed periodically.
- Control ID
- AC-04
- Control activity
- IAM team exports administrator roles every quarter. System owners approve or revoke each assignment.
- Owner and frequency
- IAM lead, quarterly
- Evidence
- Export with filters, annotated review and removal tickets
- Test and status
- Reconcile export to current roles. Inspect approvals. Operating.
Check before handing it over
A different person can operate the control or test it using the matrix and its evidence links.
Give the baseline to control owners and the assessor before walkthroughs or sampling.
Testing matrixSpreadsheet
Gather first
- Product claims and risk file
- Applicable standards, study design and acceptance evidence
- Design configuration and test facilities
How to prepare it
- Trace each claim and risk control to a test objective and acceptance criterion. Specify units, sample rationale, version and worst-case configurations.
- Write the method and expected evidence before testing. Assign approvals and record protocol deviations and their effects.
- Compare results to the criteria. Keep failed cases, raw data and rationale for repeat testing. Link the approved reports back to the requirements.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Requirement or claim
- Battery alert appears before the device can no longer capture readings.
- Protocol and design
- TR-014, test the production hardware and locked firmware at worst-case temperature.
- Acceptance criteria
- Use the limits approved in the design input before testing.
- Sample and method
- Record sample sizes, lot IDs, conditions and operator.
- Result and evidence
- Link signed protocol, raw output and approved report.
Check before handing it over
Every essential claim and risk control has evidence or a documented justification for the gap.
Give the approved protocol to the testing team and the traceability matrix to the submission owner.
- 03
Collect evidence and support assessment
Provide reproducible test records, versioned artifacts and supplier details. Resolve findings and follow the official report and listing process.
What to produce
Assessment evidenceSpreadsheet
Gather first
- Control descriptions and test request
- Source system records
- Defined period and evidence access rules
How to prepare it
- Create a register keyed by control, requirement or request. Export native records with the filters, timestamps and operator details needed to interpret them.
- Link to a restricted copy of each artifact. Note time zone, scope, date range, export method and whether the evidence shows design or actual operation.
- Test the links using the reviewer’s permissions. Flag missing periods or evidence and track a follow-up instead of filling in records retrospectively.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Evidence ID
- EV-021
- Control or request
- AC-04, October administrator review
- Period and scope
- 1 to 31 Oct 2026 UTC, production tenant
- Source and capture
- IAM export filtered to active elevated roles
- Link or record ID
- Restricted workpaper EV-021 plus ticket IAM-114
- Reviewer and status
- Security assurance, verified
Check before handing it over
A reviewer can open the right file, reproduce the population filter and see who performed or approved the real task.
Send the index and access instructions to the assessor. Keep sensitive files in the approved evidence store.
Remediation trackerSpreadsheet
Gather first
- Finding, risk or test exception
- Root-cause analysis
- Named owner, due date and expected evidence
How to prepare it
- Record the observation and link the exact test or requirement. Describe the business effect and investigate why the issue was able to happen.
- Separate immediate containment from the permanent fix. Give each action an owner, date, verification method and any required approval for deferral.
- Retest against the original failure once the fix is live. Record who accepted the outcome and keep unresolved issues visible.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Finding or risk
- F-008, a departed contractor retained production access
- Cause and effect
- HR event never reached IAM. Admin access remained active.
- Action and owner
- Revoke access and alert on failed HR sync. IAM lead.
- Due and status
- 2026-11-28, in progress
- Closure test
- Simulate departure and verify access disappears within policy
- Approver and evidence
- Risk owner, ticket IAM-114 and retest results
Check before handing it over
The closure test addresses the original problem and has a dated result from an independent reviewer where required.
Send open items and decisions to governance, audit or the assessor on the applicable cadence.
Submission packageMemo
Gather first
- Current authority instructions or package list
- Approved source records and evidence
- Submission owner and intended review route
How to prepare it
- Download the current instructions and confirm the required format and version. Create an index that maps every required document or answer to a file and owner.
- Cross-check names, version numbers and scope across the package. Check file size, required signatures, redactions and all attachment references against the actual portal requirements.
- Have a second person run a completeness check. Save a read-only copy of the submitted version, receipt, and follow-up owner.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Package section
- Evidence and supporting technical records
- Requirement and source
- Authority package checklist, current release
- Artifact and version
- Test report TR-017 v2, approved
- Responsible person
- Submission coordinator with technical reviewer
- Submission and receipt
- Record the official filing ID and date after upload
Check before handing it over
The submitted package can be recreated from the index and the receipt is linked to the exact files.
Send the approved package through the official channel. Treat the download as an index, and use issuer forms where required.
- 04
Track versions and listing commitments
Confirm maintenance requirements, approve claims for the actual scope and document how changes and vulnerabilities affect the validated version.
What to produce
Change logSpreadsheet
Gather first
- Case, change or communication records
- Required fields and timing
- Named case owner and authorized recipients
How to prepare it
- Give each event a record ID. Record the action or request, receipt or send time, owner and the deadline or next date.
- Write the decision and link the response or supporting record. Track delivery, escalation or verification separately so a sent message is distinguishable from an accepted one.
- Review open rows on a regular cadence. Restrict personal details to the case system and keep the register to IDs and necessary dates.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Record ID
- REQ-022
- Event and date
- Verified access request received 2026-11-07 UTC
- Owner and target
- Privacy operations, internal review by 2026-11-23
- Decision and status
- Approved response, sent securely
- Completion evidence
- Case delivery record, 2026-11-24
- Follow-up
- None, approved by the reviewer
Check before handing it over
Every open item has a next action and closed items have a verifiable record of closure or delivery.
Use the log at case reviews and provide a restricted copy only where the engagement requires it.
Decision and listing detailsIssuer document
Gather first
- Correct portal or issuer contact
- Approved scope and submission record
- File access and sharing requirements
How to prepare it
- Confirm which issuer or portal supplies this record and who can retrieve it. Gather the submission reference, holder name, scope and expected date.
- When the document arrives, verify recipient, scope, dates, version, conditions and any required verification link. Escalate discrepancies to the issuer.
- Save the original in the approved location. Record renewal or response actions and limit distribution to authorized recipients.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Document expected
- Issuer’s final decision or confirmation
- Reference
- Official portal or case ID
- Received and verified by
- Compliance coordinator, 2026-11-10
- Scope and conditions
- Matches the agreed service boundary and version. Follow-up recorded separately.
- Location and access
- Restricted evidence folder, named reviewers only
Check before handing it over
The original can be traced to the issuer and its scope and date match the engagement or application.
Send the verified record or approved summary to decision makers. The download is a tracking sheet for the original document.
Renewal calendarSpreadsheet
Gather first
- Current obligations, expiry dates or audit window
- Delivery dependencies and owner availability
- Official rules or engagement confirmation
How to prepare it
- Separate official due dates, trigger-based clocks and team target dates. Write down the event or rule that starts each clock.
- Work backward from each milestone. Include lead time for review and submission, and name the owner and backup.
- Cross-check the dates with the source or reviewer and make reminders actionable. Record the next verification point for changing rules.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Milestone
- Quarterly access review approved
- Date and kind
- 2026-12-18, internal target
- Trigger or source
- Internal access control schedule v3
- Prerequisite
- Access export by 2026-12-09
- Owner and reminder
- IAM lead, remind one week before
- Status
- Scheduled
Check before handing it over
Every external deadline links to a real source. Planning targets are visibly marked.
Add approved dates to the team calendar and share them with the people scheduled to deliver or review.
Official sources
- PCI SSC · Standards library (opens in a new tab)
- PCI SSC · Secure Software Lifecycle (opens in a new tab)
- PCI SSC · Software Security Framework v2 FAQ (opens in a new tab)