Download to read offline
Uploaded byGareth Davies
Web Application Security - DevFest + GDay George Town 2016
The document is a presentation by Gareth Davies on web application security, covering fundamental principles of information security, including the CIA triad (confidentiality, integrity, availability) and common best practices. It highlights key do's and don'ts for web applications, stresses the importance of OWASP's top 10 vulnerabilities, and emphasizes the need for secure user authentication and data protection. Additionally, Davies discusses his background in information security and the evolution of his infosec blog and forums.
More Related Content
Similar to Web Application Security - DevFest + GDay George Town 2016
Web Application Security - DevFest + GDay George Town 2016
- 1. Web Application Security By GarethDavies - Mindvalley CTO Founder of www.darknet.org.uk Founder of www.security-forums.com slideshare.com/ShaolinTiger
- 2. So, Who amI? • I work at Mindvalley – we hiring! mindvalley.com/careers • Ex penetration testing team lead (hacker for hire) • Founder of prominent infosec blog Darknet.org.uk
- 3. Darknet – ABrief History • Started in 1999 on EFnet (IRC) by me • Original IRC co-founder from Penang • Website launched in 2000 • Current format launched in 2006 • Top 5 Infosec Blog • 40,000+ RSS Subscribers • Nominated for multiple awards Full History: http://www.darknet.org.uk/about/
- 4. Security-Forums.com – ABrief History • Started in 2002 as the Darknet Forum • Wanted to move away from Usenet • Became the fastest growing infosec forum • Referenced in Microsoft Newsletter • Running phpBB • Sold in 2004 to WindowSecurity.com Visit: http://www.security-forums.com/
- 5. This Talk • Thistalk covers: • The principle of infosec • The basic do’s and don’ts • OWASP Top 10 Who has been hacked before? Who knows the subject well or has worked in infosec? Who is familiar with OWASP Top 10?
- 6. An Introduction ToInfosec
- 7. What is InformationSecurity? • It is quite a vague phrase – but it can be defined. C AI
- 8. The CIA Triad •Thebasic model for Information Security: •Confidentiality (keeping the data secret) •Integrity (keeping the data unchanged) •Availability (keeping the data accessible)
- 9. Confidentiality “ Preventing theunauthorized disclosure of information” • Yahoo Hack exposed 500 Million Accounts • Can lead to legal issues • Hacker only needs ‘read’ access
- 10. Integrity “ Guarding againstimproper information modification or destruction” • Less frequent but more damaging • Can remain undetected for long periods (APT) • Hacker does need ‘write’ access
- 11. Availability “Ensuring timely andreliable access to the information” • DDoS attacks can be extremely damaging • Very hard to prevent and protect against • Hacker needs NO access
- 12. Web App Do’s& Don’ts
- 13. NEVER Trust UserInput • Validate type, length, format, range • Use regex, JavaScript form validation + Back-end checks • Always whitelist, not blacklist
- 14. ALWAYS Protect Datain Transit • Use HTTPS/TLS for EVERYTHING • Use HSTS To Enforce it • Redirect all HTTP users to HTTPS • Make sure your app to DB connections are encrypted
- 15. ALWAYS Hash &Salt User Passwords • Hash ALL stored user passwords • Salt all Hashes (globally unique for each user) • Use bcrypt NOT md5 or SHA-1 • Use a validated library, don’t implement yourself
- 16. ALWAYS Authenticate UsersSafely • Use an existing, mature framework • Consider SSO (login via Facebook/Twitter etc) • Use 2FA for important access (admins/super-users) • Re-authenticate for important actions (like Github/Gmail) • Hide user existence (don’t show ID doesn’t exist error) • Prevent brute forcing with CAPTCHA, rate-limiting etc
- 17.
- 18. A1- Injection • NEVERtrust user input! • Separate interpreters from command or query • For SQL this means binding calls in prepared statements • Static analysis tools can scan for this
- 19. A2- Broken Auth& Sessions • NEVER store plain-text passwords ANYWHERE • Don’t expose Session IDs • Make sure sessions time-out • Rotate Session IDs properly • Don’t send passwords/sessions over unencrypted lines
- 20. A3- Cross-site Scripting(XSS) • NEVER trust user input! • These attacks focus on the browser as the interpreter • Properly escape all untrusted data • Whitelist server-side validation (Second layer) • There are specific auto-sanitization libraries (AntiSamy)
- 21. A4- Insecure ObjectReferences • NEVER trust user input! (seeing a pattern yet?) • Don’t use easily guessable resource names • User per session or indirect object references • Check access authorization on every request
- 22. A5- Security Misconfiguration •Don’t trust default config EVER (Google MongoDB hacks) • Always change default account credentials • Learn about the tools you use and how to secure them • Don’t expose detailed error messages/debug strings • Don’t leave samples on the servers (like php_info.php)
- 23. THE END For Stalkers Twitter/Insta:@ShaolinTiger Blog: www.shaolintiger.com Infosec: www.darknet.org.uk This presentation: www.slideshare.net/ShaolinTiger