Skip to content
Open access

An empirical lifecycle security validation framework for web application development and deployment

Dec 2026 · Array · 0 citations · 67 references

Abstract

Web applications remain vulnerable to cyberattacks such as SQL Injection (SQLi), Cross-Site Scripting (XSS), Command Injection, insecure container deployments, and software supply-chain attacks. Although modern DevSecOps practices integrate security throughout software development, existing security mechanisms often address these issues independently and provide limited support for systematic lifecycle security validation. This study presents an empirically validated lifecycle security methodology that integrates secure coding practices, container security, software supply-chain verification, deployment verification, and runtime monitoring into a unified software engineering workflow. The proposed methodology was implemented and experimentally evaluated using a purposely vulnerable Flask web application. The security effectiveness was verified through vulnerability assessments, secure coding, automated static security analyses, container hardening, software supply-chain verification, and runtime attack detection. The experimental findings show that all four representative application-layer attack attempts were prevented under the controlled experimental conditions, resulting in an Attack Prevention Rate (APR) of 100% (4/4). The container hardening process reduced the number of vulnerabilities identified from 1067 to 53 (VRR = 95.0%). In addition, the deployment validation satisfied all seven predefined security requirements (DCR = 100%) under the evaluated experimental conditions. These results demonstrate that integrating lifecycle security validation into software development and deployment workflows provides a practical and reproducible methodology for improving web application security while supporting modern secure software engineering and DevSecOps practices.

Read PDF

We use cookies to run the site and, with your consent, for analytics and to show ads. See our Cookie Policy.