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 "Front Range OWASP Conference 2013/Sessions/Sess5 Mgmt1"
Mark Major (talk | contribs) (Created page with "{{:Front_Range_OWASP_Conference_2013/Presentations/CustomerService}} {{:Front_Range_OWASP_Conference_2013/Speakers/Rojas}}") |
Jess Garrett (talk | contribs) |
||
| Line 1: | Line 1: | ||
| − | {{:Front_Range_OWASP_Conference_2013/Presentations/ | + | {{:Front_Range_OWASP_Conference_2013/Presentations/DesktopAppSec}} |
| − | {{:Front_Range_OWASP_Conference_2013/Speakers/ | + | {{:Front_Range_OWASP_Conference_2013/Speakers/McCoy}} |
Latest revision as of 16:29, 21 March 2013
Defending Desktop (.NET/C#) Applications: Mitigating in the Dark (A Case Study Remix)
This presentation is on the case study(s) of desktop applications undergoing a cracking/hacking/attacking life cycle. This is the summation of multiple software projects undergoing attacks from a detected and focused attacker. This presentation follows a Product Owner(s) and Coder(s) going from a self directed response.
Your software project has been going for years, your client base is growing, your making deadlines then one day some e-mail shows up and your world starts to crumble. Crack after Crack keeps coming out every version; Your new Upgrades/Code keep showing up in a competing product; Malware keeps hitting your clients. See the steps taken by day-to-day product Owner(s) and Coder(s) as they respond to security events that never crossed their minds as potential threats.
Jon McCoy
| Jon McCoy is focused on .NET Framework Application Security, releasing a number of tool and whitepapers in the area of .NET Framework Security. He runs www.DigitalBodyGuard.com a ThinkTank Firm that engages in development, protecting & penetration-testing digital assets from desktop applications to enterprise infrastructure. DigitalBodyGuard has a focus on .NET Application Security well beyond Reverse Engineering and Anti-Reverse Engineering. |  |
