[Owasp-spanish] Traducción a Español del OWASP Top 10 2013

Juan C Calderon johnccr en yahoo.com
Jue Jun 13 16:46:59 UTC 2013


Sugiero que se envie un correo a los capítulos de Latino America y España, porque la gente de la lista de distribucion de spanish solo contempla gente que ya ha estado en traducciones, pero debe de haber mas interesados en los capítulos.
 
Saludos,
Juan Carlos Calderón


________________________________
 From: Mateo Martinez <mateomar at gmail.com>
To: Hector Aguirre <hector.antonio.aguirre at owasp.org> 
Cc: Fabio Cerullo <fcerullo at owasp.org>; "owasp-spanish at lists.owasp.org" <owasp-spanish at lists.owasp.org> 
Sent: Thursday, June 13, 2013 11:32 AM
Subject: [Owasp-spanish] Traducción a Español del OWASP Top 10 2013
 


Estimados,

Dave me pidió que siguieramos el tema en español y sin él de por medio.

Busquemos voluntarios hasta mañana y luego hacemos la división de tareas.

Saludos,

Mateo


2013/6/13 Hector Aguirre <hector.antonio.aguirre at owasp.org>

Hi Mateo
>
>I think it's great, even the times set.
>As we say in Spanish: "Manos a la obra".
>
>Only part is coordinating Aque who touches.
>
>regards
>
>Hector A.
>
>
>
>On Thu, Jun 13, 2013 at 11:40 AM, Mateo Martinez <mateomar at gmail.com> wrote:
>
>Hi,
>>
>>
>>I want to help too.
>>
>>
>>The raw file could be downloaded from this link: https://www.owasp.org/images/4/4d/OWASP_Top_10_-_2013_Final_-_English.pptx
>>
>>
>>Let´s confirm how many of would be able to help and the let´s split the document.
>>
>>
>>I think that we should plan to release the 1st draft of the spanish version in 2 weeks and the review it and make the final release in 1 month.
>>
>>
>>What do you think?
>>
>>
>>Regards,
>>
>>
>>Mateo
>>
>>
>>
>>
>>
>>2013/6/13 Hector Aguirre <hector.antonio.aguirre at owasp.org>
>>
>>Likewise.
>>>
>>>There even are interesting materials for translation into Spanish.
>>>
>>>Thanks to coordinate. I await your instructions to start the translations
>>>
>>>
>>>
>>>On Thu, Jun 13, 2013 at 10:44 AM, Fabio Cerullo <fcerullo at owasp.org> wrote:
>>>
>>>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.
>>>>
>>>>
>>>>thanks
>>>>Fabio
>>>>
>>>>Sent from my iPhone
>>>>
>>>>On 13 Jun 2013, at 15:55, Hector Aguirre <hector.antonio.aguirre at owasp.org> wrote:
>>>>
>>>>
>>>>⃕Excellent news!
>>>>>
>>>>>There is a group for the translation of the OWASP Top 10 in Spanish?.
>>>>>I volunteer.
>>>>>
>>>>>Thanks and greetings from Paraguay
>>>>>
>>>>>Hector Aguirre
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>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:
>>>>>>A1 Injection
>>>>>>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:
>>>>>>https://www.owasp.org/index.php/Top10
>>>>>>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:
>>>>>>http://owasptop10.googlecode.com/files/OWASP%20Top%2010%20-%202013.pdf
>>>>>>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.
>>>>>>Thanks,Dave
>>>>>>Dave Wichers
>>>>>>OWASP Top 10 Project Lead
>>>>>>OWASP Boardmember
>>>>>>_______________________________________________
>>>>>>OWASP-Leaders mailing list
>>>>>>OWASP-Leaders at lists.owasp.org
>>>>>>https://lists.owasp.org/mailman/listinfo/owasp-leaders
>>>>>>
>>>>>>
>>>>>
>>>>_______________________________________________
>>>>>OWASP-Leaders mailing list
>>>>>OWASP-Leaders at lists.owasp.org
>>>>>https://lists.owasp.org/mailman/listinfo/owasp-leaders
>>>>>
>>>
>>>_______________________________________________
>>>Owasp-spanish mailing list
>>>Owasp-spanish at lists.owasp.org
>>>https://lists.owasp.org/mailman/listinfo/owasp-spanish
>>>
>>>
>>
>

_______________________________________________
Owasp-spanish mailing list
Owasp-spanish at lists.owasp.org
https://lists.owasp.org/mailman/listinfo/owasp-spanish
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.owasp.org/pipermail/owasp-spanish/attachments/20130613/458e3b15/attachment.html>


More information about the Owasp-spanish mailing list