8
www.fortinet.com 1 White Paper FortiWeb and the OWASP Top 10 2013 Mitigating the most dangerous application security threats Introduction The Open Web Application Security project (OWASP) Top Ten provides a powerful awareness document for web application security. The OWASP Top Ten represents a broad consensus about what the most critical web application security flaws are as identified by a variety of security experts from around the world who have shared their expertise to produce this list. The U.S. Federal Trade Commission strongly recommends that all companies use the OWASP Top Ten and ensure that their partners do the same. In addition, the U.S. Defense Information Systems Agency has listed the OWASP Top Ten as key for best practices. In the commercial market, the Payment Card Industry (PCI) standard has adopted the OWASP Top Ten and lists it as a key requirement as part of section 6 – “Develop and maintain secure systems and applications” mandating that all web applications be developed according to security guidelines to protect against the OWASP Top 10. OWASP TOP 10 2013 Changes The OWASP team updates the Top 10 list periodically as the threat landscape changes, new technologies released, attack vectors are changed and utilized differently, and new weaknesses found. These are the changes introduced in the 2013 release as taken from the OWASP release notes (https://www.owasp.org/index.php/Top_10_2013-Release_Notes) Broken Authentication and Session Management moved up in prevalence based on our data set. This area is being looked at harder, not because issues are actually more prevalent. This caused Risks A2 and A3 to switch places. Cross-Site Request Forgery (CSRF) moved down in prevalence based on our data set from 2010-A5 to 2013-A8. We believe this is because CSRF has been in the OWASP Top 10 for 6 years, and organizations and framework developers have focused on it enough to significantly reduce the number of CSRF vulnerabilities in real world applications. We broadened Failure to Restrict URL Access from the 2010 OWASP Top 10 to be more inclusive. 2010-A8: Failure to Restrict URL Access is now 2013-A7: Missing Function Level Access Control – to cover all of function level access control. There are many ways to specify which function is being accessed, not just the URL. We merged and broadened 2010-A7 & 2010-A9 to CREATE 2013-A6, Sensitive Data Exposure. This new category was created by merging 2010-A7 – Insecure Cryptographic Storage & 2010-A9 - Insufficient Transport Layer Protection, plus adding browser side sensitive data risks as

OWASP Top 10 2013 WP v4 - MSInfokom · to protect against the OWASP Top 10. OWASP TOP 10 2013 Changes ... 2010-A5 to 2013-A8. ... Security Misconfiguration, but now has a category

  • Upload
    others

  • View
    11

  • Download
    0

Embed Size (px)

Citation preview

Page 1: OWASP Top 10 2013 WP v4 - MSInfokom · to protect against the OWASP Top 10. OWASP TOP 10 2013 Changes ... 2010-A5 to 2013-A8. ... Security Misconfiguration, but now has a category

www.fortinet.com 1

White Paper

FortiWeb and the OWASP Top 10 2013 Mitigating the most dangerous application security threats

Introduction

The Open Web Application Security project (OWASP) Top Ten provides a powerful awareness document for web application security. The OWASP Top Ten represents a broad consensus about what the most critical web application security flaws are as identified by a variety of security experts from around the world who have shared their expertise to produce this list.

The U.S. Federal Trade Commission strongly recommends that all companies use the OWASP Top Ten and ensure that their partners do the same. In addition, the U.S. Defense Information Systems Agency has listed the OWASP Top Ten as key for best practices.

In the commercial market, the Payment Card Industry (PCI) standard has adopted the OWASP Top Ten and lists it as a key requirement as part of section 6 – “Develop and maintain secure systems and applications” mandating that all web applications be developed according to security guidelines to protect against the OWASP Top 10.

OWASP TOP 10 2013 Changes

The OWASP team updates the Top 10 list periodically as the threat landscape changes, new technologies released, attack vectors are changed and utilized differently, and new weaknesses found. These are the changes introduced in the 2013 release as taken from the OWASP release notes (https://www.owasp.org/index.php/Top_10_2013-Release_Notes)

Broken Authentication and Session Management moved up in prevalence based on our data set. This area is being looked at harder, not because issues are actually more prevalent. This caused Risks A2 and A3 to switch places.

Cross-Site Request Forgery (CSRF) moved down in prevalence based on our data set from 2010-A5 to 2013-A8. We believe this is because CSRF has been in the OWASP Top 10 for 6 years, and organizations and framework developers have focused on it enough to significantly reduce the number of CSRF vulnerabilities in real world applications.

We broadened Failure to Restrict URL Access from the 2010 OWASP Top 10 to be more inclusive. 2010-A8: Failure to Restrict URL Access is now 2013-A7: Missing Function Level Access Control – to cover all of function level access control. There are many ways to specify which function is being accessed, not just the URL.

We merged and broadened 2010-A7 & 2010-A9 to CREATE 2013-A6, Sensitive Data Exposure. This new category was created by merging 2010-A7 – Insecure Cryptographic Storage & 2010-A9 - Insufficient Transport Layer Protection, plus adding browser side sensitive data risks as

Page 2: OWASP Top 10 2013 WP v4 - MSInfokom · to protect against the OWASP Top 10. OWASP TOP 10 2013 Changes ... 2010-A5 to 2013-A8. ... Security Misconfiguration, but now has a category

White Paper: OWASP Top 10 2013

www.fortinet.com 2

well. This new category covers sensitive data protection (other than access control which is covered by 2013-A4 and 2013-A7) from the moment sensitive data is provided by the user, sent to and stored within the application, and then sent back to the browser again.

We added: 2013-A9: Using Components with Known Vulnerabilities. This issue was mentioned as part of 2010-A6 – Security Misconfiguration, but now has a category of its own as the growth and depth of component based development has significantly increased the risk of using components with known vulnerabilities.

Web Application Security Challenges

Web applications are attractive targets to hackers as often they are public facing applications that are required to be open to the Internet as they provide major e-commerce and business driving tools for organizations. Connected to backend databases web applications are perfect for hackers as these databases are the primary repository for cardholder data, company data and other sensitive information.

According to the SANS, attacks against web applications constitute more than 60% of the total attack attempts observed on the Internet. Web application vulnerabilities such as SQL injection and Cross-Site Scripting flaws in custom-built applications account for more than 80% of the vulnerabilities being discovered.

The difficulty in protecting web applications is their architecture and dynamics. While network security is simple–define security policies to allow/block traffic to/out of several applications consist of hundreds and sometimes thousands of different elements (URLs, parameters and cookies).

Manually creating different policies for each of these items is almost impossible and obviously does not scale. On top of this, web applications change frequently with new URLs and parameters being added making it difficult for security administrators to update their security policies.

FortiWeb Web Application Firewall

Combining both a Web Application Firewall, Web vulnerability scanner and a layer 7 load balancer in a single platform the FortiWeb solution allows enterprises to protect against application level attacks, help identifying application vulnerabilities in web applications while ensuring availability and accelerating application access with capabilities such as hardware SSL offload, compression and caching. Using advanced techniques to protect against SQL injection, Cross site scripting and a range of other attacks FortiWeb helps protect sensitive data and prevent identity theft, financial fraud and brand erosion which can result in significant damage while ensuring application availability.

FortiWeb provides flexible and reliable protection to address the OWASP Top Ten by utilizing a range of in-depth security modules and technologies. Sophisticated attacks are blocked using a multi-layered security approach. Incorporating a positive and a negative security module based on bi-directional traffic analysis and an embedded behavioral based anomaly detection engine FortiWeb can protect against a broad range of threats without the need for network re-architecture and application changes.

FortiWeb incorporates two security models in order to protect both known and unknown vulnerabilities:

Positive Security Model

FortiWeb uses Positive Security Model to protect against any known and unknown vulnerabilities. Once a new web application policy is defined, FortiWeb starts monitoring traffic flowing to the

Page 3: OWASP Top 10 2013 WP v4 - MSInfokom · to protect against the OWASP Top 10. OWASP TOP 10 2013 Changes ... 2010-A5 to 2013-A8. ... Security Misconfiguration, but now has a category

White Paper: OWASP Top 10 2013

www.fortinet.com 3

application and based on a behavioral analysis technology called Auto-Learn FortiWeb builds a dynamic baseline of allowed elements for the application. By analyzing normal user behavior FortiWeb understands how the web application should be accessed. Authorized URLs are created with the relevant parameters for each of the URLs. Parameter characteristics are profiled as well to provide an overall picture of the web application structure and what constitutes as normal user behavior.

The Auto-Learn profiling capability is completely transparent and does not require any changes to the application or network architecture. FortiWeb does not scan the application in order to build the profile, but rather analyzes the traffic as it monitors it flowing to the application.

By creating a comprehensive security model of the application FortiWeb can now protect against any known or unknown vulnerabilities, zero day attacks such as SQL Injection, Cross Site Scripting, and other application layer attacks. These types of attacks require manipulating URLs and parameters by inserting different characters that are not part of learned profiled and as such can be immediately blocked.

Figure 1 and 2 FortiWeb Traffic Analysis based on Positive Security Model

Negative Security Model

FortiWeb includes a full application signature dictionary to protect against known application layer attacks and application logic attacks. A sophisticated engine scans both inbound and outbound traffic, matching elements with pre-defined known exploits.

Page 4: OWASP Top 10 2013 WP v4 - MSInfokom · to protect against the OWASP Top 10. OWASP TOP 10 2013 Changes ... 2010-A5 to 2013-A8. ... Security Misconfiguration, but now has a category

White Paper: OWASP Top 10 2013

www.fortinet.com 4

FortiWeb provides an enhanced flexible engine that also allows customers to write their own signatures using a regular expression engine which provides the ability to create new and customized signatures for every application and vulnerability.

FortiWeb’s signature dictionary is updated regularly and automatically via FortiGuard Labs, a Security Subscription Service which delivers continuous, automated updates and offers dynamic protection based on the work of the Fortinet® Global Security Research Team, which researches and develops protection against known and potential security threats.

FortiWeb extends the negative security layer with an HTTP RFC enforcement layer making sure any access to the protected application is done according to the HTTP standard. FortiWeb provides an enhanced policy configuration with multiple rules to protect against buffer overflows, encoding based attacks and any other attack that tries to manipulate the HTTP protocol.

Figure 3 and 4: FortiWeb signature dictionaries and protocol constraints are part of the Negative Security Model

Page 5: OWASP Top 10 2013 WP v4 - MSInfokom · to protect against the OWASP Top 10. OWASP TOP 10 2013 Changes ... 2010-A5 to 2013-A8. ... Security Misconfiguration, but now has a category

White Paper: OWASP Top 10 2013

www.fortinet.com 5

Additional FortiWeb Functionality Helps Protect against OWASP Top 10

Data Leak Prevention and Information Disclosure

FortiWeb extends monitoring and protection to outgoing traffic such as credit card leakage and information disclosure. Providing multiple policies for information disclosure FortiWeb immediately alerts any web application abnormalities that may be caused by an attack or by poor application configuration. Rules can be extended to rewrite information disclosure such that users are not exposed to any sensitive application data. Additional credit card leakage rules make sure any outgoing traffic does not include credit card numbers.

FortiWeb also allows customers to create their own custom rules providing an entire solution for Data Leak Prevention.

Figure 5 FortiWeb Protects against Information Disclosure

Web Vulnerability Scanner

FortiWeb is the only vendor that provides a Vulnerability Scanner module within the web application firewall that automatically scans and analyzes the protected web applications and detects security weaknesses, known and unknown vulnerabilities.

Together with the web application firewall FortiWeb completes a comprehensive solution for PCI DSS requirement 6.6 and 6.5 allowing organizations to scan their applications, identify vulnerabilities and protect them in real time from the same platform.

Page 6: OWASP Top 10 2013 WP v4 - MSInfokom · to protect against the OWASP Top 10. OWASP TOP 10 2013 Changes ... 2010-A5 to 2013-A8. ... Security Misconfiguration, but now has a category

White Paper: OWASP Top 10 2013

www.fortinet.com 6

Figure 6 FortiWeb’s Vulnerability Scanner

Page Access and Start Page Enforcement

Enforcing access to the application according to the correct business logic is an important part of web application security. Applications that do not enforce this open themselves to Cross Site Request Forgery (CSRF) attacks. For example, e-commerce applications should not allow access to the shipping or payments stage directly, without prior access to the ordering pages.

By defining a Page Access rule on FortiWeb CSRF attacks are immediately blocked helping with OWASP Top Ten A5 requirement.

Additionally, FortiWeb offers a Start Page policy as well which defines the entry point to the application helping with requests that try to circumvent authentication or any other environment that requires users to start browsing at a specific page.

Page 7: OWASP Top 10 2013 WP v4 - MSInfokom · to protect against the OWASP Top 10. OWASP TOP 10 2013 Changes ... 2010-A5 to 2013-A8. ... Security Misconfiguration, but now has a category

White Paper: OWASP Top 10 2013

www.fortinet.com 7

OWASP Top Ten and FortiWeb Mitigation Technique

The table below lists the OWASP Top Ten and the corresponding FortiWeb mitigation techniques.

OWASP Top 10 Explanation FortiWeb Mitigation

A1. Injection

Injection flaws, such as SQL, 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 unauthorized data.

Auto-Learn profiling automatically builds an allowed baseline to provide comprehensive request validation capability to enforce strict URL and parameter control. Enhanced application signature detection engine updated regularly by the FortiGuard Labs team adds a secondary layer for abnormal characters and known injection strings.

A2. Broken Authentication and Session Management

Application functions related to authentication and session management are often not implemented correctly, allowing attackers to compromise passwords, keys, session tokens, or exploit other implementation flaws to assume other users’ identities.

FortiWeb enforces session management with strict cookie control by tracking all sessions and cookies. Any attempt to compromise cookies is mitigated. Additionally various Authentication Offload capabilities (supporting Local, LDAP and NTLM) are included to offer additional security layer.

A3. Cross-Site Scripting (XSS)

XSS flaws occur whenever an application takes untrusted data and sends it to a web browser without proper validation and escaping. 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.

FortiWeb application signature layer engine includes various XSS signatures to protect against the most sophisticated XSS attacks. Additionally, FortiWeb’s Auto-Learn builds a comprehensive baseline of normal behavior such as URLs and parameters. Any attempt to inject illegal and unknown characters to arguments can be immediately blocked.

A4. Insecure Direct Object References

A direct object reference occurs when a developer exposes a reference to an internal implementation object, such as a file, directory, or database key. Without an access control check or other protection, attackers can manipulate these references to access unauthorized data.

Auto-Learn profiling builds a comprehensive profile of allowed elements within the application. Any attempt to manipulate a parameter will trigger an alert and immediately be blocked. Hidden Fields Rules detect and block any attempt by the client to alter a hidden parameter value.

A5. Security Misconfiguration

Good security requires having a secure configuration defined and deployed for the application, frameworks, application server, web server, database server, and platform. Secure settings should be defined, implemented, and maintained, as defaults are often insecure. Additionally, software should be kept up to date.

1) Using Auto-Learn FortiWeb will block any attempt made by an attacker to exploit a misconfigured web application. 2) Through monitoring application responses, FortiWeb is able to identify any application failure. 3) Vulnerability Scanner module scans the protected applications, finds inherent misconfigurations and quickly turns them to security rules.

