This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org

Difference between revisions of "Template:Application Security News"

From OWASP
Jump to: navigation, search
Line 3: Line 3:
 
: Comment or "Quote"
 
: Comment or "Quote"
 
-->
 
-->
 +
 +
; '''Jul 18 - [http://www.fortifysoftware.com/reports/threatreport.jsp Fortify study shows raging storm]'''
 +
: "On average, 50%-70% of attacks experienced by web applications come from bots and bot networks searching for known vulnerabilities...The effect is much like a storm raging over a landscape – the probes are sprayed throughout the Internet and ceaselessly (and somewhat randomly) hit web applications."
  
 
; '''Jul 18 - [http://pestilenz.org/cgi-bin/blosxom.cgi/2005/11/11 Think liability for vendors will work? Try unreliable programming]'''
 
; '''Jul 18 - [http://pestilenz.org/cgi-bin/blosxom.cgi/2005/11/11 Think liability for vendors will work? Try unreliable programming]'''
Line 12: Line 15:
 
; '''Jul 12 - [http://googleresearch.blogspot.com/2006/06/extra-extra-read-all-about-it-nearly.html Beware integer overflow in Java]'''
 
; '''Jul 12 - [http://googleresearch.blogspot.com/2006/06/extra-extra-read-all-about-it-nearly.html Beware integer overflow in Java]'''
 
: Joshua Bloch (of Java Puzzlers fame) discovered this [[Integer overflow|overflow]] that affects Arrays.binarySearch() and any other divide-and-conquer algorithms (probably other languages as well). "The general lesson that I take away from this bug is humility: It is hard to write even the smallest piece of code correctly, and our whole world runs on big, complex pieces of code."
 
: Joshua Bloch (of Java Puzzlers fame) discovered this [[Integer overflow|overflow]] that affects Arrays.binarySearch() and any other divide-and-conquer algorithms (probably other languages as well). "The general lesson that I take away from this bug is humility: It is hard to write even the smallest piece of code correctly, and our whole world runs on big, complex pieces of code."
 
; '''Jul 12 - [http://opensource.sys-con.com/read/244332_p.htm Source code secrecy not a countermeasure]'''
 
: Yet another pointless article discussing whether open-source or closed-source is more secure. The truth is that your application should be secure even if an attacker has the source. If you're using a source code control system (and you absolutely should), there are copies of your code all over the place. So get over it - secrecy isn't a countermeasure.
 
 
; '''Jul 11 - [http://www.yankeegroup.com/public/research/author_page.jsp?ID=E6175864177D44AD Yankee predicts AAP to replace WAF]'''
 
: In a report titled, "Application Assurance Platforms Arise from Web App Firewall Market’s Ashes," Yankee projects overall product revenue in the evolving AAP market to grow to $230 million by 2009. AAP's are predicted to combine the web application firewall, database security, XML security gateway and application traffic management segments.
 
  
 
; [[Application Security News|Older news...]]
 
; [[Application Security News|Older news...]]

Revision as of 12:04, 18 July 2006


Jul 18 - Fortify study shows raging storm
"On average, 50%-70% of attacks experienced by web applications come from bots and bot networks searching for known vulnerabilities...The effect is much like a storm raging over a landscape – the probes are sprayed throughout the Internet and ceaselessly (and somewhat randomly) hit web applications."
Jul 18 - Think liability for vendors will work? Try unreliable programming
Imagine there was liability for software vendors. They would introduce "an interesting new paradigm of programming. Methods of this school of programming could include: Do something random, procrastination, decoy, blame someone else, and Inject errors in other running programs."
Jul 17 - Give offensive coding a try
"Spurious null checks are a symptom of bad code. That’s not to say that null checks are wrong. If a vendor gives you a library that can return null, you’re obliged to check for null. And, if people are passing null all over the place in your code, it makes sense to keep putting some null checks in, but, you know what? That just means that you’re dealing with bad code"
Jul 12 - Beware integer overflow in Java
Joshua Bloch (of Java Puzzlers fame) discovered this overflow that affects Arrays.binarySearch() and any other divide-and-conquer algorithms (probably other languages as well). "The general lesson that I take away from this bug is humility: It is hard to write even the smallest piece of code correctly, and our whole world runs on big, complex pieces of code."
Older news...