Insights Contact

Trackers

Cloud, Security & Certification Tracker

← All trackers

The cloud, security and certification rules payment firms must meet, country by country: data location and cloud oversight, cyber security rules, and payment industry certifications such as PCI and Swift. Each item shows what it means, the opportunity it opens up, and its key date. Verified facts only, each linked to its source.

Last updated: Thursday, November 19, 2026 · Checked monthly against official sources. Items leave the tracker a few months after they take effect.

FILTER BY TOPIC

Cloud (3)Security (8)Certification (3)

FILTER BY REGION

Global (3)Singapore (2)United Kingdom (2)India (2)Nigeria (1)

FILTER BY STATUS

Deadline soonJust startedUpcomingProposed
Region · Topic Rule or change What it means Opportunity Key date
India
Security
RBI cyber resilience rules for non-bank PSOs
Our guide → · Source: Global Law Experts
One rulebook for payment operators; large and medium now, small by Apr 2028. Gap assessments, 6-hour incident reporting and vendor security clauses. Now; small PSOs 2028
Just started
India
Security
RBI 6-hour cyber incident reporting
Our guide → · Source: Glenbrook (summary)
Non-bank payment operators report cyber incidents within 6 hours. Automated incident detection and reporting tools. Nov 2026
Just started
Global
Certification · Security
Swift CSP annual security attestation
Our guide → · Source: Swift
Every Swift user must attest against the mandatory security controls by Dec 31. Independent assessments and control fixes for banks on Swift. Dec 31, 2026
Deadline soon
Nigeria
Cloud
Payment data must be stored in Nigeria
Our guide → · Source: BusinessDay
Payment firms must store and manage Nigerian payment data inside the country. Local cloud regions, data migration and residency testing. Jan 1, 2027
Deadline soon
Global
Certification
PCI PTS POI v5 devices expire
Our guide → · Source: PCI SSC
Card terminals approved under PTS POI v5 lose approval for new deployment. Terminal refresh plans and certification testing for acquirers. Apr 30, 2027
Upcoming
Global
Certification · Security
PCI PTS HSM v4: last new approvals
Our guide → · Source: Foregenix (PCI assessor)
New HSM models can be certified under v4 only until this date. HSM roadmap and key management upgrades ahead of v5. Jun 30, 2027
Upcoming
Singapore
Security
MAS AI risk management guidelines
Our guide → · Source: Hogan Lovells
Rules for how financial firms govern AI, including AI from vendors. AI inventories, model risk controls and vendor AI due diligence. Oct 7, 2027
Upcoming
Singapore
Security · Cloud
MAS technology risk notice changes
Our guide → · Source: Allen & Gledhill
Proposed stricter IT inventory, risk and downtime rules, incl. payment firms. IT asset inventories and resilience monitoring before rules are final. Consultation closed
Proposed
United Kingdom
Security · Cloud
Cyber Security and Resilience Bill
Our guide → · Source: UK Government
Brings data centres and managed IT providers under UK cyber law. Supplier reviews and incident-notice clauses with IT providers. Bill in Parliament
Proposed
United Kingdom
Security
UK regulators’ draft cyber resilience guidance
Our guide → · Source: Bank of England
Draft PRA and FCA expectations on managing cyber risk, including suppliers. Map cyber controls and supplier oversight against the draft expectations. Feedback due Feb 26
Proposed

WHO OWNS THIS

Cloud, security and certification: roles and sign-off

Each item on this tracker needs a clear owner and a written sign-off. The cloud solution architect owns the design and must get it approved before build; security, compliance and executives then review, certify and sign off before go-live or before an attestation is submitted.

1. Roles and responsibilities

Business owner
Product or payments head who owns the service.
  • Accountable for the service and its risk
  • Funds fixes and certifications
  • Accepts remaining risk in writing
  • Co-signs go-live
Cloud solution architect
Designs how the service runs in the cloud.
  • Owns the cloud design and data flow diagram
  • Picks regions that meet data location rules
  • Gets the design approved at the architecture board
  • Signs the design review before build
Cloud platform lead
Runs the landing zone, accounts and pipelines.
  • Builds the secure baseline: network, keys, logging
  • Runs patching, backup and recovery
  • Keeps configuration evidence
  • Fixes cloud findings by the due date
Security architect
Reviews designs against security standards.
  • Threat model and security design review
  • Approves encryption, key and access design
  • Tracks exceptions with expiry dates
  • Recommends sign-off to the CISO
CISO
Head of information security.
  • Owns the security policy and control set
  • Approves high-risk exceptions
  • Leads incident response and regulator reporting
  • Signs security readiness and attestations
Compliance and certification lead
Owns PCI DSS, PCI PTS, Swift CSP and regulator mapping.
  • Maps each rule on this page to controls
  • Plans assessment and attestation dates
  • Collects evidence packs
  • Submits attestations after sign-off
