Merge branch 'release/1.0.0'

Author: PauloASilva

2019/en/dist/owasp-api-security-top-10.odt

@@ -4,7 +4,7 @@ Notice
 This is the text version of OWASP API Security Top 10, used as source for the
 official version distributed as a Portable Document Format (PDF).
 
-Contributions to the project such as comments, corrections or translations
+Contributions to the project such as comments, corrections, or translations
 should be done here. For details on [How To Contribute][1], please refer to
 [CONTRIBUTING.md][1].
 

2019/en/dist/owasp-api-security-top-10.pdf

@@ -9,7 +9,7 @@ Table of Contents
 * [API Security Risks](0x10-api-security-risks.md)
 * [OWASP Top 10 API Security Risks – 2019](0x11-t10.md)
 * [API1:2019 Broken Object Level Authorization](0xa1-broken-object-level-authorization.md)
-* [API2:2019 Broken Authentication](0xa2-broken-authentication.md)
+* [API2:2019 Broken User Authentication](0xa2-broken-user-authentication.md)
 * [API3:2019 Excessive Data Exposure](0xa3-excessive-data-exposure.md)
 * [API4:2019 Lack of Resources & Rate Limiting](0xa4-lack-of-resources-and-rate-limiting.md)
 * [API5:2019 Broken Function Level Authorization](0xa5-broken-function-level-authorization.md)

2019/en/src/0x00-notice.md

@@ -13,7 +13,7 @@ become a target for attackers. Without secure APIs, rapid innovation would be
 impossible.
 
 Although a broader web application security risks Top 10 still makes sense, due
-to their particular nature, an API specific security risks list is required.
+to their particular nature, an API-specific security risks list is required.
 API security focuses on strategies and solutions to understand and mitigate the
 unique vulnerabilities and security risks associated with APIs.
 

2019/en/src/0x00-toc.md

@@ -20,7 +20,7 @@ architects, managers, or organizations.
 In the [Methodology and Data][2] section, you can read more about how this first
 edition was created. In future versions, we want to involve the security
 industry, with a public call for data. For now, we encourage everyone to
-contribute with questions, comments and ideas at our [GitHub repository][3] or
+contribute with questions, comments, and ideas at our [GitHub repository][3] or
 [Mailing list][4].
 
 [1]: https://www.owasp.org/index.php/OWASP_API_Security_Project

2019/en/src/0x02-foreword.md

@@ -10,13 +10,13 @@ section, you'll find more details about how this version was built. For more
 details about the security risks, please refer to the [API Security Risks][2]
 section.
 
-It is important to realize that over the last few years, applications'
-architecture has significantly changed. Currently, APIs play a very important
+It is important to realize that over the last few years, architecture of 
+applications has significantly changed. Currently, APIs play a very important
 role in this new architecture of microservices, Single Page Applications (SPAs),
 mobile apps, IoT, etc.
 
 The OWASP API Security Top 10 was a required effort to create awareness about
-modern APIs security issues. It was only possible due to a great effort of
+modern API security issues. It was only possible due to a great effort of
 several volunteers, all of them listed in the [Acknowledgments][3] section.
 Thank you!
 

2019/en/src/0x03-introduction.md

@@ -4,12 +4,12 @@ OWASP Top 10 API Security Risks – 2019
 | Risk | Description |
 | ---- | ----------- |
 | API1:2019 - Broken Object Level Authorization | APIs tend to expose endpoints that handle object identifiers, creating a wide attack surface Level Access Control issue. Object level authorization checks should be considered in every function that accesses a data source using an input from the user. |
-| API2:2019 - Broken Authentication | Authentication mechanisms are often implemented incorrectly, allowing attackers to compromise authentication tokens or to exploit implementation flaws to assume other user's identities temporarily or permanently. Compromising system's ability to identify the client/user, compromises API security overall. |
+| API2:2019 - Broken User Authentication | Authentication mechanisms are often implemented incorrectly, allowing attackers to compromise authentication tokens or to exploit implementation flaws to assume other user's identities temporarily or permanently. Compromising system's ability to identify the client/user, compromises API security overall. |
 | API3:2019 - Excessive Data Exposure | Looking forward to generic implementations, developers tend to expose all object properties without considering their individual sensitivity, relying on clients to perform the data filtering before displaying it to the user. |
 | API4:2019 - Lack of Resources & Rate Limiting | Quite often, APIs do not impose any restrictions on the size or number of resources that can be requested by the client/user. Not only can this impact the API server performance, leading to Denial of Service (DoS), but also leaves the door open to authentication flaws such as brute force. |
 | API5:2019 - Broken Function Level Authorization | Complex access control policies with different hierarchies, groups, and roles, and an unclear separation between administrative and regular functions, tend to lead to authorization flaws. By exploiting these issues, attackers gain access to other users’ resources and/or administrative functions. |
 | API6:2019 - Mass Assignment | Binding client provided data (e.g., JSON) to data models, without proper properties filtering based on a whitelist, usually lead to Mass Assignment. Either guessing objects properties, exploring other API endpoints, reading the documentation, or providing additional object properties in request payloads, allows attackers to modify object properties they are not supposed to. |
 | API7:2019 - Security Misconfiguration | Security misconfiguration is commonly a result of unsecure default configurations, incomplete or ad-hoc configurations, open cloud storage, misconfigured HTTP headers, unnecessary HTTP methods, permissive Cross-Origin resource sharing (CORS), and verbose error messages containing sensitive information. |
