Meridian Alpha

Remediation that failed retest

Q2 2026 remediation, retested in Q3 2026
As of 9 Oct 2026
Remediation that failed retest● Not holding
5 of 16
No prior period

5 of the 16 Q2 2026 remediations failed retest; 9 Q3 2026 retests are still pending.

Investigate →

Remediation that failed retest by application

View records →
actions whose validation failed · Q2 2026 remediation, retested in Q3 2026
  • SAP S/4HANA 2 20%
  • Salesforce (Sales + Financial Services Cloud) 2 20%
  • Amazon Web Services (ap-south-1) 1 10%
  • Microsoft Entra ID 1 10%
  • GitHub Enterprise Cloud 1 10%
  • Other (3) 3 30%

Domains between periods

Fastest rise: Third-Party Risk (+2)
Q2 2026Q3 2026Third-Party Risk 13 Third-Party Risk (+2)Segregation of Duties 12 Segregation of Duties (+1)Joiner/Mover/Leaver 11 Joiner/Mover/LeaverProcure-to-Pay 11 Procure-to-PayCustomer Onboarding 11 Customer OnboardingData Protection 00 Data ProtectionGovernance 00 GovernanceAccess Control 32 Access Control (-1)Operations & Resilience 21 Operations & Resilience (-1)Security Operations 10 Security Operations (-1)Logging & Monitoring 10 Logging & Monitoring (-1)Payments Security 10 Payments Security (-1)Change Management 31 Change Management (-2)
Each line is a control domain, from Q2 2026 to Q3 2026 (recorded values only). Red = rising, green = falling. Click a domain for its records.

Remediation that failed retest

JunJulAugSeptOctNovDecJan
ClosedIn progressOpenValidation (planned / failed / passed)Bars run from the cycle close when the finding was raised to the action target date.