Secure Coding — Resources
Secure coding is seen as a manner of writing source code compatible with the best security principles for a given system and interface. All devices, platforms, systems and even people have their own vulnerabilities and are exposed to several attack vectors and security issues, including cyberattacks and hacking.
In this sense, IT developers need to realize how important the principle of secure coding is. It can help to anticipate security challenges and prevent security issues in a premature design phase.
Some of the strategies used include the validation of all external inputs to ensure that input comes from trusted sources, checking the range of allocated memories in order to prevent buffer overflows, and many others; the list is immense. To fight this problem, developers must create a new doctrine to make secure code possible, preventing and reducing its exposure to the backdoors, loopholes, and vulnerabilities that can invite hackers.
In this article, we will present some resources connected to secure coding, including books, guides, whitepapers and discussion forums that can provide valuable information for both new students and experts.
Popular Books About Secure Coding
This section presents some interesting books that can help programmers improve their secure coding skills.
Secure Computer Software Development: Introduction to Vulnerability Detection Tools, by Ron McFarland, Ph.D., PMP, CISSP (Buy here)
A solid introduction to secure coding with screenshots, tools and compliance guidelines for best practices provided by OWASP and CERT. Rather than being a deep dive, this book serves as an introductory text. It includes a list of additional resources provided by the author and is under revision to reflect new information.
Engineering Safe and Secure Software Systems (Artech House Information Security and Privacy), by C. Warren Axelrod (Buy here)
If you need a broad spectrum of (Read more...)
*** This is a Security Bloggers Network syndicated blog from InfoSec Resources authored by Pedro Tavares. Read the original post at: http://feedproxy.google.com/~r/infosecResources/~3/gb9ndahMsQs/
