|
|
| (4 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| | === Main === | | === Main === |
| | + | <!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --> |
| | + | <div style="width:100%;height:100px;border:0,margin:0;overflow: hidden;">[[Image:OWASP Inactive Banner.jpg|800px| link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Inactive_Projects]] </div> |
| | + | == Objective == |
| | | | |
| − | == Objective ==
| + | The OWASP Enterprise Application Security Project (OWASP-EAS) exists to provide guidance to people involved in the procurement, design, implementation, or sign-off of large scale (i.e. 'Enterprise') applications. |
| | | | |
| − | The OWASP Enterprise Application Security Project (OWASP-EAS) exists to provide guidance to people involved in the procurement, design, implementation or sign-off of large scale (i.e. 'Enterprise') applications. | + | The latest project information can be found here <nowiki>http://eas-sec.org</nowiki> |
| | | | |
| | == The purpose of the project == | | == The purpose of the project == |
| Line 15: |
Line 18: |
| | 1 Aware people about enterprise application security vulnerabilities by releasing annual statistics of enterprise business application security vulnerabilities. | | 1 Aware people about enterprise application security vulnerabilities by releasing annual statistics of enterprise business application security vulnerabilities. |
| | | | |
| − | [[Enterprise Business Application Vulnerability Statistics]] | + | [[Enterprise Application Vulnerability Statistics]] |
| | | | |
| − | 2 Help companies to begin assessment of enterprise applications | + | 2 Help companies to begin the assessment of enterprise applications |
| | | | |
| − | [[Enterprise Business Application Security Implementation Assessment]] | + | [[Enterprise Application Security Vulnerability Assessment]] |
| | | | |
| | 3 Help companies to securely develop and customize business applications | | 3 Help companies to securely develop and customize business applications |
| | | | |
| − | [[Enterprise Business Application Security Development Issues]] | + | [[Enterprise Application Security Development Issues]] |
| − | | |
| − | 4 Develop free tools for Enterprise business applications assessment
| |
| − | | |
| − | [[Enterprise Business Application Security Software]]
| |
| | | | |
| | == Project Roadmap == | | == Project Roadmap == |
| | | | |
| | Have a look at the [[OWASP Enterprise Application Security Project/Roadmp]] | | Have a look at the [[OWASP Enterprise Application Security Project/Roadmp]] |
| − |
| |
| − | === Statistics ===
| |
| − |
| |
| − | == Objective ==
| |
| − |
| |
| − | This document is the first statistics report which will be repeated annually including tendencies and changes in Enterprise Business Application Security area.
| |
| − |
| |
| − | == Purpose ==
| |
| − |
| |
| − | This document will show the results of statistical research in the Business Application security area made by ERPscan Research Group and OWASP-EAS project. The purpose of this document is to raise awareness about Enterprise Business Application security by showing the current number of vulnerabilities found in those applications, how critical those are and what tendences we see.
| |
| − |
| |
| − | == Intro ==
| |
| − |
| |
| − | Business applications like ERP, CRM, SRM, and others are one of the major topics within the field of computer security as these applications store business data, and any vulnerability in these applications will cause a significant monetary loss. Nonetheless, people still do not pay much attention to Enterprise Business Application, judging by our and our collegues' research and assessment data.
| |
| − | Business applications are very large and complex systems that consist of different components such as Database server, Front-end, Web server, Application server and other parts. Also, those systems rely on different hardware and software that can have their own vulnerabilities.
| |
| − | Overall security of an Enterprise Business Application consist of different layers, such as: <br>
| |
| − | • Network architecture security <br>
| |
| − | • OS security <br>
| |
| − | • Database security <br>
| |
| − | • Application security <br>
| |
| − | • Front-end security <br>
| |
| − |
| |
| − | Every described layer may have its own vulnerabilities that can give attacker full access to business data even if other layers are completely secured. In this document, all the popular applications from described levels and their vulnerabilities will be shown. The purpose of this document is to increase awareness of Business Application security.
| |
| − |
| |
| − | == Links ==
| |
| − |
| |
| − | Surveys:
| |
| − |
| |
| − | [http://dsecrg.com Business applications vulnerability statistics 2009 and future trends] - Presentation by Dmitry Evdokimov and Dmitry Chastukhin
| |
| − |
| |
| − | [https://www.owasp.org/images/6/6b/SAP_Security_in_figures_-_a_global_survey_2007-2011._OWASP-EAS.pdf SAP Security In Figures – A Global Survey 2007-2011]
| |
| − |
| |
| − | Links:
| |
| − | [http://www.sdn.sap.com/irj/sdn/index?rid=/webcontent/uuid/c05604f6-4eb3-2d10-eea7-ceb666083a6a SAP SDN page with latest vulnerabilities]
| |
| − |
| |
| − | [http://www.oracle.com/security/critical-patch-update.html Oracle Secalert CPU page with latest vulnerabilities]
| |
| − |
| |
| − | == Authors ==
| |
| − |
| |
| − | Alexander Polyakov, Alexey Tyurin, Dmitry Chastukhin, Dmitry Evdokimov (ERPScan Research Group)
| |
| − |
| |
| − |
| |
| − |
| |
| − | === Development of guides ===
| |
| − |
| |
| − | == Objective ==
| |
| − |
| |
| − | This document will describe different areas of program vulnerabilities that can be found in Enterprise Business applications and ERP systems.
| |
| − |
| |
| − | == Purpose ==
| |
| − |
| |
| − | The purpose of this document is to increase awareness of the developers of Enterprise Business software. Here, we will collect top software vulnerabilities in server side and frontend side that can exist in Business Applications.
| |
| − |
| |
| − | == Intro ==
| |
| − |
| |
| − | There are many different languages and technologies that can be used to develop business applications and write costom code. Here, we will try to categorize it first by dividing into Server and Client side. Top 10 list of vulnerabilities for both areas will be shown.
| |
| − |
| |
| − | == Main ==
| |
| − |
| |
| − | Crosslinks to CWE SANS OWASP and risks with descriptions will be added soon.
| |
| − |
| |
| − | [[Image:Dev1.png|484x290px]] <br>
| |
| − |
| |
| − | <br>
| |
| − |
| |
| − | <br>
| |
| − |
| |
| − | <br>
| |
| − |
| |
| − | <br>
| |
| − |
| |
| − | <br>
| |
| − |
| |
| − | <br>
| |
| − |
| |
| − | <br>
| |
| − |
| |
| − | == Top 10 Server vulnerabilities (EASAD) ==
| |
| − |
| |
| − | 1 XSS<br>
| |
| − | 2 Improper Access Control<br>
| |
| − | 3 Information disclosure<br>
| |
| − | 4 Command/code injection in proprietary language<br>
| |
| − | 5 SQL Injection <br>
| |
| − | 6 Missing Encryption of Sensitive Data<br>
| |
| − | 7 Buffer overflows <br>
| |
| − | 8 Path traversal<br>
| |
| − | 9 CSRF <br>
| |
| − | 10 Use of a Broken or Risky Cryptographic Algorithm
| |
| − |
| |
| − | == Top 10 Frontend vulnerabilities (EASFD) ==
| |
| − |
| |
| − | 1 Buffer overflows (ActiveX)<br>
| |
| − | 2 Exposed Dangerous Method or Function (ActiveX)<br>
| |
| − | 3 Insecure scripting server access <br>
| |
| − | 4 File handling Frontend vulnerabilities<br>
| |
| − | 5 Use of a Broken or Risky Cryptographic Algorithm<br>
| |
| − | 6 Cleartext Storage of Sensitive Information<br>
| |
| − | 7 Use of hard-coded password<br>
| |
| − | 8 Lack of integrity checking for front-end application<br>
| |
| − | 9 Cleartext Transmission of Sensitive Information<br>
| |
| − | 10 Vulnerable remote services
| |
| − |
| |
| − | == Links ==
| |
| − |
| |
| − | coming soon
| |
| − |
| |
| − | <br>
| |
| − |
| |
| − | == Authors ==
| |
| − |
| |
| − | Alexander Polyakov (ERPScan Research Group) <br>
| |
| − | Mikhail Markevich <br>
| |
| − | Dmitry Evdokimov (ERPScan Research Group) <br>
| |
| − | Alexey Sintsov (ERPScan Research Group)
| |
| − |
| |
| − |
| |
| − |
| |
| − | === Implementation guides ===
| |
| − |
| |
| − | == Objective ==
| |
| − |
| |
| − | This document will describe different areas of secure implementation of Enterprise Business Applications and ERP systems. Here, we will mainly focus on security architecture and configuration threats because program errors are well described in the "Software vulnerabilities" topic.
| |
| − |
| |
| − | == Purpose ==
| |
| − |
| |
| − | The purpose of this document is to increase awareness of the administrators of Business Application security and help them to start a self-assessment of their systems and find the most critical violations.
| |
| − |
| |
| − | == Intro ==
| |
| − |
| |
| − | Enterprise Business Applications (like ERP, it is any software system that has been designed to support and automate the business process of medium and large business) are very large systems that consist of different components such as Database server, Front-end, Web server, Application server and other parts. Also, those systems rely on different hardware and software that can have their own vulnerabilities. Every described layer may have its own vulnerabilities and misconfigurations that can give attacker full access to business data even if other layers are completely secured.
| |
| − |
| |
| − | All the data was collected and categorized during our big practice of assessing the security of popular Business Applications such as SAP ERP, Oracle E-Business Suite, Oracle Peoplesoft, JD-Edwards and other less known or custom applications.
| |
| − |
| |
| − | == Main ==
| |
| − |
| |
| − | Overall security of Enterprise Business Application consists of different layers, including: <br>
| |
| − | • Network architecture security <br>
| |
| − | • OS security <br>
| |
| − | • Database security <br>
| |
| − | • Application security <br>
| |
| − | • Front-end security <br>
| |
| − | In this document, we will describe top 10 violations on every layer of Enterprise Business Application that can be easily assessed and mitigated.
| |
| − |
| |
| − |
| |
| − | [[Image:Dev2.png]]
| |
| − |
| |
| − | == Top 10 Network/Architecture issues ==
| |
| − |
| |
| − | 1 Lack of proper network filtration between EA and Corporate network<br>
| |
| − | 2 Lack or vulnerable encryption between corp net and EA Network<br>
| |
| − | 3 Lack of separation between Test, Dev, and Prod system<<br>
| |
| − | 4 Lack of encryption inside EA Network<br>
| |
| − | 5 Insecure trusted relations between components<br>
| |
| − | 6 Insecurely configured Internet facing applications <br>
| |
| − | 7 Vulnerable / default configuration of routers<br>
| |
| − | 8 Lack of frontend access filtration<br>
| |
| − | 9 Lack or misconfigured monitoring IDS/IPS<br>
| |
| − | 10 Insecure/unappropriate wireless comunications
| |
| − |
| |
| − | == Top 10 OS issues ==
| |
| − |
| |
| − | 1 Unnecessary enabled services<br>
| |
| − | 2 Missing 3rd party software patches<br>
| |
| − | 3 Insecure trust relations<br>
| |
| − | 4 Universal OS passwords<br>
| |
| − | 5 Missing OS patches<br>
| |
| − | 6 Lacking or misconfigured network access control<br>
| |
| − | 7 Lacking or misconfigured monitoring<br>
| |
| − | 8 Insecure internal acces control <br>
| |
| − | 9 Unencrypted remote access <br>
| |
| − | 10 Lack of password lockout/complexity checks<br>
| |
| − |
| |
| − | == Top 10 Database issues ==
| |
| − |
| |
| − | 1 Default passwords for DB access<br>
| |
| − | 2 Lack of DB patch management<br>
| |
| − | 3 Unnecessary enabled DB features <br>
| |
| − | 4 Lack of password lockout/complexity checks<br>
| |
| − | 5 Unencrypted sensitive data transport / data<br>
| |
| − | 6 Lack or misconfigured network acess control<br>
| |
| − | 7 Extensive user and group privileges<br>
| |
| − | 8 Lacking or misconfigured audit<br>
| |
| − | 9 Insecure trust relations<br>
| |
| − | 10 Open additional interfaces
| |
| − |
| |
| − | == Top 10 Application issues ==
| |
| − |
| |
| − | 1 Lack of patch management<br>
| |
| − | 2 Default passwords for application access<br>
| |
| − | 3 SoD conficts<br>
| |
| − | 4 Unnecessary enabled application features <br>
| |
| − | 5 Open remote management interfaces<br>
| |
| − | 6 Lack of password lockout/complexity checks<br>
| |
| − | 7 Insecure options <br>
| |
| − | 8 Unecrypted communications<br>
| |
| − | 9 Insecure trust relations<br>
| |
| − | 10 Guest access
| |
| − |
| |
| − | == Top 10 Frontend issues ==
| |
| − |
| |
| − | 1 Vulnerable frontend applications<br>
| |
| − | 2 Lack of server trust check<br>
| |
| − | 3 Lack of encryption<br>
| |
| − | 4 Autocomplete enabled in the browser <br>
| |
| − | 5 Insecure browser scripting options<br>
| |
| − | 6 Insecure configuration <br>
| |
| − | 7 Insecure sortware distribution service<br>
| |
| − | 8 Lack of AV software<br>
| |
| − | 9 Password stored in configuration file<br>
| |
| − | 10 Sensitive information storage
| |
| − |
| |
| − | == Links ==
| |
| − |
| |
| − | [http://dsecrg.com ERP Security:Myths Problems Solutions] - by Alexander Polyakov and Ilya Medvedovsky
| |
| − |
| |
| − | == Authors ==
| |
| − |
| |
| − | Alexander Polyakov (ERPScan Research Group)
| |
| − | Mikhail Markevich
| |
| | | | |
| | ==== Project About ==== | | ==== Project About ==== |
| Line 261: |
Line 40: |
| | __NOTOC__ <headertabs /> | | __NOTOC__ <headertabs /> |
| | | | |
| − | [[Category:OWASP_Project|Enterprise Application Security Project]] [[Category:OWASP_Document]] [[Category:OWASP_Alpha_Quality_Document]] | + | [[Category:OWASP Project|Enterprise Application Security Project]] |
| | + | [[Category:OWASP_Document]] |
| | + | [[Category:OWASP_Alpha_Quality_Document]] |
The OWASP Enterprise Application Security Project (OWASP-EAS) exists to provide guidance to people involved in the procurement, design, implementation, or sign-off of large scale (i.e. 'Enterprise') applications.
Enterprise applications security is one of the major topics in overall security area because those applications control money and resources, and any security violation can result in significant money loss. The purpose of this project is to aware people about enterprise application security problems and create guidelines and tools for enterprise application security assessment.
1 Aware people about enterprise application security vulnerabilities by releasing annual statistics of enterprise business application security vulnerabilities.
