What Secure SLC v2.0 Means for Teams Using AI Coding Tools

Keep your release checks and decide what the coding tool can access

443 Labs Security Team4 min read
In this article

A developer uses an AI assistant to change how the payment application retries a refund. The tests pass. Before you merge it, ask what happens if the payment provider accepts the refund and the response never reaches the application. Could the customer get two refunds?

Your usual release checks should catch that problem, whether a developer or an assistant wrote the code. Check the tool separately: what could it read or do while it made the change? Set those boundaries before anyone turns it on.

What changed in Secure SLC v2.0

The PCI Security Standards Council released version 2.0 of its Secure Software Lifecycle Standard, or Secure SLC, on 28 September 2026. It is aimed at software vendors that build software commonly used in payment environments. The Council’s announcement says v2.0 adds material on digital tools, including how vendors account for AI in their development processes.

Secure SLC is part of the PCI Software Security Framework. It concerns how a vendor develops and maintains software. The separate Secure Software Standard concerns the software being assessed. PCI SSC says assessment against either standard does not require assessment against the other. If you are planning a validation, use the final standard and programme material to check what applies to your team. The engineering practices here are a starting point for reviewing your own workflow.

Decide what the tool can see and do

Start with an ordinary development task. An assistant that suggests a test for a refund function may need the relevant code and a description of the expected behaviour. It does not need live payment records, production credentials or permission to deploy. If it can open pull requests, decide which repositories it may work in and keep the rules that govern merging in place.

Tell developers which tools they can use and which files they can share with them. An assistant that suggests the next line in an editor needs different permissions from one that can run commands or change files on its own. Check what the tool can read in that environment and what it sends outside it.

GitHub’s own guidance says its AI code review should supplement human review. A second automated opinion may help you spot an issue. The person accepting the change still needs to understand what will happen in the payment flow.

A refund change with a green test suite

In an r/devops discussion, a contributor described using the same checks for AI-assisted and manually written code: unit tests, a development deployment, integration tests and human review. A reply asked what happens when the tool writes the tests too. The usual pipeline is a good place to review the change, provided someone checks the tests against the payment rule.

Consider the refund again. In this illustrative example, the first test only checks that a request is retried after a timeout. It never accounts for the provider having accepted the first request. A reviewer can start from the approved business rule: one approved refund request should result in at most one refund. In a test environment using fake transactions, the team checks the outcome when a response is lost, then checks the records that finance uses to reconcile refunds. Checking the number of refunds and the reconciliation record tells the reviewer more than seeing a retry succeed.

NIST’s Secure Software Development Framework covers both reviewing code and testing the software it produces. A study by researchers including Neil Perry also found that participants with access to an older coding assistant produced less secure submissions on its tasks. Most participants were university students, so it does not tell us how often today’s tools cause problems in payment teams. It does give a reason to ask for evidence from your own workflow before trusting a smooth-looking change.

Keep proof in the normal release record

For that refund change, the pull request can carry the payment rule, the test cases and the reviewer’s decision. The tool policy can sit alongside the team’s existing development rules, with an owner for changes to access. If the assistant is later allowed to make changes in another repository or run a new kind of task, review that access before enabling it.

Try this on one payment flow. Write down an outcome that has to hold even when something fails, then ask a reviewer to show which test checks it. Keep that test and the reviewer’s decision with the change.

Related 443 Labs guides

Ask 443 Labs to help review how your payment software team controls development tools, reviews changes and keeps release evidence.

Get in Touch

Sources