This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org

Difference between revisions of "Bil Corry 2018 Bio and Why me"

From OWASP
Jump to: navigation, search
(Added bio from Bil's call for nominations submission)
(Added sub-headings for the sections)
Line 1: Line 1:
 +
=== Bio ===
 
I am a lifetime member of OWASP and I've been involved with OWASP since 2008. I'm currently serving on the OWASP Compliance Committee, and have contributed to a variety of projects over the years (anyone remember the OWASP Certification project?). I've volunteered at AppSec USA, rounded up speakers for chapter meetings in Chicago and the Bay Area, hosted a Bay Area chapter meeting, helped WIA become a 2.0 Committee and have been a trainer using the OWASP Secure Coding deck. You might have also seen me at W3C, IETF, and WASC (cookie specification, content security policy, WASC Threat Classification, etc). Professionally, I worked as a web application developer for more than a decade before moving into security full time.
 
I am a lifetime member of OWASP and I've been involved with OWASP since 2008. I'm currently serving on the OWASP Compliance Committee, and have contributed to a variety of projects over the years (anyone remember the OWASP Certification project?). I've volunteered at AppSec USA, rounded up speakers for chapter meetings in Chicago and the Bay Area, hosted a Bay Area chapter meeting, helped WIA become a 2.0 Committee and have been a trainer using the OWASP Secure Coding deck. You might have also seen me at W3C, IETF, and WASC (cookie specification, content security policy, WASC Threat Classification, etc). Professionally, I worked as a web application developer for more than a decade before moving into security full time.
 +
 +
=== Why Me? ===

Revision as of 00:49, 13 September 2018

Bio

I am a lifetime member of OWASP and I've been involved with OWASP since 2008. I'm currently serving on the OWASP Compliance Committee, and have contributed to a variety of projects over the years (anyone remember the OWASP Certification project?). I've volunteered at AppSec USA, rounded up speakers for chapter meetings in Chicago and the Bay Area, hosted a Bay Area chapter meeting, helped WIA become a 2.0 Committee and have been a trainer using the OWASP Secure Coding deck. You might have also seen me at W3C, IETF, and WASC (cookie specification, content security policy, WASC Threat Classification, etc). Professionally, I worked as a web application developer for more than a decade before moving into security full time.

Why Me?