-
Notifications
You must be signed in to change notification settings - Fork 72
Commit
- Loading branch information
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,9 @@ | ||
# About OWASP | ||
|
||
!!! warning "New Version Available!" | ||
|
||
You are looking at the legacy 2018 version of the OWASP Top 10 Proactive Controls. The current version is the [OWASP Top 10 Proactive Controls 2024](./../2024/introduction/about-owasp.md)! | ||
Check failure on line 5 in docs/archive/2018/0x01-about-owasp.md GitHub Actions / Lint markdownLine length
|
||
|
||
The *Open Web Application Security Project* (OWASP) is a 501c3 non for profit educational charity dedicated to enabling organizations to design, develop, acquire, operate, and maintain secure software. All OWASP tools, documents, forums, and chapters are free and open to anyone interested in improving application security. We can be found at [www.owasp.org](https://www.owasp.org). | ||
|
||
OWASP is a new kind of organization. Our freedom from commercial pressures allows us to provide unbiased, practical, cost effective information about application security. | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,9 @@ | ||
# About this Project | ||
|
||
!!! warning "New Version Available!" | ||
|
||
You are looking at the legacy 2018 version of the OWASP Top 10 Proactive Controls. The current version is the [OWASP Top 10 Proactive Controls 2024](./../2024/index.md)! | ||
Check failure on line 5 in docs/archive/2018/0x02-about-project.md GitHub Actions / Lint markdownLine length
|
||
|
||
Insecure software is undermining our financial, healthcare, defense, energy, and other critical infrastructure worldwide. As our digital, global infrastructure gets increasingly complex and interconnected, the difficulty of achieving application security increases exponentially. We can no longer afford to tolerate relatively simple security problems. | ||
|
||
## Aim & Objective | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,9 @@ | ||
# Document Structure | ||
|
||
!!! warning "New Version Available!" | ||
|
||
You are looking at the legacy 2018 version of the OWASP Top 10 Proactive Controls. The current version is the [OWASP Top 10 Proactive Controls 2024](./../2024/index.md)! | ||
Check failure on line 5 in docs/archive/2018/0x03-about-structure.md GitHub Actions / Lint markdownLine length
|
||
|
||
This document is structured as a list of security controls. Each control is described as follows: | ||
|
||
## Cx: Control Name | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,9 @@ | ||
# Introduction | ||
|
||
!!! warning "New Version Available!" | ||
|
||
You are looking at the legacy 2018 version of the OWASP Top 10 Proactive Controls. The current version is the [OWASP Top 10 Proactive Controls 2024](./../2024/the-top-10/index.md)! | ||
Check failure on line 5 in docs/archive/2018/0x04-introduction.md GitHub Actions / Lint markdownLine length
|
||
|
||
The OWASP Top Ten Proactive Controls 2018 is a list of security techniques that should be considered for every software development project. This document is written for developers to assist those new to secure development. | ||
|
||
One of the main goals of this document is to provide concrete practical guidance that helps developers build secure software. These techniques should be applied proactively at the early stages of software development to ensure maximum effectiveness. | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,9 @@ | ||
# C1: Define Security Requirements | ||
|
||
!!! warning "New Version of the Control Available!" | ||
|
||
You are looking at the legacy 2018 version of the OWASP Top 10 Proactive Controls. You can find information about the same control within the [OWASP Top 10 Proactive Controls 2024](./../2024/index.md) within [C4: Address Security from the Start](./../2024/the-top-10/c4-secure-architecture.md)! | ||
Check failure on line 5 in docs/archive/2018/c1-security-requirements.md GitHub Actions / Lint markdownLine length
|
||
|
||
## Description | ||
|
||
A security requirement is a statement of needed security functionality that ensures one of many different security properties of software is being satisfied. Security requirements are derived from industry standards, applicable laws, and a history of past vulnerabilities. Security requirements define new features or additions to existing features to solve a specific security problem or eliminate a potential vulnerability. | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,9 @@ | ||
# C10: Handle all Errors and Exceptions | ||
|
||
!!! warning "New Version of the Control Available!" | ||
|
||
You are looking at the legacy 2018 version of the OWASP Top 10 Proactive Controls. You can find information about the same control within the [OWASP Top 10 Proactive Controls 2024](./../2024/index.md) within [C3: Validate all Input & Handle Exceptions](./../2024/the-top-10/c3-validate-input-and-handle-exceptions.md)! | ||
Check failure on line 5 in docs/archive/2018/c10-errors-exceptions.md GitHub Actions / Lint markdownLine length
|
||
|
||
## Description | ||
|
||
Exception handling is a programming concept that allows an application to respond to different error states (like network down, or database connection failed, etc) in various ways. Handling exceptions and errors correctly is critical to making your code reliable and secure. | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,9 @@ | ||
# C2: Leverage Security Frameworks and Libraries | ||
|
||
!!! warning "New Version of the Control Available!" | ||
|
||
You are looking at the legacy 2018 version of the OWASP Top 10 Proactive Controls. You can find information about the same control within the [OWASP Top 10 Proactive Controls 2024](./../2024/index.md) within [C6: Keep your Components Secure](./../2024/the-top-10/c6-use-secure-dependencies.md)! | ||
Check failure on line 5 in docs/archive/2018/c2-leverage-security-frameworks-libraries.md GitHub Actions / Lint markdownLine length
|
||
|
||
## Description | ||
|
||
Secure coding libraries and software frameworks with embedded security help software developers guard against security-related design and implementation flaws. A developer writing an application from scratch might not have sufficient knowledge, time, or budget to properly implement or maintain security features. Leveraging security frameworks helps accomplish security goals more efficiently and accurately. | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,9 @@ | ||
# C3: Secure Database Access | ||
|
||
!!! warning "New Version of the Control Available!" | ||
|
||
You are looking at the legacy 2018 version of the OWASP Top 10 Proactive Controls. You can find information about the same control within the [OWASP Top 10 Proactive Controls 2024](./../2024/index.md) within [C3: Validate all Input & Handle Exceptions](./../2024/the-top-10/c3-validate-input-and-handle-exceptions.md)! | ||
Check failure on line 5 in docs/archive/2018/c3-secure-database.md GitHub Actions / Lint markdownLine length
|
||
|
||
## Description | ||
|
||
This section describes secure access to all data stores, including both relational databases and NoSQL databases. Some areas to consider: | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,9 @@ | ||
# C4: Encode and Escape Data | ||
|
||
!!! warning "New Version of the Control Available!" | ||
|
||
You are looking at the legacy 2018 version of the OWASP Top 10 Proactive Controls. You can find information about the same control within the [OWASP Top 10 Proactive Controls 2024](./../2024/index.md) within [C3: Validate all Input & Handle Exceptions](./../2024/the-top-10/c3-validate-input-and-handle-exceptions.md)! | ||
Check failure on line 5 in docs/archive/2018/c4-encode-escape-data.md GitHub Actions / Lint markdownLine length
|
||
|
||
## Description | ||
|
||
**Encoding** and escaping are defensive techniques meant to stop injection attacks. Encoding (commonly called "Output Encoding") involves translating special characters into some different but equivalent form that is no longer dangerous in the target interpreter, for example translating the ``<`` character into the ``<`` string when writing to an HTML page. **Escaping** involves adding a special character before the character/string to avoid it being misinterpreted, for example, adding a ``\`` character before a ``"`` (double quote) character so that it is interpreted as text and not as closing a string. | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,9 @@ | ||
# C5: Validate All Inputs | ||
|
||
!!! warning "New Version of the Control Available!" | ||
|
||
You are looking at the legacy 2018 version of the OWASP Top 10 Proactive Controls. You can find information about the same control within the [OWASP Top 10 Proactive Controls 2024](./../2024/index.md) within [C3: Validate all Input & Handle Exceptions](./../2024/the-top-10/c3-validate-input-and-handle-exceptions.md)! | ||
Check failure on line 5 in docs/archive/2018/c5-validate-inputs.md GitHub Actions / Lint markdownLine length
|
||
|
||
## Description | ||
|
||
Input validation is a programming technique that ensures only properly formatted data may enter a software system component. | ||
|