A6. Sensitive Data Exposure

Many web applications do not properly protect sensitive data, such as credit cards, tax IDs, and authentication credentials. Attackers may steal or modify such weakly protected data to conduct credit card fraud, identity theft, or other crimes. Sensitive data deserves extra protection such as encryption at rest or in transit, as well as special precautions when exchanged with the browser.

FortiWeb protects against attacks that lead to sensitive data exposure such as SQL Injection and other injection types. Additionally, FortiWeb inspects all web server outgoing traffic for sensitive data such as Social Security numbers, credit card number and other predefined or custom based sensitive data. When identified, FortiWeb can either mask the data or block it from reaching the client all together

A7. Missing Function Level Access Control

Most web applications verify function level access rights before making that functionality visible in the UI. However, applications need to perform the same access control checks on the server when each function is accessed. If requests are not verified, attackers will be able to forge requests in order to access functionality without proper authorization.

FortiWeb validates sessions and any attempt to manipulate it to gain unauthorized or elevated application access control. FortiWeb can also perform authentication with local or RADIUS and LDAP servers to provide another security layer

Page 8: OWASP Top 10 2013 WP v4 - MSInfokom · to protect against the OWASP Top 10. OWASP TOP 10 2013 Changes ... 2010-A5 to 2013-A8. ... Security Misconfiguration, but now has a category

