Enhancing Security and Real-Time Resilience in Microservices: Automated Self-Healing Controls for Secure gRPC over HTTP/3 with AES-256-GCM

Authors

  • Isarar Khan
  • Muhammad Kalamuddin Ahamad

Keywords:

Microservices security, HTTP/3, AES-256-GCM, automated remediation, Performance, Encryption

Abstract

Microservices are essential to modern distributed systems because they allow for scalability and agility, but they also present significant security and performance issues that call for rigorous mathematical answers. In this study, a performance–security model is used to describe an integrated framework for secure gRPC communication over HTTP/3 with AES-256-GCM encryption. We derive end-to-end latency analytical expressions Ltotal = Lnet + Lenc + Lproc and demonstrate how QUIC's multiplexing and 0-RTT handshake reduce Lnet whereas hardware-accelerated AES lowers Lenc We provide an algorithmic specification for runtime anomaly detection and automatic remediation, formally characterize the threat model of the system, demonstrate its termination, and bound the remediation time complexity to O(n) with regard to the number of microservices. The model's experimental deployment on a 5-node Kubernetes cluster verifies it: with only 5% more CPU overhead, mean latency dropped by 23% and throughput increased by 20% when compared to baseline HTTP/2 + TLS 1.2. The suggested approach shows how provably safe, robust, and high-performance microservice architectures can be achieved by mathematically based design of anomaly detection, cryptographic controls, and self-healing mechanisms.

Downloads

Published

2025-09-25

How to Cite

Isarar Khan, & Muhammad Kalamuddin Ahamad. (2025). Enhancing Security and Real-Time Resilience in Microservices: Automated Self-Healing Controls for Secure gRPC over HTTP/3 with AES-256-GCM. Utilitas Mathematica, 122(2), 1259–1268. Retrieved from https://utilitasmathematica.com/index.php/Index/article/view/2855

Citation Check

Most read articles by the same author(s)

Obs.: This plugin requires at least one statistics/report plugin to be enabled. If your statistics plugins provide more than one metric then please also select a main metric on the admin's site settings page and/or on the journal manager's settings pages.