Loading article...
Loading article...
Stream/Area:
-
Subject:
-
Paper ID:
IJSREM68385
Volume:
10 |
10 |
Oct 2026
Pages:
1-5
Publication Frequency:
Monthly (12 issues per year)
License:International Journal of Scientific Research in Engineering and Management follows the Creative Commons Attribution 4.0 (CC BY 4.0) License, allowing free use and distribution with proper attribution.
Department of Cyber Security
Chikitsak Samuhas's Patkar Varde College
AI coding assistants based on Large Language Models (LLMs) are now widely used to generate source code, but the security quality of that code is not guaranteed. This paper proposes a design-and-evaluation framework for comparing the security of LLM-generated programs with human-written programs. Programs for identical task specifications are produced by popular AI coding assistants and by human developers, then analysed with static application security testing (SAST) tools and manual verification. The study focuses on five weakness categories: SQL Injection, Cross-Site Scripting (XSS), Broken Authentication, Insecure File Handling, and Hardcoded Credentials, mapped to CWE and OWASP classifications. Findings are compared using vulnerability density, vulnerable-program rate, severity distribution, and scanner precision. Static analysis is treated as an aid rather than a final judge: flagged issues are manually verified before being counted. The paper also discusses ethical use of AI tools, licensing, threats to validity, and recommendations for secure AI-assisted development.
KEYWORDS
AI coding assistants improve productivity, but functional code is not necessarily secure code. This paper proposed a controlled, reproducible framework for comparing LLM-generated and human-written programs across five common weakness classes, combining static analysis with manual verification and standard taxonomies. The central contribution is a methodology that treats AI output as untrusted code, measures its security with transparent metrics, and reports tool errors honestly. Empirical execution of the study will determine the actual vulnerability patterns and support evidence-based guidance for secure AI-assisted development.
[1] H. Pearce, B. Ahmad, B. Tan, B. Dolan-Gavitt, and R. Karri, "Asleep at the Keyboard? Assessing the Security of GitHub Copilot's Code Contributions," in Proc. IEEE Symposium on Security and Privacy (S&P), 2022. [2] N. Perry, M. Srivastava, D. Kumar, and D. Boneh, "Do Users Write More Insecure Code with AI Assistants?," in Proc. ACM Conference on Computer and Communications Security (CCS), 2023. [3] M. Souppaya, K. Scarfone, and D. Dodson, "Secure Software Development Framework (SSDF) Version 1.1," NIST Special Publication 800-218, 2022. [4] OWASP Foundation, "OWASP Top 10 – 2021: The Ten Most Critical Web Application Security Risks," 2021. [5] MITRE Corporation, "Common Weakness Enumeration (CWE)," https://cwe.mitre.org. [6] M. Chen et al., "Evaluating Large Language Models Trained on Code," arXiv:2107.03374, 2021. [7] Government of India, "The Digital Personal Data Protection Act, 2023," Act No. 22 of 2023, Aug. 11, 2023.
Publication Date
10/27/2026
Peer Review Type
Double-Blind Peer Review
Review Rounds: 2
Documents
Article Views
0
Total views since publication
PDF Downloads
3
Total downloads since publication
Geographic Reach
5
Digital Preservation: This article is permanently archived on Zenodo and complies with all data preservation standards across major indexing platforms.
Plagiarism Screening
This manuscript has been checked for plagiarism using TurnitinPlagiarismChecker software.
Conflict of Interest
The authors declare no conflict of interest related to this research work.
Funding Information
No funding information available for this research.
Related research in the same subject area
Loading similar articles...