File:Owasp logo normal.jpg

Click on a date/time to view the file as it appeared at that time.

	Date/Time	Thumbnail	Dimensions	User	Comment
current	16:02, 29 July 2009		216 × 216 (13 KB)	Mark.bristow (talk | contribs)

More than 100 pages link to this file. The following list shows the first 100 page links to this file only. A full list is available.

• A new approach to preventing injection attacks on the Web Application Stack
• Anatomy of a Logic Flaw: Breaking the Myth
• AppSecDC OWASP O2 PLATFORM
• AppSec DC 2010 Keynote Neal Ziring
• Attacking WCF Web Services
• BeNeLux09 - Secure development (for a secure planet).
• Botnet Resistant Coding: Protecting Your Users from Script Kiddies
• Building an in-house application security assessment team
• Closing the Gap: Analyzing the Limitations of Web Application Vulnerability Scanners
• Cloudy with a chance of 0-day
• Cloudy with a chance of hack!
• Clubbing WebApps with a Botnet
• Code Reviewing Strategies
• Constricting the Web: Offensive Python for Web Hackers
• Custom Intrusion Detection Techniques for Monitoring Web Applications
• DISA's Application Security and Development STIG: How OWASP Can Help You
• Deploying Secure Web Applications with OWASP Resources
• Detecting, correcting and preventing defects through a holistic AppSec program
• Don't Judge a Website by its Icon - Read the Label!
• Ensuring Software Assurance Process Maturity
• Enterprise Application Security - GE's approach to solving root cause and establishing a Center of Excellence
• Federal Perspectives on Application Security
• Finding the Hotspots: Web-security testing with the Watcher tool
• Fracturing Flex For Fun- An Alliterative Attackers Approach
• Framed! Security-patching Common Web Development Frameworks
• Friendly Traitor 2 Features are hot but giving up our secrets is not!
• GuardRails: A Nearly Painless Solution to Insecure Web Applications
• H.....t.....t....p.......p....o....s....t
• Hacking Oracle From Web Apps
• Hacking SAP BusinessObjects
• Implementing a Secure Software Development Program
• Improving application security after an incident
• Introducing the Web Application Security Scanner Evaluation Criteria
• JavaSnoop: How to hack anything written in Java
• Learning by Breaking: A New Project Insecure Web Apps
• Lessons Learned from Process Implementation and Benchmarking
• Microsoft's Security Development Lifecycle for Agile Development
• OWASP AppSec DC 2012/Anatomy of a Logic Flaw
• OWASP AppSec DC 2012/Case Study How New Software Assurance Policy Reduces Riskand Costs
• OWASP AppSec DC 2012/Enterprise Security API ESAPI for C Plus Plus
• OWASP AppSec DC 2012/Mobile application security with Facebook Twitter
• OWASP AppSec DC 2012/Risk Analysis and Measurement with CWRAF
• OWASP AppSec DC 2012/Securing Critical Infrastructure
• OWASP AppSec DC 2012/Security at scale Web application security in a continuousdeployment environment
• OWASP AppSec DC 2012/Software Security Goes Mobile
• OWASP AppSec DC 2012/The Easy Button for Your Web Application Security Career
• OWASP AppSec DC 2012/The Unfortunate Reality of Insecure Libraries
• OWASP AppSec DC 2012/Unraveling some of the Mysteries around DOMbased XSS
• OWASP AppSec DC 2012/Using PHPIDS to Understand Attacks Trends
• OWASP AppSec DC 2012/Vulnerabilities in Industrial Control Systems
• OWASP AppSec DC 2012/WhackaMobile II Mobile App Pen Testing with the MobiSecLive Environment
• OWASP Broken Web Applications Project Update
• OWASP DHS SWA Day 2010 ESAPI
• OWASP DHS SWA Day 2010 Getting Started
• OWASP DHS SWA Day 2010 Intro
• OWASP DHS SWA Day 2010 OWASP
• OWASP DHS SWA Day 2010 OWASP WTE
• OWASP DHS SWA Day 2010 OpenSAMM
• OWASP ESAPI SwingSet
• OWASP Live CD: An open environment for Web Application Security.
• OWASP ModSecurity Core Rule Set Project
• OWASP Top 10 2010 AppSecDC
• OWASP in Action: Tools for the DISA ASD STIG
• One Click Ownage
• Pen Testing with Iron
• People, Process, and Technology: OWASP Impact on the SwA Processes and Practices Working Group
• Promoting Application Security within Federal Government
• Protecting Federal Government from Web 2.0 Application Security Risks
• Providing application-level assurance through DNSSEC
• Python Basics for Web App Pentesters
• Secure Code Review: Enterprise Metrics
• Secure Software Updates: Update Like Conficker
• Securing the Core JEE Patterns
• Smashing WebGoat for Fun and Research: Static Code Scanner Evaluation
• Social Zombies Gone Wild: Totally Exposed and Uncensored
• Software Development The Next Security Frontier
• Solving Real World Problems with ESAPI
• Synergy! A world where the tools communicate
• Techniques in Attacking and Defending XML/Web Services
• The Big Picture: Web Risks and Assessments Beyond Scanning
• The Case of Promiscuous Parameters and Other Ongoing Capers in Web Security
• The ESAPI Web Application Firewall (ESAPI WAF)
• The Entrepreneur's Guide to Career Management
• The OWASP Security Spending Benchmarks Project
• The OWASP Top 10 is dead, long live the OWASP Top 10 !
• The Strengths of Combining Code Review with Application Penetration Testing
• The Web Hacking Incidents Database
• The essential role of infosec in secure software development
• Threat Modeling by John Steven
• Threats from Economical Improvement
• Transparent Proxy Abuse
• Understanding How They Attack Your Weaknesses: CAPEC
• Understanding the Implications of Cloud Computing on Application Security
• Unicode Transformations: Finding Elusive Vulnerabilities
• User input piercing for Cross Site Scripting Attacks
• Using Misuse Cases to Articulate Vulnerabilities to Stakeholders
• WAF and Business Logic Attacks
• WXf: Web Exploitation Framework
• Web Application Security Scanner Evaluation Criteria
• When Web 2.0 Attacks - Understanding Security Implications of AJAX, Flash and