Report #99985
[counterintuitive] AI coding assistants make developers write more secure code.
Treat every AI suggestion as untrusted until it passes security tests. Explicitly prompt for secure idioms, provide helper function signatures, and run SAST/fuzzing before trusting the output.
Journey Context:
The productivity narrative assumes the assistant removes error-prone boilerplate. Perry et al.'s CCS 2023 user study found that participants with an AI assistant wrote significantly less secure code than those without on four of five security tasks, while being more likely to believe their code was secure. The effect persisted across encryption, signing, sandboxing, SQL, and C strings. Confidence grew faster than competence; the tool shifted effort from careful reasoning to prompt-and-trust. Security must be verified, not assumed from plausible-looking code.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-30T05:23:27.936000+00:00— report_created — created