The Illusion of Secure LLM Code: Closing the Security Gap via Iterative Reprompting
This paper evaluates the security of authentication code generated by five AI coding assistants using static code analysis and dynamic penetration testing, revealing inconsistent compliance with NIST guidelines and the need for iterative Reprompting.
First study to evaluate the security of authentication code generated by AI coding assistants using a bi-modal assessment framework.
Keywords
Before reading this…
Applications
- →Software Development
- →Security Engineering
To understand this paper, make sure you know these concepts first:
- Understanding of Large Language Modelsfind papers →
- Familiarity with NIST SP 800-63B guidelinesfind papers →
Abstract
More Like ThisLarge Language Models (LLMs) are increasingly integrated into software development workflows, yet their ability to autonomously generate secure authentication code remains uncertain. This paper evaluates the security architecture of authentication systems generated by five prominent AI coding assistants through a bi-modal assessment framework combining static code analysis and dynamic penetration testing, mapped to NIST SP 800-63B guidelines. The study examines model behavior across four prompting strategies Basic, Secure, NIST-Based, and Reprompting to reflect varying levels of developer guidance. Empirical results demonstrate that code generated from functional or generically secure prompts consistently omits critical protections, particularly concerning brute-force resistance, session management, and robust password handling. While providing explicit, single-shot NIST context significantly improves compliance, the findings reveal that this remains structurally inadequate. Instead, iterative Reprompting: forcing models into a contextual self-auditing loop is strictly required to achieve a comprehensive, defense-in-depth security architecture. Ultimately, this study proves that current AI coding assistants do not produce secure-by-default applications, dictating that enterprise deployments must transition from single-shot prompt engineering to continuous, standards-driven verification pipelines.