Building Intelligent Risk Detection Systems for Large-Scale Financial Services with AI

References

[1] Nagraj, A. (2024). GraphQL in Wealth Management Platforms: Optimizing data access and performance. al-kindipublishers. org. 10.32996/bjmss.2024.3.1.3

[2] Beller, M., Gousios, G., Panichella, A., & Zaidman, A. (2017). Developer testing in the IDE: Patterns, beliefs, and behavior. IEEE Transactions on Software Engineering, 45(3), 261–284. https://doi.org/10.1109/TSE.2017.2776152

[3] Chen, L. (2015). Continuous delivery: Huge benefits, but challenges too. IEEE Software, 32(2), 50–54. https://doi.org/10.1109/MS.2015.27

[4] Nagraj, A. (2025). Implementing Continuous Integration and Deployment in Digital Banking and Payments. ISCSITR-INTERNATIONAL JOURNAL OF SCIENTIFIC RESEARCH IN INFORMATION TECHNOLOGY (ISCSITR-IJSRIT), 6(3), 6-21.

[5] Debroy, V., Miller, S., & Wong, W. E. (2019). Security testing in DevOps: Current practices and future directions. IEEE Software, 36(6), 24–31. https://doi.org/10.1109/MS.2019.2933682

[6] Ebert, C., Gallardo, G., Hernantes, J., & Serrano, N. (2016). DevOps. IEEE Software, 33(3), 94–100. https://doi.org/10.1109/MS.2016.68

[7] Nagraj, A. (2026, June). AI-Driven Continuous Compliance and Risk Detection in Large-Scale Brokerage and Asset Management Platforms. In 2026 4th International Conference on Inventive Computing and Informatics (ICICI) (pp. 1839-1846). IEEE. 10.1109/ICICI68773.2026.11580880

[8] Erich, F., Amrit, C., & Daneva, M. (2017). A mapping study on cooperation between information system development and operations. Information and Software Technology, 53, 124–135. https://doi.org/10.1016/j.infsof.2017.01.003

[9] Forsgren, N., Kersten, M., Storey, M. A., Maddila, C., Zimmermann, T., Houck, B., & Butler, J. (2021). The SPACE of developer productivity. Queue, 19(1), 20–48. https://doi.org/10.1145/3454122.3454124

[10] Fowler, M. (2006). Continuous Integration. IEEE Software, 23(6), 18–20. https://doi.org/10.1109/MS.2006.145

[11] Humble, J., & Molesky, J. (2011). Why enterprises must adopt DevOps to enable continuous delivery. Cutter IT Journal, 24(8), 6–12. https://doi.org/10.48550/arXiv.2201.12874

[12] Nagraj, A. (2025). Architecting Modern FinTech Systems with APIs: Approaches and Solutions. ISCSITR-INTERNATIONAL JOURNAL OF COMPUTER SCIENCE AND ENGINEERING (ISCSITR-IJCSE)-ISSN, 3067-7394.

[13] Kim, G., Debois, P., Willis, J., & Humble, J. (2021). DevOps practices in enterprise software delivery: Evidence from industry. IEEE Software, 38(1), 92–99. https://doi.org/10.1109/MS.2020.3027047

[14] Lwakatare, L. E., Karvonen, T., Sauvola, T., Kuvaja, P., Olsson, H. H., Bosch, J., & Oivo, M. (2019). DevOps in practice: A multiple case study. Information and Software Technology, 114, 217–230. https://doi.org/10.1016/j.infsof.2019.06.010

[15] Myrbakken, H., & Colomo-Palacios, R. (2017). DevSecOps: A multivocal literature review. Lecture Notes in Business Information Processing, 291, 17–29. https://doi.org/10.1007/978-3-319-64218-5_2

[16] Nagraj, A. (2024). Performance Optimization Techniques for High-Frequency Trading and Financial Platforms. Frontiers in Computer Science and Artificial Intelligence, 3(1), 90-95.

[17] Rahman, A. A., Williams, L., & Williams, L. (2020). Characterizing DevSecOps: A systematic mapping study. Proceedings of the ACM/IEEE International Symposium on Empirical Software Engineering and Measurement. https://doi.org/10.1145/3382494.3410688

[18] Shahin, M., Ali Babar, M., & Zhu, L. (2017). Continuous integration, delivery and deployment: A systematic review on approaches, tools, challenges and practices. IEEE Access, 5, 3909–3943. https://doi.org/10.1109/ACCESS.2017.2685629

[19] Soni, M. (2015). End to end automation on cloud with build pipeline: The case for DevOps and CI/CD. International Journal of Computer Applications, 132(1), 30–35. https://doi.org/10.5120/ijca2015907491

[20] Virtanen, T., Mikkonen, T., & Systä, K. (2023). Continuous software engineering in cloud-native systems: A systematic review. Journal of Systems and Software, 197, 111563. https://doi.org/10.1016/j.jss.2022.111563

@article{1720028,
      author = {Awogbade Kehinde, Asiyanbola Olaoluwa Ebenezer, Iyiola Ifeoluwa Johnson, Samson Precious Loveth, Omisope Abiodun Oluwasegun},
      title = {Building Intelligent Risk Detection Systems for Large-Scale Financial Services with AI},
      journal = {Iconic Research And Engineering Journals},
      year = {2026},
      volume = {10},
      number = {1},
      pages = {2546-2558},
      issn = {2456-8880},
      url = {https://www.irejournals.com/formatedpaper/1720028.pdf},
      abstract = {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.},
      keywords = {Continuous Integration, Continuous Deployment, CI/CD, DevSecOps, Digital Banking, Software Security, Secure Software Development, Cloud Computing},
      month = {July},
      doi = {https://doi.org/10.64388/IREV10I1-1720028}
  }