agriculture | asatru | copywrongs | humor | musings | politics | technology | index | haxton.org  
   
MacRaven Logo
MacRaven
Dave Haxton's Weblog
Musings, Reflections, Rants and Comments from a Hoosier Heathen husband, father, grandfather, farmer and software engineer. There's really only one of me ...

Contact Me   

RSS Feed   

←September→
Sun Mon Tue Wed Thu Fri Sat
  1 2 3 4 5 6
7 8 9 10 11 12 13
14 15 16 17 18 19 20
21 22 23 24 25 26 27
28 29 30        

The Blogroll
A Mindful Life The Accidental Smallholder Asahel's Search Austro-Athenian Empire Brad Spangler DiRT Dispatches Garden of Thought Hardscrabble Creek The High Seat Knit Together Laudator Temporis Acti Little Heathen Fox Lorrie's Livejournal Masson's Blog Mutualist Blog MyAppleMenu nobody asked, BUT NoNAIS Notes on Religion Numenous Thoughts OrangeGuru Overlawyered Prophet or Madman rogueclassicism Secular Blasphemy Sugar Mountain Farm TMN Thud Factor Wildhunt Blog within the crainium

Page Loaded at

Eastern Standard Time

Support Denmark!

No NAIS!

MLL


lunar phases
 


Click for Thorntown, Indiana Forecast

        

home :: Technology :: Thinking_of_Sec...fects.writeback

Sun, 29 Jun 2008

Thinking of Security Vulnerabilities As Defects

Don't just think of them as defects, treat them that way. Because they are! Doh!

ZDNet Zero-Day blogger Nate McFeters has asked the question, 'Should vulnerabilities be treated as defects?' McFeters claims that if vulnerabilities were treated as product defects, companies would have an effective way of forcing developers and business units to focus on security issue. McFeters suggests providing bonuses for good developers, and taking away from bonuses for those that can't keep up. It's an interesting approach that if used, might force companies to take a stronger stance on security related issues.

(link) [Slashdot]

/Technology | 0 writebacks | permanent link

writebacks...

comment...

 
Notes: If you put a <mailto:> link in the URL field your address will not be mangled: this could be a bad idea as your email address could be easily harvested by bots designed for SPAM. The comments field should now format correctly for line feeds and carriage returns: when you hit the 'Enter' or 'Return' keys in your comment it should break to a new line. The text should wrap cleanly. Please let me know if it doesn't. No HTML tags will pass through - entering links seems to be the main cause of comment SPAM. Also, please be sure that Javascript is enabled in your browser before attempting to post a writeback. Sorry for any inconvenience, but this really helps cut down on the amount of comment SPAM I have to deal with.
 
 Name:
 URL:(optional)
 Title: (optional)
 Comments:  
Save my Name and URL/Email for next time