Third-party risk manager
Manages cloud providers and other key vendors.
  • Due diligence and contract terms for providers
  • Checks provider reports and certificates
  • Plans exit and concentration risk
  • Reviews providers every year
External assessor and internal audit
Independent checks.
  • QSA or Swift assessor tests controls
  • Internal audit samples the evidence trail
  • Reports findings to the audit committee
  • Confirms fixes are done
CTO or CIO
Technology executive sponsor.
  • Approves cloud strategy and funding
  • Final technology sign-off for go-live
  • Owns technology risk with the CISO
  • Reports status to the board

2. Who is accountable for what (RACI)

Activity Business owner Cloud architect Platform lead Security architect CISO Compliance lead CTO / CIO
Cloud design and data flow review C A R C I I I
Region choice and data location rules (for example Nigeria) C R C C I A I
Secure baseline: network, keys, logging I C R C A I I
Threat model and security design sign-off I R C R A I I
Cloud provider due diligence and exit plan A C C C C R I
Penetration test and fixing findings I C R C A I I
PCI DSS assessment and report A C R C C R I
Swift CSP yearly attestation I C R C A R I
Card terminal and HSM approvals (PCI PTS) A C C C I R I
Incident reporting to regulators I I R C A R I
AI risk controls (for example MAS guidelines) A C C C C R I
Go-live sign-off R R C C R C A

A accountable (one per activity, approves) · R responsible (does the work) · C consulted · I informed. External assessors and internal audit test independently and are not shown.

3. From review to sign-off

STEP 1 · BEFORE BUILD
Design review
Cloud solution architect presents design, data flow and regions; the architecture board approves.
Evidence: Signed design document, data flow diagram
STEP 2 · BEFORE BUILD
Security review
Security architect runs the threat model; CISO approves or logs exceptions with expiry dates.
Evidence: Threat model, exception log
STEP 3 · DURING BUILD
Build and test
Platform lead builds the secure baseline; pen test findings are fixed or accepted.
Evidence: Configuration evidence, pen test report
STEP 4 · YEARLY OR PER RULE
Assess and certify
Compliance lead runs PCI DSS, PCI PTS and Swift CSP checks with the assessor and closes findings.
Evidence: Assessment report, evidence pack
STEP 5 · GO-LIVE AND YEARLY
Sign off
Business owner, CISO and CTO or CIO sign; the compliance lead then submits any attestation.
Evidence: Sign-off record, submitted attestation

4. Sign-off record

One line per design, assessment or attestation. No signed line, no go-live and no submission.

Item Prepared by Reviewed by Signed off by When Evidence
Cloud design for a new payment service Cloud solution architect Security architect Architecture board, CISO Before build Design document, data flow, threat model
Swift CSP attestation 2026 Compliance and certification lead Independent assessor CISO, then submitted By Dec 31 Assessment, evidence pack, submission
PCI DSS yearly assessment Compliance and certification lead QSA Business owner, CISO, CTO or CIO Report date Report on compliance, attestation

Titles differ by firm. In smaller teams one person may hold two roles, but the person who builds should not be the only one who signs off. General guidance, not legal advice.

Runbook: from a cloud, security or certification change to sign-off

How to handle a cloud change, security standard or certification deadline 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: Cloud solution architect. With: Business owner (priority and funding), Compliance and certification lead (rule mapping), Security architect.

Example: a certification renewal. Confirm scope, systems and the audit date with the assessor.

How

  1. Open the official source linked in the tracker and read the actual text, not only the summary.
  2. Map it to your products, rails, systems, vendors and customers in scope.
  3. Run a short gap analysis: what we do today versus what the rule needs.
  4. Size the work (small, medium, large) and add it to the roadmap with a target date.
  5. 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: Cloud solution architect. With: Security architect (threat model), Cloud platform lead, Third-party risk manager (provider checks), External assessor (scope).

Example: map each control to its owner and collect existing evidence early.

How

  1. Write requirements that quote the rule clause they come from.
  2. Agree the design and any vendor or partner changes, with dates.
  3. Build a traceability matrix: rule clause, requirement, test case, evidence.
  4. Plan test data, environments and a rollback.
  5. 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: Cloud platform lead. With: Cloud solution architect, Security architect, Penetration testers.

Example: fix control gaps and run a mock audit or readiness check.

How

  1. Build or configure the change behind a flag where possible.
  2. Run unit, system, regression and negative tests, plus UAT with the business.
  3. Fix defects and re-test; keep the defect log current.
  4. Hold a go/no-go meeting with clear criteria.
  5. 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: Compliance and certification lead. With: Cloud platform lead (configuration evidence), CISO (attestation content).

Example: keep policies, screenshots, logs and tickets per control.

