From the course: Programming Foundations: Secure Coding

Unlock the full course today

Join today to access over 22,500 courses taught by industry experts or purchase this course individually.

Document what you understand

Document what you understand

From the course: Programming Foundations: Secure Coding

Start my 1-month free trial

Document what you understand

- Documenting your designs, documenting your APIs, and documenting your code are all built into a team's development process. What usually isn't part of the process is documenting all of the security decisions you have made. Now, I know, I know, I've heard all the excuses in the book about documentation. Heck, I've used many of them myself. I've heard documentation is dead the minute it's written, or documentation is never read, or that it's too hard to find the answers you really need. The point is, though, that regardless of the excuses, there is value in documentation especially in the security realm, as you will see. One of the first things that you should document even if only on Post-it Notes is how are going to deal with security-related bugs found in production. Now, I won't argue that you need a full-blown vulnerability management plan, you do, but that's for another course. You do, however, at least need to have a plan to prioritize and fix production security bugs and route…

Contents