[Owasp-board] Barracuda taking OWASP name in vain?

Jeff Williams jeff.williams at owasp.org
Tue Feb 12 18:17:41 UTC 2008

Yes - Curphey blogged about it and it's been on the OWASP feed too.  The
question is whether/how to respond to ridiculous abuses of the OWASP name
like this.  I'd like to have some kind of protocol to follow here, like.


1)      Nice letter explaining the brand and the violation

2)      If unfixed, warning letter explaining consequences (wall of shame)

3)      If unfixed, wall of shame






From: owasp-board-bounces at lists.owasp.org
[mailto:owasp-board-bounces at lists.owasp.org] On Behalf Of Andrew van der
Sent: Tuesday, February 12, 2008 1:36 AM
To: OWASP Board
Subject: [Owasp-board] Barracuda taking OWASP name in vain?


Hi guys,


You might have seen this. 


w&newsId=20080207005234&newsLang=en> &newsId=20080207005234&newsLang=en


About Barracuda Web Application Controllers

Barracuda Web Application Controllers, including both the Barracuda Web
Application Firewall and Barracuda Application Gateway, protect Web sites
from attackers leveraging protocol or application vulnerabilities to
instigate unauthorized access, data theft, denial of service or defacement.
Designed to deliver comprehensive Web security, Barracuda Web Application
Controllers act as a proxy for Web traffic to insulate Web servers from
direct access by hackers, enforces data security standards, such as the
Payment Card Industry Data Security Standard (PCI DSS), and secures Web
sites against the top 10 major Web vulnerabilities compiled by Open Web
Application Security Project (OWASP). Available in two models, the Barracuda
Web Application Firewall provides Web applications and Web services with
complete protection against malicious attacks. The Barracuda Application
Gateway, also available in three models, enhances the powerful Barracuda Web
Application Firewall to integrate traffic management capabilities for
increased performance and availability.

I don't think *anything* can. I deliberately made some of the Top 10 NP hard
problems to avoid claims such as this. 







-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.owasp.org/pipermail/owasp-board/attachments/20080212/54053c31/attachment-0002.html>

More information about the Owasp-board mailing list