How

  1. Create one folder per tracker item with a simple index.
  2. Store each document with date, version and owner.
  3. Complete the traceability matrix with links to every test and approval.
  4. Add screenshots or exports of live configuration where relevant.
  5. 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: External assessor (QSA or Swift assessor). Independent check: Internal audit.

Example: the external assessor or internal audit tests the controls.

How

  1. Walk through the evidence pack against the rule text.
  2. Re-perform a sample of key tests or checks.
  3. Raise findings with a rating, owner and due date.
  4. 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: CISO. With: Compliance and certification lead, Cloud solution architect (findings, exceptions and next dates).

Example: track any findings and confirm the certificate or report is issued.

How

  1. Check live metrics: errors, rejects, exceptions, complaints, incidents.
  2. Confirm all findings and defects are closed or accepted.
  3. Note lessons learned and update this runbook if needed.
  4. 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: CTO or CIO (approves) with the Business owner. Signers in order: Cloud solution architect, Cloud platform lead, Security architect, Third-party risk manager, Compliance and certification lead, CISO.

Example: sign-off includes the CISO or security lead.

How

  1. Share the evidence pack and review notes with the approvers.
  2. Each approver confirms their part in writing, with date.
  3. Archive the pack in your GRC tool or records system.
  4. 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 Cloud solution architect Prepared Design, data flow and regions approved; data location rules met Design document, data flow, architecture board minutes ________________
2 Cloud platform lead Prepared Secure baseline built; pen test findings fixed Configuration evidence, pen test report ________________
3 Security architect Reviewed Threat model done; exceptions have expiry dates Threat model, exception log ________________
4 Third-party risk manager Reviewed Cloud provider due diligence and exit plan done Provider reports, contract terms ________________
5 Compliance and certification lead Certified PCI DSS, PCI PTS or Swift CSP requirements met; assessor findings closed Assessment report, evidence pack ________________
6 CISO Certified Security readiness confirmed; attestation content correct Signed attestation ________________
7 Business owner Approved Accepts remaining risk Signed risk acceptance ________________
8 CTO or CIO Approved Final go-live or submission approval Signed 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): Cloud, security and certification

The main risks for this area, the controls that reduce them, and the risk left after those controls. 5 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.

High residual
0
from 4 inherent
Medium residual
2
from 7 inherent
Low residual
9
from 0 inherent

11 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.

Likelihood
5
10
15
20
25
4
8
12
16
20
3
6
9
12
15
2
4
6
8
10
1
2
3
4
5
R1
R2
R3
R4
R5
C1
C2
C3
C4
C5
C6
12345
Impact

QUARTERLY RCSA CYCLE

IdentifyList risks for this area
AssessRate likelihood and impact
Map controlsLink each risk to controls
TestCheck controls work, with evidence
RateSet residual risk
ActAgree actions, owners, dates
ReportShare results and sign off

RISK AND CONTROL REGISTER

ID Type Risk and cause Control Owner Inherent Residual
CS-R1 This area A certification or attestation lapses
Cause: Renewal dates not tracked; evidence late
Renewal calendar, control owners and a mock audit 90 days before
Preventive and detective · Quarterly
Compliance and certification lead Medium 10
L2 x I5
Low 4
L1 x I4
Control: Effective
CS-R2 This area A cloud provider change breaks payments
Cause: Provider notices not read or acted on
Provider notice watch; migration plan and test before the cut-off
Preventive · Monthly
Cloud platform lead Medium 12
L3 x I4
Low 4
L1 x I4
Control: Effective
CS-R3 This area Data is stored in a region the law does not allow
Cause: Region chosen without a residency check
Region approval in design review; policy blocks unapproved regions
Preventive · Per change
Cloud solution architect High 15
L3 x I5
Low 5
L1 x I5
Control: Effective
CS-R4 This area A cloud outage stops payments
Cause: Single region; failover not tested
Multi-zone design, failover test twice a year, exit plan
Corrective · Half-yearly
Cloud platform lead Medium 10
L2 x I5
Low 6
L2 x I3
Control: Partly effective
CS-R5 This area A security exception is never closed
Cause: Exceptions have no expiry date
Exception register with expiry dates; monthly CISO review
Preventive and detective · Monthly
CISO Medium 12
L3 x I4
Low 6
L2 x I3
Control: 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
Compliance and certification 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
Compliance and certification lead 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
Cloud solution architect 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
Security architect 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
Compliance and certification 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

  • CS-R1: run a Swift CSP mock audit before Dec 1. Owner: Compliance and certification lead.
  • CS-R4: run a regional failover test before peak season. Owner: Cloud platform lead.
  • Test two controls in this area each quarter and keep the results in the evidence pack. Owner: CISO.

Quarterly attestation

Cloud solution architect and Cloud platform lead (first line): confirm risks, controls and ratings are current. ________________

CISO (second line review): confirms the review and challenge. ________________

CTO or CIO: 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.