White Paper: OWASP Top 10 2013

www.fortinet.com 8

A8. Cross-Site Request Forgery (CSRF)

A CSRF attack forces a logged-on victim’s browser to send a forged HTTP request, including the victim’s session cookie and any other automatically included authentication information, to a vulnerable web application. This allows the attacker to force the victim’s browser to generate requests the vulnerable application thinks are legitimate requests from the victim.

Strict reference page enforcing provides protection against sophisticated CSRF attacks. Also, page access rules allow customers to define URL order. Common CSRF attacks attempt to submit a specific crafted request. For example, FortiWeb enforces a page order sequence that will block the request if it didn’t go through the proper payment order sequence and as such - invalid.

A9. Using Components With Known Vulnerabilities

Components, such as libraries, frameworks, and other software modules, almost always run with full privileges. If a vulnerable component is exploited, such an attack can facilitate serious data loss or server takeover. Applications using components with known vulnerabilities may undermine application defenses and enable a range of possible attacks and impacts.

FortiGuard Labs continuously update FortiWeb’s signature layer with new signatures to virtually patch newly discovered vulnerabilities. With FortiWeb’s Auto Learn functionality creating a baseline of normal user behavior and its Protocol constraints layer FortiWeb can protect against zero day attacks exploiting vulnerabilities yet to be discovered

