The Peon's Guide To Secure System Development
libertynews writes "Michael Bacarella has written an article on coding and security. He starts out by saying 'Increasingly incompetent developers are creeping their way into important projects. Considering that most good programmers are pretty bad at security, bad programmers with roles in important projects are guaranteed to doom the world to oblivion.' It is well worth the time to read it."
for me to peon.
Karma: Good (despite my invention of the Karma: sig)
While 'tis true I'm sure that secure coding practices grow more likely to contain security flaws as more and more of us code, I think the best way for coding to become more secure is to have more managers in the bizz that know about code.
The more experienced a manager is in actual coding,the more likely he or she will:
>Listen to and support action upon security
>Allow time to make apps secure in project deadlines
>Be less likely buy crappy software from the start (see the section in the article on middleware)
>Hire good sys admins
I don't think coders should always get such a bad rap when those "above" tend to sell products without often thinking of how to make it secure, and sometimes don't allow programmers the time to design solid security into a system.
Don't retire, just replace someone that thinks powerpoint is a good web development app.
Prevent email address forgery. Publish SPF records for y