Systems | Development | Analytics | API | Testing

Kuwaiti banks got two very different signals from their regulator within a few months of each other. In December 2025, the Central Bank of Kuwait (CBK) replaced its 2020 Cybersecurity Framework with something far more demanding – the Cyber and Operational Resilience Framework (CORF). Then in March 2026, CBK went the other way on capital and liquidity, temporarily easing several key ratios to give banks more breathing room. Read separately, these look like contradictory moves.

On 26 March 2026, the KSA Central Bank moved Open Banking out of its controlled sandbox and into a formal licensing regime, granting its first licences to Neotek and Lean Technologies on the same day. For KSA banks, this was more than a regulatory milestone it marks the moment when “being innovative” is no longer enough. Since March, SAMA has kept licensing new open banking and payment companies. More approvals came through the year, including in the second and third quarters.

On 16 September 2026, the one-year transitional period under the UAE’s new Central Bank Law comes to an end. Federal Decree-Law No. 6 of 2025 came into force on 16 September 2025, giving licensed financial institutions exactly one year to bring their operations into line with a fully overhauled regulatory framework. That window is now closing.

Quick answer: Agentic AI in banking refers to AI systems that don’t just generate text or answer questions – they take a goal, break it into steps, use tools and data sources, make decisions, and complete multi-step workflows (like investigating a fraud case or processing a KYC file) with minimal human intervention, looping in a person only for genuine judgment calls. Walk into any banking technology conference in 2026, and you’ll notice the conversation has quietly shifted.

Every year, retailers invest millions in uptime. Yet when disaster strikes, most discover their DR plan protects infrastructure, not the business that runs on it. “It wasn’t the outage that hurt us most. It was the 45 minutes we had no idea it was happening.” – CTO, UK fashion retailer, post-incident review You have a DR plan. Your infrastructure team tested it six months ago. Your board presentation has a green tick next to Business Continuity.

If you’re running Microsoft Dynamics 365 and relying on RSAT (Regression Suite Automation Tool) to keep your test automation ticking, there’s a deadline you cannot afford to ignore: RSAT support ends on 15 May 2027. That’s not far away, and the decisions you make now will shape how painlessly your QA practice survives the transition. So let’s talk about what comes next and why the answer is more interesting than you might expect.

There is a moment most travel platform teams are now experiencing for the first time. The AI-powered booking assistant is live. The conversational search feature is generating rave reviews from product managers. The personalised itinerary engine is pulling data from a dozen microservices in real time. And then peak season arrives. Response times climb. The AI layer starts queuing. The booking funnel drops. Users abandon. And the engineering team realises something uncomfortable.

A strategic framework for using AI-powered quality engineering to accelerate delivery without sacrificing regulatory requirements.

Are you still relying on manual testing for your Dynamics 365 Finance & Operations (D365 F&O) environment? In today’s fast-paced digital landscape, where Microsoft rolls out frequent updates and business needs evolve rapidly, manual testing is no longer just inefficient. It’s a strategic risk.

Performance testing without observability is like diagnosing a sick patient using only a thermometer. You get one number. You miss everything that matters. Observability-driven performance testing combines load testing with metrics, logs and distributed tracing to identify not just when performance degrades, but exactly why.