Secure coding: Difference between revisions

Revision as of 17:18, 4 November 2020

Revision as of 01:28, 14 December 2020

Line 6:

{{Computer security}}

'''Secure coding''' is the practice of developing computer [[software]] in a way that guards against the accidental introduction of security vulnerabilities. Defects, [[Software bug|bugs]] and logic flaws are consistently the primary cause of commonly exploited software vulnerabilities.<ref name="bss2001">{{Cite book| last = Viega | first = John |author2=Gary McGraw | title = Building Secure Software: How to Avoid Security Problems the Right Way | year = 2001 | publisher = MAddison-Wesley Professional | pages = 528 | isbn = 978-0201721522 | page = }}</ref> Through the analysis of thousands of reported vulnerabilities, security professionals have discovered that most vulnerabilities stem from a relatively small number of common software programming errors. By identifying the insecure coding practices that lead to these errors and educating developers on secure alternatives, organizations can take proactive steps to help significantly reduce or eliminate vulnerabilities in software before deployment.<ref>{{Cite journal|last=Taylor|first=Blair|last2=Azadegan|first2=Shiva|date=2006-09-22|title=Threading secure coding principles and risk analysis into the undergraduate computer science and information systems curriculum|url=https://doi.org/10.1145/1231047.1231053|journal=Proceedings of the 3rd annual conference on Information security curriculum development|series=InfoSecCD '06|___location=Kennesaw, Georgia|publisher=Association for Computing Machinery|pages=24–29|doi=10.1145/1231047.1231053|isbn=978-1-59593-437-6}}</ref>

== Buffer-overflow prevention ==

Line 81:

==References==

{{Reflist}}

* {{Cite book| last = Taylor | first = Art |author2=Brian Buege |author3=Randy Layman | title = Hacking Exposed J2EE & Java | year = 2006 | publisher = McGraw-Hill Primis | pages = 426 | isbn = 0-390-59975-1 | page = }}

==External links==