[Owasp-spanish] OWASP Top 10 for 2013 Spanish
Juan C Calderon
johnccr en yahoo.com
Jue Jun 13 15:50:33 UTC 2013
I am interested as well, so count me in.
Juan Carlos Calderón
From: Fabio Cerullo <fcerullo at owasp.org>
To: Hector Aguirre <hector.antonio.aguirre at owasp.org>; "dave.wichers at owasp.org" <dave.wichers at owasp.org>
Cc: "owasp-spanish at lists.owasp.org" <owasp-spanish at lists.owasp.org>; "Juan Carlos Calderon MCE, CSSLP" <johnccr at yahoo.com>
Sent: Thursday, June 13, 2013 9:44 AM
Subject: OWASP Top 10 for 2013 Spanish
Hector et all,
now that the Top 10 has been officially released, who would be interested to translate it to spanish?
I'm happy to coordinate the activity.
Sent from my iPhone
On 13 Jun 2013, at 15:55, Hector Aguirre <hector.antonio.aguirre at owasp.org> wrote:
>There is a group for the translation of the OWASP Top 10 in Spanish?.
>Thanks and greetings from Paraguay
>On Wed, Jun 12, 2013 at 11:47 AM, Dave Wichers <dave.wichers at owasp.org> wrote:
>>The OWASP Top 10projecthasupdated and released the final version of the OWASP Top 10 for 2013based on the feedback it received during the formal comment period.
>>The OWASP Top 10for2013 is as follows:
>>A2 Broken Authentication and Session Management
>>A3 Cross-Site Scripting (XSS)
>>A4 Insecure Direct Object References
>>A5 Security Misconfiguration
>>A6 Sensitive Data Exposure
>>A7 Missing Function Level Access Control
>>A8 Cross-Site Request Forgery (CSRF)
>>A9 Using Known Vulnerable Components
>>A10 Unvalidated Redirects and Forwards
>>The final release can be downloaded from the main project page at:
>>Or the Google Top 10 Project page at:https://code.google.com/p/owasptop10/
>>If you simply want to download the document immediately, its available at:
>>Thanks to everyone for their contributions to this important OWASP project!
>>Please spread the word to those organizations you are involved in to raise awareness of these issues, particularly the new and unfamiliarA9:Using Known Vulnerable Components.With the rapid increase in the pace of development and the tempo of issuing new releases, it's getting even more challenging toavoid introducing theserisks inmodernapplications.Thisrapiddevelopment tempo is also encouraging the increased use of3rd party as well as internally developedcomponents,which have security issues just like any other software. That's why A9 was introduced, to raise awareness that developers need to make sure they arenotcontinuing tousecomponents with known vulnerabilities.
>>OWASP Top 10 Project Lead
>>OWASP-Leaders mailing list
>>OWASP-Leaders at lists.owasp.org
>OWASP-Leaders mailing list
>OWASP-Leaders at lists.owasp.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Owasp-spanish