Randomized trial examines secure CI/CD practices for software reliability in digital banking environments, suggesting improvements.
In today's digital era, Continuous Integration and Continuous Deployment (CI/CD) is an integral aspect of software development methodology that allows organizations to make software updates fast without compromising the quality or reliability of the software. Secure and reliable CI/CD pipelines are especially crucial in the digital banking space, the place information details are essential to financial transactions, private customer data and mission-critical services are handled through applications. Banking platforms need to keep evolving to satisfy their customers' needs and requirements, adhere to regulations, and tackle cybersecurity risks while maintaining the availability of the system and the integrity of the data. The old way of doing this with software deployment processes frequently includes long release cycles, manual testing and greater operational risks, which block innovation and slow down the delivery of critical features. CI/CD overcomes these issues by automating the integration, testing, security validation and deployment processes. But for financial institutions, the need to comply with strict regulatory rules and constraints, have a complex legacy infrastructure, be on the constant guard for cyber security threats, and deploy with zero downtime pose unique challenges to adopting an approach to CI/CD. This article looks at existing CI/CD practices and the best practices in secure and reliable implementation of CI/CD pipelines in digital banking environments. It covers DevSecOps principles, automated security testing, Infrastructure as Code, Containerisation, Continuous Monitoring, Compliance Automation and Cloud Native Deployment strategies. Additionally, a conceptual CI/CD model specifically designed for digital banking platforms is suggested for this purpose. The review highlights the impact of secure CI/CD practices on increase in reliability of software deployment, better software quality, operational efficiencies, regulatory adherence, trustworthiness of customers and organizations' resilience.
No takes yet. Share an insight, caveat, or question.
Kehinde et al. (2026) studied this question.
Synapse has enriched 5 closely related papers on similar clinical questions. Consider them for comparative context: