Zeichick's Take: Learning from LexisNexis


From the September 29th edition of News on Thursday


Email    print   
October 1, 2005 —  (Page 1 of 2)
For the past several weeks, we've been working on the technical program for next February's Software Security Summit. We've finally nailed it all down, and as of today, you should be able to see the entire class listing online at www.S-3con.com. (S-3Con is produced by BZ Media, which publishes this newsletter.)

What struck me while reviewing the final program, is how many ways that vulnerabilities can get into an application. Sometimes you have to look at the forest, not the trees; sometimes you have to look at the trees, instead of the forest. And sometimes you have to look at the a specific leaf, branch or root.

For example, one way to introduce vulnerabilities is to neglect to properly code a buffer to handle an accidental or malicious overflow. Many documented Web exploits leverage unchecked buffers. The place to fix that would be at the code level; it's not an architectural or design flaw, so architects or designers wouldn't be able to plan for it.

Yet sometimes the problem is a big-picture issue. For example, Web services and SOAs entail many hand-offs between one application and another, and they generally make implicit assumptions about the security of the transport, or the presence of an authentication/authorization system, or some such. Here, security needs to be provided at the infrastructure level, but its presence must be enforced- enforced!-by the applications themselves.

A good rule of defensive programming is, "you can't assume that the other program took care of the security." But architects and designers make that assumption all the time, and don't mandate that the individual pieces of the application most actively participate in the security scheme. Since it's not in the design, it's not in the requirements, and so it doesn't get built or tested.

But a bigger problem isn't the forest, but the forest ranger: Too few dev teams are taking security seriously-as seriously as hitting the release dates, or meeting all their functional requirements.




Pages 1 2 


Share this link: http://sdt.bz/28898
 
Most Read Latest News Blog Resources

Add comment


Name*
Email*  
Country     


  • Comment
Loading




close
NEXT ARTICLE
Zeichick’s Take: My recommendation for learning: Pair Conferencing
Why go alone when you can learn more than twice as much when you go to conferences? Read More...
 
 
 
 
News on Monday
more>>
SharePoint Tech Report
more>>


   

 
 

Download Current Issue
FEBRUARY 2012 PDF ISSUE

Need Back Issues?
DOWNLOAD HERE

Want to subscribe?


 
blogs tab
Are you at risk for burnout?
Burnout is a severe problem and it can strike at any time. Here's how to tell if you are nearing the edge.
02/09/2012 02:16 PM EST

Agility, mom, and apple pie
If we're to evaluate the state-of-the-art in software development, we should start with the values espoused in the Agile Manifesto.
02/07/2012 11:57 AM EST

RIM woos developers with free tablet
How do you get more apps ported to the BlackBerry PlayBook? By giving every developer a free tablet, of course!
02/04/2012 01:57 PM EST

GitHire: Use Headhunters to Find Your Perfect Programmer
Are you a hiring manager tired of scouring the job boards? Check out this new service that will find 5 people interested in your jobs.
02/03/2012 12:17 PM EST

Facebook claims hacker cred
Facebook's SEC S-1 filing form includes a short essay on the Hacker Way by Mark Zuckerberg himself.
02/02/2012 08:26 AM EST

Ryan Dahl steps down
Ryan Dahl, creator of Node.js, steps back from his position as gatekeeper for the project.
02/01/2012 04:58 PM EST

 
Events calendar tab
2/13/2012 to 2/16/2012
Santa Clara
TechWeb

2/26/2012 to 2/29/2012
San Francisco
BZ Media

2/27/2012 to 3/2/2012
San Francisco
RSA

3/4/2012 to 3/7/2012
Las Vegas
IBM Tivoli

3/5/2012 to 3/9/2012
San Francisco
TechWeb