-| API8:2019 - Injection | Injection flaws, such as SQL, NoSQL, Command Injection, etc. occur when untrusted data is sent to an interpreter as part of a command or query. The attacker's malicious data can trick the interpreter into executing unintended commands or accessing data without proper authorization. |
+| API8:2019 - Injection | Injection flaws, such as SQL, NoSQL, Command Injection, etc., occur when untrusted data is sent to an interpreter as part of a command or query. The attacker's malicious data can trick the interpreter into executing unintended commands or accessing data without proper authorization. |
 | API9:2019 - Improper Assets Management | APIs tend to expose more endpoints than traditional web applications, making proper and updated documentation highly important. Proper hosts and deployed API versions inventory also play an important role to mitigate issues such as deprecated API versions and exposed debug endpoints. |
 | API10:2019 - 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 to tamper with, extract, or destroy data. Most breach studies demonstrate the time to detect a breach is over 200 days, typically detected by external parties rather than internal processes or monitoring. |

2019/en/src/0x04-release-notes.md

@@ -44,9 +44,6 @@ modify other users' account data.
 
 * Implement a proper authorization mechanism that relies on the user policies
   and hierarchy.
-* Prefer not to use an ID that has been sent from the client, but instead use an
-  ID that is stored in the session object when accessing a database record by
-  the record ID.
 * Use an authorization mechanism to check if the logged-in user has access to
   perform the requested action on the record in every function that uses an
   input from the client to access a record in the database.

2019/en/src/0x11-t10.md

@@ -1,5 +1,5 @@
-API2:2019 Broken Authentication
-===============================
+API2:2019 Broken User Authentication
+====================================
 
 | Threat agents/Attack vectors | Security Weakness | Impacts |
 | - | - | - |
@@ -15,17 +15,16 @@ mechanisms.
 An API is vulnerable if it:
 * Permits [credential stuffing][1] whereby the attacker has a list of valid
   usernames and passwords.
-* Permits attackers to perform a brute force attack on the same user, without
-  presenting captcha / account lockout mechanism.
+* Permits attackers to perform a brute force attack on the same user account, without
+  presenting captcha/account lockout mechanism.
 * Permits weak passwords.
-* Sends sensitive authentication details, such as auth tokens and password in
+* Sends sensitive authentication details, such as auth tokens and passwords in
   the URL.
 * Doesn’t validate the authenticity of tokens.
-* Accepts unsigned / weakly signed JWT tokens (`"alg":"none"`) / doesn’t
+* Accepts unsigned/weakly signed JWT tokens (`"alg":"none"`)/doesn’t
   validate their expiration date.
 * Uses plain text, encrypted, or weakly hashed passwords.
-* Uses weak encryption keys / API keys.
-
+* Uses weak encryption keys.
 
 ## Example Attack Scenarios
 
@@ -49,23 +48,23 @@ within a few minutes.
 ## How To Prevent
 
 * Make sure you know all the possible flows to authenticate to the API (mobile/
-  web/deep links that implement one-click authentication/etc)
+  web/deep links that implement one-click authentication/etc.)
 * Ask your engineers what flows you missed.
 * Read about your authentication mechanisms. Make sure you understand what and
-  how they are used. OAuth is not authentication, and neither API keys .
+  how they are used. OAuth is not authentication, and neither is API keys.
 * Don't reinvent the wheel in authentication, token generation, password
   storage. Use the standards.
-* Credential recovery / forget password endpoints should be treated as login
-  endpoints in terms of brute force, rate limiting and lockout protections.
-* Use the [OWASP Authentication Cheatsheet][3]
+* Credential recovery/forget password endpoints should be treated as login
+  endpoints in terms of brute force, rate limiting, and lockout protections.
+* Use the [OWASP Authentication Cheatsheet][3].
 * Where possible, implement multi-factor authentication.
 * Implement anti brute force mechanisms to mitigate credential stuffing,
-  dictionary attack and brute force attacks on your authentication endpoints.
-  This mechanism should be  stricter than the regular rate limiting mechanism on
+  dictionary attack, and brute force attacks on your authentication endpoints.
+  This mechanism should be stricter than the regular rate limiting mechanism on
   your API.
 * Implement [account lockout][4] / captcha mechanism to prevent brute force
   against specific users. Implement weak-password checks.
-* API keys should not be used for user authentication, but for [client app /
+* API keys should not be used for user authentication, but for [client app/
   project authentication][5].
 
 ## References