Open-source code runs inside almost every payment app, gateway and bank system. This tracker lists the open-source and software supply-chain rules that payment, compliance and testing teams need to meet, with the opportunity in each. Verified facts only, each linked to its source.
Last updated: Wednesday, November 18, 2026 · Checked monthly against official sources. Items leave the tracker a few months after they take effect.
FILTER BY REGION
FILTER BY ECOSYSTEM OR LIBRARY
FILTER BY STATUS
| Region | Rule or change | What it means | Opportunity | Key date |
|---|---|---|---|---|
| Global PyPI (Python) |
PyPI shows package provenance and warns when it is missing Our guide → · Source: PyPI |
Each release shows whether its files carry attestations. Dropping them is now visible to users. | Publish with Trusted Publishing; check provenance before approving Python dependencies. | Nov 6, 2026 Just started |
| Global NuGet (.NET) |
.NET 8 and .NET 9 support has ended Our guide → · Source: Microsoft .NET Blog |
Both versions stopped getting security fixes on this date. .NET 10 LTS is supported to November 2028. | Move payment services and their NuGet packages to .NET 10; record any exceptions for audit. | Nov 10, 2026 Just started |
| Global PostgreSQL |
PostgreSQL 14 reaches end of life Our guide → · Source: PostgreSQL |
Release 14.25 was the last one; version 14 gets no further security or bug fixes. | Upgrade payment databases to PostgreSQL 17 or 18 and retest replication and backups. | Nov 12, 2026 Just started |
| Global Linux base images |
OpenSSH login-bypass flaw on Linux actively exploited Our guide → · Source: The Hacker News |
CISA listed CVE-2026-123158 as exploited; attackers can skip SSH authentication on affected Linux servers. | Patch OpenSSH on payment hosts and images, then review SSH keys and access logs. | KEV due Nov 12, 2026 Just started |
| European Union | New Product Liability Directive covers software Our guide → · Source: CMS |
Software is a product; open source you build into a commercial product is in scope. | Open-source inventories, patch evidence and supplier terms that manage liability. | Dec 9, 2026 Deadline soon |
| Global Spring Boot |
Spring Boot 4.0 free support ends Our guide → · Source: Spring |
No more free security patches for 4.0 after this date. Spring Boot 3.5 free support ended June 30, 2026. | Move payment services to Spring Boot 4.1 or newer, or buy commercial support. | Dec 31, 2026 Deadline soon |
| Global Apache Tomcat |
Tomcat 9.0 support ends Our guide → · Source: Apache Tomcat |
No more 9.0 fixes after this date. A new 9.1 branch keeps Java EE apps supported to 2030. | Move payment web apps to Tomcat 10.1 or 11, or plan the 9.1 switch. | Mar 31, 2027 Upcoming |
| Global Node.js |
Node.js moves to one major release a year Our guide → · Source: Node.js |
Starting with Node.js 27, one release each April becomes LTS in October. Every release now gets LTS. | Plan one yearly runtime upgrade instead of two. | Apr 2027 Upcoming |
| Global Node.js |
Node.js 22 reaches end of life Our guide → · Source: NodeSource |
No security patches after this date. Node.js 20 already lost support on Apr 30, 2026. | Move payment services to Node.js 24 or 26 now. | Apr 30, 2027 Upcoming |
| European Union | Cyber Resilience Act: full rules apply Our guide → · Source: Goodwin |
Main duties apply; open-source stewards get lighter reporting duties. | SBOM tooling and open-source due diligence for payment software sold in the EU. | Dec 11, 2027 Upcoming |
| United States | NIST SSDF v1.2 secure development update Our guide → · Source: NIST |
Draft update to the US secure software development practices; final pending. | Map build pipelines and update processes to SSDF 1.2 early. | Draft; final pending Proposed |
| Global Gradle (Java builds) |
Gradle 10 will need Java 21 Our guide → · Source: Gradle |
Gradle 9.6 already warns when the build runs on Java below 21; Gradle 10 makes it required. | Run build servers on Java 21+ and clear Gradle 10 deprecation warnings now. | Date not set Planned |
WHO OWNS THIS
Open-source compliance: roles and sign-off
Open-source rules and end-of-life dates need clear owners. The engineering lead owns each application and its components; the open-source program office and legal own licences; application security and the CISO own vulnerabilities; the product owner signs each release.
1. Roles and responsibilities
- Funds upgrades and fixes
- Accepts remaining risk in writing
- Signs each release
- Reports status to leadership
- Keeps the bill of materials (SBOM) current
- Plans end-of-life upgrades
- Fixes flaws by the due date
- Certifies no unsupported parts each quarter
- Runs scans on every build
- Rates and assigns flaws
- Reviews exceptions
- Recommends release sign-off
- Patches base images and runtimes
- Secures the build pipeline and signing
- Generates SBOMs automatically
- Keeps build evidence
- Approves new packages
- Tracks licences and provenance
- Watches ecosystem rule changes
- Leads EU CRA readiness
- Reviews licence obligations
- Advises on EU CRA and Product Liability rules
- Reviews supplier contracts
- Signs licence exceptions
- Sets fix deadlines for critical flaws
- Approves high-risk exceptions
- Leads incident response
- Reports risk to leadership
- Checks vendor SBOMs and support terms
- Tracks vendor end-of-support dates
- Reviews vendors yearly
- Plans exits
- Samples SBOMs and exceptions
- Tests patch timelines
- Reports findings
- Confirms fixes
2. Who is accountable for what (RACI)
| Activity | Product owner | Engineering lead | AppSec lead | Platform / DevOps | OSPO | Legal | CISO |
|---|---|---|---|---|---|---|---|
| Keep an SBOM for every release | I | A | C | R | C | I | I |
| Approve new open-source packages | I | R | C | I | A | C | I |
| Licence review | I | C | I | I | R | A | I |
| Patch actively exploited flaws on time | I | R | C | R | I | I | A |
| End-of-life upgrade plan | A | R | C | R | C | I | I |
| Exception for an unsupported component | R | R | C | C | C | I | A |
| Build pipeline security and package signing | I | C | R | A | I | I | C |
| EU Cyber Resilience Act and Product Liability readiness | A | C | C | I | R | R | C |
| Release sign-off | A | R | R | C | C | I | C |
A accountable (one per activity, approves) · R responsible (does the work) · C consulted · I informed. Internal audit tests independently and is not shown.
3. From review to sign-off
4. Sign-off record
One line per upgrade, exception or release. No signed line, no release.
| Item | Prepared by | Reviewed by | Signed off by | When | Evidence |
|---|---|---|---|---|---|
| Upgrade off .NET 8 and .NET 9 | Engineering lead | AppSec lead | Product owner, CISO | Plan by Dec 2026 | Upgrade plan, test results |
| OpenSSH exploited flaw on Linux images | Platform and DevOps lead | AppSec lead | CISO | Within fix deadline | Scans before and after, change ticket |
| EU Product Liability Directive review | OSPO lead | Legal | Product owner | Before Dec 9, 2026 | Gap assessment, actions |
Titles differ by firm; small teams may combine roles, but the person who builds should not be the only one who signs off. General guidance, not legal advice.
Runbook: from an open-source change to sign-off
How to handle an end-of-life, a security flaw or a supply-chain rule from this tracker. Use one runbook per item. Each phase says when, why, what, who and how, and the evidence to keep.
▸1. Plan · Decide if the item applies to you, how big the change is, and who owns it.
When: As soon as an item appears on the tracker. Target: at least 90 days before the key date (T-90). For proposed rules, inside the comment window.
Why: Late discovery is the main reason teams miss deadlines, pay fines or ship rushed changes. Early planning turns a rule into a normal roadmap item.
What: Decide if the item applies to you, how big the change is, and who owns it.
Who: Owner: Engineering lead. With: Open-source program office (policy and licences), Application security lead (risk rating), Product owner (priority).
Example: Node.js 22 end of life. Use your SBOM to find every payment service still on it.
How
- Open the official source linked in the tracker and read the actual text, not only the summary.
- Map it to your products, rails, systems, vendors and customers in scope.
- Run a short gap analysis: what we do today versus what the rule needs.
- Size the work (small, medium, large) and add it to the roadmap with a target date.
- Log risks, assumptions, issues and dependencies in the RAID log.
Evidence to keep
- Impact assessment (applies / does not apply, with reason)
- Gap analysis
- Epic or change request with owner and target date
- RAID log entry
▸2. Prepare · Turn the rule into requirements, a design, a test plan and a rollout plan.
When: T-90 to T-60 days.
Why: Clear requirements and a test plan stop rework and give auditors a straight line from the rule to the change.
What: Turn the rule into requirements, a design, a test plan and a rollout plan.
Who: Owner: Engineering lead. With: Platform and DevOps lead (images, runtimes, pipeline), Application security lead, Legal (licence questions).
Example: pick the target version, check library compatibility and plan the upgrade order.
How
- Write requirements that quote the rule clause they come from.
- Agree the design and any vendor or partner changes, with dates.
- Build a traceability matrix: rule clause, requirement, test case, evidence.
- Plan test data, environments and a rollback.
- Book change windows and tell support and operations teams.
Evidence to keep
- Requirements with rule references
- Design or configuration decision
- Traceability matrix (draft)
- Test plan and rollback plan
▸3. Execute · Build or configure, test, and release the change safely.
When: T-60 days to go-live.
Why: This is where the change is built and proven. Testing against the rule, not just the feature, is what protects you.
What: Build or configure, test, and release the change safely.
Who: Owner: Engineering lead. With: Platform and DevOps lead (builds, patches, SBOM), Application security lead (scans).
Example: upgrade, run regression and security scans, and fix breaking changes.
How
- Build or configure the change behind a flag where possible.
- Run unit, system, regression and negative tests, plus UAT with the business.
- Fix defects and re-test; keep the defect log current.
- Hold a go/no-go meeting with clear criteria.
- Release, watch live metrics and keep the rollback ready.
Evidence to keep
- Test results and defect log
- UAT sign-off
- Go/no-go record
- Change ticket and release notes
▸4. Evidence · One evidence pack that shows the rule was understood, built, tested and approved.
When: Collected all the way through; packaged by T-7 days.
Why: If it is not written down, it did not happen. Good evidence makes audits short and calm.
What: One evidence pack that shows the rule was understood, built, tested and approved.
Who: Owner: Application security lead. With: Platform and DevOps lead (SBOM and build logs), Open-source program office (package approvals, licence report).
Example: keep the SBOM before and after, scan reports and patch tickets.
How
- Create one folder per tracker item with a simple index.
- Store each document with date, version and owner.
- Complete the traceability matrix with links to every test and approval.
- Add screenshots or exports of live configuration where relevant.
- Record training or communications sent to staff and customers.
Evidence to keep
- Evidence index
- Final traceability matrix
- Configuration proof
- Training and communication records
▸5. Audit · Second line (Compliance or Risk) tests the control; Internal Audit may sample it later.
When: From T-7 days to 30 days after go-live.
Why: An independent check finds gaps before a regulator, scheme or customer does.
What: Second line (Compliance or Risk) tests the control; Internal Audit may sample it later.
Who: Owner: CISO (control check). Independent check: Internal audit.
Example: security re-checks that no service still runs the old version.
How
- Walk through the evidence pack against the rule text.
- Re-perform a sample of key tests or checks.
- Raise findings with a rating, owner and due date.
- Track findings to closure and re-test the fix.
Evidence to keep
- Control test results
- Findings log with owners and dates
- Closure evidence for each finding
▸6. Review · Post-implementation review: did it work, what broke, what we learned.
When: About 30 days after go-live.
Why: A short look back confirms the change works in real life and makes the next rule easier.
What: Post-implementation review: did it work, what broke, what we learned.
Who: Owner: Engineering lead. With: Application security lead, Open-source program office, Product owner (exceptions and next upgrade dates).
Example: watch errors and performance after the upgrade.
How
- Check live metrics: errors, rejects, exceptions, complaints, incidents.
- Confirm all findings and defects are closed or accepted.
- Note lessons learned and update this runbook if needed.
- Update the tracker status and any related guides.
Evidence to keep
- Post-implementation review notes
- Metrics snapshot
- Lessons learned
▸7. Sign-off · Named people confirm the item is done and the evidence is complete.
When: After the review, and before closing the item.
Why: Formal sign-off shows clear ownership and closes the loop for auditors.
What: Named people confirm the item is done and the evidence is complete.
Who: Owner: Product owner (approves) with the CISO. Signers in order: Engineering lead, Platform and DevOps lead, Application security lead, Open-source program office lead, Legal (licence items).
Example: sign-off includes the security or AppSec lead.
How
- Share the evidence pack and review notes with the approvers.
- Each approver confirms their part in writing, with date.
- Archive the pack in your GRC tool or records system.
- Close the epic and the RAID entries.
Evidence to keep
- Signed approvals (name, role, date)
- Archived evidence pack
- Closed epic and RAID items
Sign-off
Sign in this order: Prepared, then Reviewed, then Certified, then Approved. Each signer checks the evidence of the lines above. Close the item only when every line has a name, date and evidence link. The person who prepares cannot approve.
| # | Role | Stage | Confirms | Evidence | Name and date |
|---|---|---|---|---|---|
| 1 | Engineering lead | Prepared | SBOM current; upgrade or fix done | SBOM, change ticket | ________________ |
| 2 | Platform and DevOps lead | Reviewed | Images, runtimes and pipeline patched and signed | Build logs, image scan | ________________ |
| 3 | Application security lead | Certified | No open critical or exploited flaws, or exceptions logged with expiry | Scan report, exception log | ________________ |
| 4 | Open-source program office lead | Certified | Packages approved and licences tracked | Package approvals, licence report | ________________ |
| 5 | Legal counsel (licence or liability items) | Certified | Licence and liability duties met | Legal review | ________________ |
| 6 | CISO | Approved | Security risk acceptable; exceptions approved | Signed exception or approval | ________________ |
| 7 | Product owner | Approved | Accepts remaining risk and closes the item | Signed release approval | ________________ |
Tip: copy this runbook into your own tracker or GRC tool, one copy per rule. Dates are relative to the key date shown in the tracker (T-90 means 90 days before).
Risk and control self-assessment (RCSA): Open-source compliance
The main risks for this area, the controls that reduce them, and the risk left after those controls. 4 risks are specific to this area and 6 are shared by every tracker (C1 to C6). Owners match the roles in the Who owns this section above. Reviewed every quarter and checked by the second line. Preventive controls lower likelihood; detective and corrective controls lower impact. Read more in our RCSA guide.
10 risks assessed for this area. Controls bring every high inherent risk down to medium or low.
How to read the heat map: each dot is a risk. It starts at its inherent rating (no controls) and moves to its residual rating (after controls). Score = likelihood x impact: 1 to 6 Low, 8 to 12 Medium, 15 to 25 High. Mid-blue dots are this area; navy dots are shared risks.
QUARTERLY RCSA CYCLE
RISK AND CONTROL REGISTER
| ID | Type | Risk and cause | Control | Owner | Inherent | Residual |
|---|---|---|---|---|---|---|
| OSS-R1 | This area | Unsupported open source runs in production Cause: No list of components and versions |
SBOM and end-of-life scan every month; upgrade plan for each item Preventive · Monthly |
Engineering lead | High 16 L4 x I4 |
Medium 8 L2 x I4 Control: Partly effective |
| OSS-R2 | This area | A known flaw in a library is exploited Cause: Patches applied slowly |
Fix deadlines by severity; actively exploited flaws fixed first Preventive and corrective · Continuous |
CISO | High 15 L3 x I5 |
Medium 8 L2 x I4 Control: Effective |
| OSS-R3 | This area | Licence terms are broken in shipped software Cause: Licences not checked before release |
Licence scan on every build; approval for restricted licences Preventive · Per build |
Open-source program office lead | Medium 12 L3 x I4 |
Low 4 L1 x I4 Control: Effective |
| OSS-R4 | This area | A malicious or tampered package enters the build Cause: No provenance or signature checks |
Approved registries only, pinned versions, provenance and signature checks Preventive · Per build |
Platform and DevOps lead | High 15 L3 x I5 |
Medium 10 L2 x I5 Control: Partly effective |
| C1 | Shared | A rule change is missed Cause: No owner watches the sources; news arrives late |
Weekly tracker review; every new item gets a named owner within 5 days Preventive and detective · Weekly |
Open-source program office lead | High 20 L4 x I5 |
Medium 8 L2 x I4 Control: Effective |
| C2 | Shared | A rule is read the wrong way Cause: Summaries used instead of the rule text; no expert review |
The impact assessment is signed against the source text Preventive · Per item |
Legal counsel | High 15 L3 x I5 |
Medium 10 L2 x I5 Control: Effective |
| C3 | Shared | A deadline is missed Cause: Work starts too late; dependencies not tracked |
Planning starts at T-90; RAID log and go/no-go before release Preventive and detective · Per item |
Engineering lead | High 16 L4 x I4 |
Low 6 L2 x I3 Control: Effective |
| C4 | Shared | Testing does not cover the rule Cause: Tests check features, not rule clauses |
Traceability from each rule clause to a test, with sign-off Preventive · Per release |
Application security lead | Medium 12 L3 x I4 |
Low 4 L1 x I4 Control: Effective |
| C5 | Shared | Evidence is missing at audit time Cause: Documents spread across tools; no index |
Evidence pack with an index, checked at T-7 Preventive · Per item |
Engineering lead | Medium 9 L3 x I3 |
Low 3 L1 x I3 Control: Effective |
| C6 | Shared | Audit findings stay open Cause: No due dates or follow-up |
Findings log with owner and due date; monthly review Preventive and detective · Monthly |
CISO | Medium 9 L3 x I3 |
Low 4 L2 x I2 Control: Partly effective |
Open actions
- OSS-R1: extend the end-of-life scan to container base images. Owner: Engineering lead.
- OSS-R4: turn on provenance checks for npm and PyPI packages. Owner: Platform and DevOps lead.
- Test two controls in this area each quarter and keep the results in the evidence pack. Owner: CISO.
Quarterly attestation
Engineering lead (first line): confirm risks, controls and ratings are current. ________________
CISO (second line review): confirms the review and challenge. ________________
Product owner: accepts residual risk. ________________
This is a sample RCSA for planning and training. Adjust risks, ratings and owners to your own organisation before use. The full cross-area register is in the monthly portfolio status report.
This tracker is a summary for planning, not legal advice. Dates can change, so always check the official source before acting. The Opportunity column is our own view. Summaries are written in our own words; linked pages remain the property of their publishers. Corrections: sp@paymentconsultant.top. See also Payment Rules Tracker and Payment Tech News.