A10.Unvalidated Redirects and Forwards

Web applications frequently redirect and forward users to other pages and websites, and use untrusted data to determine the destination pages. Without proper validation, attackers can redirect victims to phishing or malware sites, or use forwards to access unauthorized pages.

Auto-Learn profiling identifies when parameters are used in a different manner then supposed to. Validation enforcement makes sure characters that are usually associated with redirects and forwards are not allowed as part application usage.

Summary

The OWASP Top Ten provides a great starting point for customers to measure their application security and prioritize their risk. Mandated by the Payment Card Industry (PCI) standard as a key requirement as part of section 6 and widely adopted by many organizations the OWASP Top 10 is an important guideline that helps organizations focus on application security.

FortiWeb’s integrated Web Application Firewall and Vulnerability assessment scanner allow customers to protect against high-risk attacks such as defined in the OWASP Top Ten and many others.

GLOBAL HEADQUARTERSFortinet Inc.899 Kifer RoadSunnyvale, CA 94086United StatesTel: +1.408.235.7700Fax: +1.408.235.7737www.fortinet.com/sales

EMEA SALES OFFICE120 rue Albert Caquot06560, Sophia Antipolis, FranceTel: +33.4.8987.0510Fax: +33.4.8987.0501

APAC SALES OFFICE300 Beach Road 20-01The ConcourseSingapore 199555Tel: +65.6513.3730Fax: +65.6223.6784

