Code (In)Security - ISC

Configuration differences between the development and
production environments must be ensured so that code can
execute with least privilege, irrespective of the environment. It
is also imperative to ensure that code explicitly set to run with
elevated privileges is carefully monitored (audited) and managed.
Conclusion
‘Don’t write insecure code’ is one of the eight secure habits discussed
in “8 Simple Rules for Developing More Secure Code”. i Without a
thorough understanding of what constitutes insecure code, it would
be unfair to expect developers to write more secure code.
“It is critical to all those who write
code to make it a habit to incorporate
security in the code they write. ”
Should your code fall victim to a security breach, the code itself
would be deemed innocent, but that kind of leniency will not be
extended to the individual, team, or organization that wrote the
code. So it is critical to all those who write code to make it a habit
to incorporate security in the code they write.
• Validates input
Secure Code Characteristics
• Does not allow dynamic construction of queries using
user-supplied data
• Audits and logs business-critical functions
• Is signed to verify the authenticity of its origin
• Does not use predictable session identifiers
• Does not hard-code secrets inline
• Does not cache credentials
• Is properly instrumented
• Handles exceptions explicitly
• Does not disclose too much information in its errors
• Does not reinvent existing functionality, and uses proven
cryptographic algorithms
• Does not use weak cryptographic algorithms
• Uses randomness in the derivation of cryptographic keys
• Stores cryptographic keys securely
• Does not use banned APIs and unsafe functions
• Is obfuscated or shrouded
• Is built to run with least privilege
6
“Writing secure code has the added benefit
of producing code that is of quality –
functional, reliable, and less error-prone.”
It would be far beyond the scope of this paper to enumerate all the
ways that one can avoid writing insecure code, and/or write secure
code. Instead, this should be treated as merely an eye-opener to
how to code securely, and the tremendous risks of not doing so.
Just as a game of chess produces an infinite number of moves
once the game begins, with a limited number of opening gambits,
understanding the characteristics of insecure code is one of the
first moves to ensure that code is written to be hacker-resistant.
Insecure code means checkmate.
www.isc2.org