There was a phrase like: code has to be correct may be optimal must be secure phrase In…
- User
There was a phrase like: code has to be correct may be optimal must be secure phrase In one of owasp articles
- Assistant
You're likely thinking of a well-known security principle often paraphrased and cited in OWASP and secure coding communities. The phrase you're referring to is commonly stated as:
"Code must be correct, may be optimal, and has to be secure."
Or in some variations:
"Code must be correct, should be efficient, and must be secure."
Explanation:
- Correct: First and foremost, the code must do what it's intended to do — no bugs, no incorrect behavior.
- Optimal/Efficient: It's preferable for the code to be performant, but this is secondary to correctness.
- Secure: Security is non-negotiable — the code must not expose vulnerabilities or unsafe practices.
Source:
This phrase or philosophy is often attributed to the secure coding mindset promoted in OWASP, CERT guidelines, and other secure software development resources.
A similar sentiment is reflected in OWASP materials — particularly in OWASP Secure Coding Practices and tutorials about DevSecOps or Secure SDLC.
Let me know if you want the exact OWASP article or PDF where it's mentioned — I can help look it up or summarize it.
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.