LATIN AMERICA SALES OFFICEProl. Paseo de la Reforma 115 Int. 702Col. Lomas de Santa Fe,C.P. 01219 Del. Alvaro ObregónMéxico D.F.Tel: 011-52-(55) 5524-8480

Copyright© 2014 Fortinet, Inc. All rights reserved. Fortinet®, FortiGate®, FortiCare® and FortiGuard®, and certain other marks are registered trademarks of Fortinet, Inc., and other Fortinet names herein may also be registered and/or common law trademarks of Fortinet. All other product or company names may be trademarks of their respective owners. Performance and other metrics contained herein were attained in internal lab tests under ideal conditions, and actual performance and other results may vary. Network variables, different network environments and other conditions may affect performance results. Nothing herein represents any binding commitment by Fortinet, and Fortinet disclaims all warranties, whether express or implied, except to the extent Fortinet enters a binding written contract, signed by Fortinet’s *HQHUDO�&RXQVHO��ZLWK�D�SXUFKDVHU�WKDW�H[SUHVVO\�ZDUUDQWV�WKDW�WKH�LGHQWL¿HG�SURGXFW�ZLOO�SHUIRUP�DFFRUGLQJ�WR�FHUWDLQ�H[SUHVVO\�LGHQWL¿HG�SHUIRUPDQFH�PHWULFV�DQG��LQ�VXFK�HYHQW��RQO\�WKH�VSHFL¿F�SHUIRUPDQFH�PHWULFV�H[SUHVVO\�LGHQWL¿HG�LQ�VXFK�ELQGLQJ�ZULWWHQ�FRQWUDFW�VKDOO�EH�ELQGLQJ�RQ�)RUWLQHW��)RU�DEVROXWH�FODULW\��DQ\�VXFK�ZDUUDQW\�ZLOO�EH�OLPLWHG�WR�SHUIRUPDQFH�LQ�WKH�VDPH�LGHDO�FRQGLWLRQV�DV�LQ�)RUWLQHW¶V�LQWHUQDO�lab tests. Fortinet disclaims in full any covenants, representations, and guarantees pursuant hereto, whether express or implied. Fortinet reserves the right to change, modify, transfer, or otherwise revise this publication without notice, and the most current version of the publication shall be applicable.