HP Security Products Blog
From applications to infrastructure, enterprises and governments alike face a constant barrage of digital attacks designed to steal data, cripple networks, damage brands, and perform a host of other malicious intents. HP Enterprise Security Products offers products and services that help organizations meet the security demands of a rapidly changing and more dangerous world. HP ESP enables businesses and institutions to take a proactive approach to security that integrates information correlation, deep application analysis and network-level defense mechanisms—unifying the components of a complete security program and reducing risk across your enterprise. In this blog, we will announce the latest offerings from HP ESP, discuss current trends in vulnerability research and technology, reveal new HP ESP security initiatives and promote our upcoming appearances and speaking engagements.

Getting to Know the OWASP ASVS

The Open Web Application Security Project OWASP is well known for its Top 10 list, and perhaps for its testing methodology as well, but comparitively few people are aware of its Application Security Verification Standard (ASVS) Project




The ASVS, as the name alludes to, is a standard for verifying the security of applications as opposed to a methodology for testing them. This is not a distinction without a difference, but rather a key piece missing from many appsec efforts...

Tags: appsec| owasp| websec
Labels: appsec| asvs| OWASP| websec

How to Practice Your Web Application Testing Skills




For those who are learning web application security testing (or just trying to stay sharp) it's often difficult to find quality websites to test one's skills. There are a few scattered around the Internet (see the link in the notes section below) but it would be nice to have a solid collection of test sites all in one place.


Aside from finding them all, another problem with most of these sites is that you can download them for free but they often require some fairly significant configuration. There should be a counter somewhere that shows how much time has been wasted trying to get Webgoat to run, for example.


There is a project that solves both of these problems simultaneously: The OWASP Broken Web Applications Project. It collects a ton of broken web apps into a single project and accomplishes a few major things:


  1. Aggregation: there are over a dozen broken apps--some on purpose and some old versions of real software.
  2. Preconfiguration: they all work the way they're supposed to--every time. 
  3. Virtualization: they run from a virtual machine so you simply run the VM and go.
The project includes the following apps (screenshot from the homescreen):


That is a ton of apps, and as I said, they actually work. You click the link as you see it above in the screenshot and you've landed on the start URL for your target. Fire up your browser, your proxy tool of choice, your favorite web scanners, etc. and you're on your way. It's projects like these that make me happy to contribute to OWASP every year.





1 Be sure to run this VM in a secure environment to avoid introduction of vulnerability to a sensitive network. Running the VM in a NAT configuration is one option.

 2 I've also compiled a list on my own site that includes a collection of the web-facing vulnerable web apps provided by vendors, as well as a number of webappsec tools and suites.

Labels: OWASP| webappsec| websec

HP Application Security Center at OWASP DC 11/11-13

The HP Application Security Center has several presentations at the upcoming OWASP Global Summit In Washington, DC. Ryan English, Rafal Los, Dennis Hurst and Kim Dinerman will all be there.  More information about the summit can be found here: OWASP Global Summit. Details concerning each of our presentations follow here:

 Dennis Hurst at OWASP

Understanding the Implications of Cloud Computing on Application Security” (11/12, 10:30-11:30)

Understanding the Implications of Cloud Computing on Application Security Cloud Computing paradigms spell fundamental changes for where your applications run, the platforms on which they run, who controls these platforms and the boundaries corporate data  crosses. The speaker will address the distinct security challenges posed by each of the three Cloud Computing models: Infrastructure as a Service (IaaS), where hosted servers, software and network equipment are deployed in the cloud; Platforms as a Service (PaaS), where the organization develops its own applications, but does so within the provider’s framework or specified platform; and Software as a Service (SaaS), where the organization trusts its  application to both the provider’s hardware and software.  What steps should you take in each case to protect your data?  Companies that choose not to use the Cloud model at all run a different risk--  rogue departments doing it anyway.  What is a logical, predictable, and mature approach to adopting Cloud Computing?

 “SDLC Industry Panel” (11/12, 2:30pm - 4:30pm)

A  panel discussion on the growth of secure SDLCs/Application Development Program/Application Life Cycles, where you can share the facets that have made your organization's efforts successful and unique, what you feel others should know so that they can improve their programs, and to talk about the future of the application security space with regards to life cycle processes.
OWASP envisions having each participant give a (very) brief introductory talk, where they discuss the highlights of their program and what has set their program apart. This will be followed by a moderated Q&A discussing overcoming hurdles in implementing an SDLC and what the next steps are in the evolution of Secure SDLCs, which will then opened to general questions from the audience.

Rafal Los at OWASP

When Web 2.0 Attacks: UnderstandingAJAX, Flashand Highly Interactive Technologies”(11/12 5:30pm-6:30pm)                                         

Web 2.0 -love it or hate it, thetechnology driving the highly interactive web experience is in your browser andcoming to your enterprise. Securing Web 2.0 requires extraordinary means due tothe increased attack surface, new breed of "Web 2.0 developers" and increasedvisibility of sites and applications. Understanding the risks associated withWeb 2.0 and beyond is essential to building "less risky" web applications intothe next phase of the web. This talk focuses on how 2 prevalent technologies;AJAXandAdobe Flash!, create the potential forcatastrophic failure. Focus is given to understandingeach technology's attack surface, most common security failures, andexploitation of common coding mistakes. This workshop-style walk-through of theWeb 2.0's ugly underbelly will give participants a deeper understanding of whysecurity professionals are terrified of "highly interactive web technologies"and why we say that "everything old is new again."

Even in recession, web application security spending to increase

A recent OWASP survey found that over a quarter of IT organizations plan to spend more money specifically for web application security.  Another 36% expect web application security spending to remain at current levels. Considering the state of the economy, those are good numbers. Even with recessionary belt-tightening and across the board budget reductions, web application security isn't being ignored because more enterprises understand it simply can't be ignored. Granted, this survey was conducted on a site devoted to web application security, so the responders are much more likely to care than 'other' IT professionals. But, if anybody should know that security spending is going up or at least staying the same, it's them. Let's call that a push.

There are some other good nuggets within thesurvey. This is the best selling point I've heard for web application security in quite some time. "Organizations that have suffered a public data breach spend more on security in the development process than those that have not." We'll call that the 'barn door axiom'.  If you've been breached, the pain ensures you do what you can to mitigate the risk of another incident. And the best way to do that is building security into the development process, not brushing it on after the product has been released.


Showing results for 
Search instead for 
Do you mean 
About the Author(s)
Top Kudoed Posts
HP Blog

HP Software Solutions Blog


Follow Us
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.