Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | Re: [WEB SECURITY] New PCI requires code review or WAF |
|---|---|
| Date: | Fri, 08 Sep 2006 11:24:50 -0400 |
I would guess that since they have done a list of approved scanning vendors: https://sdp.mastercardintl.com/vendors/vendor_list.shtml they will do another list of vendors that specialize in web applications? Jeff Robertson wrote:
Before actually reading the PDF, I immediately want to ask:
1. What are the criteria for an "organization that specializes in
application security"?
2. What is considered an application layer firewall?
Maybe these questions are answered in the document.
------------------------------------------------------------------------
*From:* Jeff Williams [mailto:jeff.williams@owasp.org]
*Sent:* Thursday, September 07, 2006 10:22
*To:* webappsec@securityfocus.com; webappsec@lists.owasp.org;
websecurity@webappsec.org
*Subject:* [WEB SECURITY] New PCI requires code review or WAF
Under the new requirements, applications processing cardholder
information MUST get either a code review or a web app firewall.
The language isn’t exactly clear about what happens in 2008.
>From the document --
https://www.pcisecuritystandards.org/pdfs/pci_dss_v1-1.pdf
6.5 Develop all web applications based on secure coding guidelines
such as the Open Web Application Security Project guidelines. Review
custom application code to identify coding vulnerabilities. Cover
prevention of common coding vulnerabilities in software development
processes, to include the following:
6.5.1 Unvalidated input
6.5.2 Broken access control (for example, malicious use of user IDs)
6.5.3 Broken authentication and session management (use of account
credentials and session cookies)
6.5.4 Cross-site scripting (XSS) attacks
6.5.5 Buffer overflows
6.5.6 Injection flaws (for example, structured query language (SQL)
injection)
6.5.7 Improper error handling
6.5.8 Insecure storage
6.5.9 Denial of service
6.5.10 Insecure configuration management
6.6 Ensure that all web-facing applications are protected against
known attacks by applying either of the following methods:
. Having all custom application code reviewed for common
vulnerabilities by an organization that specializes in application
security . Installing an application layer firewall in front of
web-facing applications.
Note: This method is considered a best practice until June 30, 2008,
after which it becomes a requirement.
--Jeff
Jeff Williams, Chair
The OWASP Foundation <http://www.owasp.org/>
-- Nick Owen WiKID Systems, Inc. 404.962.8983 http://www.wikidsystems.com Commercial/Open Source Two-Factor Authentication https://www.linkedin.com/in/nickowen ------------------------------------------------------------------------- Sponsored by: Watchfire As web applications become increasingly complex, tremendous amounts of sensitive data - personal, medical and financial - are exchanged, and stored. Consumers expect and demand security for this information. This whitepaper examines a few vulnerability detection methods - specifically comparing and contrasting manual penetration testing with automated scanning tools. Download "Automated Scanning or Manual Penetration Testing?" today! https://www.watchfire.com/securearea/whitepapers.aspx?id=701500000008Vmm --------------------------------------------------------------------------
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [Full-disclosure] Cross Context Scripting with Sage, pdp (architect) |
|---|---|
| Next by Date: | Re: Microsoft Research Builds BrowserShield, Sap . |
| Previous by Thread: | [Full-disclosure] Cross Context Scripting with Sage, pdp (architect) |
| Next by Thread: | Re: [WEB SECURITY] New PCI requires code review or WAF, Dave Ockwell-Jenner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |