My colleague Dave Ladd has a post "Security Education v. Security Training:"
Unfortunately, there's an assumption held by many in our (IT) community that the road to better security leads to “drinking from the fire hose” – that is to say, employees are rocketed through week long training classes, then drilled and tested on security topics. Without the necessary exposure to secure systems design and concepts, more often than not these classes simply become a blur.
Over at the Old New Thing, Raymond Chen has a really interesting post titled "How my lack of understanding of how processes exit on Windows XP forced a security patch to be recalled:"
I was one of the people brought in to study this new behavior, poke holes in its design, poke holes in its implementation, review every line of code that changed and make sure that it did exactly what it was supposed to do without introducing any new bugs along the way. We found some issues, testers found some other issues, and all the while, the clock was ticking since this was a security patch and people enjoy mocking Microsoft over how long it takes to put a security patch together.
Have you read these related articles?
Newsletter:
