owasp-id · appsecasia · Nov 22, 2024 · Nov 23, 2024 · Nov 23, 2024 · Nov 23, 2024
diff --git a/.gitignore b/.gitignore
@@ -71,10 +71,27 @@ $RECYCLE.BIN/
 # IDE folders
 .idea/
 
+# Python Cache files
+__pycache__/
+*.py[cod]
+
+# Python virtual environments
+venv/
+.env
+.env.*
+
+generated/
+bin/
+lib/
+
 # mkdocs site (this is built using mkdocs gh-deploy
-2021/site/
-2021/site/0x00-notice/index.html
+*/site/
+
+# mkdocs build output (contains nested git repo for gh-pages deployment)
+build/
 
 # Pipenv
 Pipfile
-2021/site/0x00-notice/index.html
+
+# osib library
+osib
diff --git a/.vscode/settings.json b/.vscode/settings.json
@@ -0,0 +1,3 @@
+{
+    "makefile.configureOnOpen": false
+}
diff --git a/...WebApplicationSecurityTopTen-Version1.pdf → ...WebApplicationSecurityTopTen-Version1.pdf b/...WebApplicationSecurityTopTen-Version1.pdf → ...WebApplicationSecurityTopTen-Version1.pdf
diff --git a/2004/OWASP_Top_Ten_2004.doc b/2004/OWASP_Top_Ten_2004.doc
diff --git a/2004/OWASP_Top_Ten_2004.docx b/2004/OWASP_Top_Ten_2004.docx
diff --git a/2004/OWASP_Top_Ten_2004.odt b/2004/OWASP_Top_Ten_2004.odt
diff --git a/archives/OWASP_Top_Ten_2004.pdf → 2004/OWASP_Top_Ten_2004.pdf b/archives/OWASP_Top_Ten_2004.pdf → 2004/OWASP_Top_Ten_2004.pdf
diff --git a/2004/OWASP_Top_Ten_2004_Chinese.pdf b/2004/OWASP_Top_Ten_2004_Chinese.pdf
diff --git a/2004/OWASP_Top_Ten_2004_French.doc b/2004/OWASP_Top_Ten_2004_French.doc
diff --git a/2004/OWASP_Top_Ten_2004_French.pdf b/2004/OWASP_Top_Ten_2004_French.pdf
diff --git a/2004/OWASP_Top_Ten_2004_Japanese.doc b/2004/OWASP_Top_Ten_2004_Japanese.doc
diff --git a/2004/OWASP_Top_Ten_2004_Japanese.pdf b/2004/OWASP_Top_Ten_2004_Japanese.pdf
diff --git a/2004/OWASP_Top_Ten_2004_Korean.doc b/2004/OWASP_Top_Ten_2004_Korean.doc
diff --git a/2004/OWASP_Top_Ten_2004_Spanish.pdf b/2004/OWASP_Top_Ten_2004_Spanish.pdf
diff --git a/2007/OWASP Top 10 2007.doc b/2007/OWASP Top 10 2007.doc
diff --git a/2007/OWASP Top 10 2007.docx b/2007/OWASP Top 10 2007.docx
diff --git a/2007/OWASP Top 10 2007.pdf b/2007/OWASP Top 10 2007.pdf
diff --git a/2007/OWASP_Top_10_2007_Korean.doc b/2007/OWASP_Top_10_2007_Korean.doc
diff --git a/2007/OWASP_Top_10_2007_Korean.pdf b/2007/OWASP_Top_10_2007_Korean.pdf
diff --git a/2007/Presentations/OWASP Intro and Top 10.ppt b/2007/Presentations/OWASP Intro and Top 10.ppt
diff --git a/2007/Presentations/OWASP Intro and Top 10.pptx b/2007/Presentations/OWASP Intro and Top 10.pptx
diff --git a/2007/data/2006 issues.xls b/2007/data/2006 issues.xls
diff --git a/2007/data/2006 issues.xlsx b/2007/data/2006 issues.xlsx
diff --git a/2007/data/OWASP Top Ten Survey.doc b/2007/data/OWASP Top Ten Survey.doc
diff --git a/2007/data/vtrend-ALL.html b/2007/data/vtrend-ALL.html
diff --git a/2007/drafts/OWASP Top 10 2007 RC1.doc b/2007/drafts/OWASP Top 10 2007 RC1.doc
diff --git a/2007/drafts/OWASP Top 10 2007 RC2.doc b/2007/drafts/OWASP Top 10 2007 RC2.doc
diff --git a/2007/drafts/OWASP Top 10 2007 dw.doc b/2007/drafts/OWASP Top 10 2007 dw.doc
diff --git a/2007/drafts/OWASP Top 10 2007.doc b/2007/drafts/OWASP Top 10 2007.doc
diff --git a/2007/drafts/OWASP Top 10 RC2 to Final redline.doc b/2007/drafts/OWASP Top 10 RC2 to Final redline.doc
diff --git a/2007/drafts/OWASP Top 10 RC2.pdf b/2007/drafts/OWASP Top 10 RC2.pdf
diff --git a/2007/drafts/OWASP Top 10 RC3 post dw.docx b/2007/drafts/OWASP Top 10 RC3 post dw.docx
diff --git a/2007/drafts/OWASP Top 10 RC3.docx b/2007/drafts/OWASP Top 10 RC3.docx
diff --git a/2007/drafts/OWASP Top 10 post dw sc.docx b/2007/drafts/OWASP Top 10 post dw sc.docx
diff --git a/2007/drafts/OWASP Top 10.docx b/2007/drafts/OWASP Top 10.docx
diff --git a/2007/drafts/OWASP_Top_10_2007_RC2 dw.doc b/2007/drafts/OWASP_Top_10_2007_RC2 dw.doc
diff --git a/2007/drafts/OWASP_Top_10_2007_RC2-christey.doc b/2007/drafts/OWASP_Top_10_2007_RC2-christey.doc
diff --git a/2007/drafts/owasp-top10-rc1-christey.doc b/2007/drafts/owasp-top10-rc1-christey.doc
diff --git a/2010/OWASP Top 10 - 2010 English.pdf b/2010/OWASP Top 10 - 2010 English.pdf
diff --git a/2010/OWASP Top 10 - 2010 French.pdf b/2010/OWASP Top 10 - 2010 French.pdf
diff --git a/2010/OWASP Top 10 - 2010 Indonesian.pdf b/2010/OWASP Top 10 - 2010 Indonesian.pdf
diff --git a/2010/OWASP Top 10 - 2010 Japanese-A4.pdf b/2010/OWASP Top 10 - 2010 Japanese-A4.pdf
diff --git a/2010/OWASP Top 10 - 2010 Korean.pdf b/2010/OWASP Top 10 - 2010 Korean.pdf
diff --git a/2010/OWASP Top 10 - 2010 Spanish.pdf b/2010/OWASP Top 10 - 2010 Spanish.pdf
diff --git a/2010/OWASP Top 10 2010 Chinese.pdf b/2010/OWASP Top 10 2010 Chinese.pdf
diff --git a/2010/OWASP Top 10 2010 German.pdf b/2010/OWASP Top 10 2010 German.pdf
diff --git a/2010/OWASP Top 10 2010 Hebrew.pdf b/2010/OWASP Top 10 2010 Hebrew.pdf
diff --git a/2010/OWASP Top 10 2010 Italian.pdf b/2010/OWASP Top 10 2010 Italian.pdf
diff --git a/2010/OWASP Top 10 2010 Spanish.pdf b/2010/OWASP Top 10 2010 Spanish.pdf
diff --git a/2010/OWASP Top 10 2010 Spanish.pptx b/2010/OWASP Top 10 2010 Spanish.pptx
diff --git a/2010/OWASPTop 10 2010 Vietnamese.pdf b/2010/OWASPTop 10 2010 Vietnamese.pdf
diff --git a/2010/drafts/OWASP_T10_-_2010_rc1.pdf b/2010/drafts/OWASP_T10_-_2010_rc1.pdf
diff --git a/2010/presentations/OWASP_Top_10_-_2010 Presentation.pptx b/2010/presentations/OWASP_Top_10_-_2010 Presentation.pptx
diff --git a/..._Comparison/OWASP_Top_Ten_-_Comparison_of_2003,2004,2007,2010,2013_and_2017_Releases.docx b/..._Comparison/OWASP_Top_Ten_-_Comparison_of_2003,2004,2007,2010,2013_and_2017_Releases.docx
diff --git a/2017/OWASP-Top-10-2017-en.html b/2017/OWASP-Top-10-2017-en.html
diff --git a/2017/OWASP-Top-10-2017-fr.html b/2017/OWASP-Top-10-2017-fr.html
diff --git a/2017/OWASP-Top-10-2017-pt-br.html b/2017/OWASP-Top-10-2017-pt-br.html
diff --git a/2017/de/readme.md b/2017/de/readme.md
@@ -1,7 +1,7 @@
 # OWASP Top 10 2017 de
 
 This folder contains the German version of the OWASP Top 10 - 2017.<br>
-The official website is here: https://www.owasp.org/index.php/Germany/Projekte/Top_10
+The official website is here: https://wiki.owasp.org/index.php/Germany/Projekte/Top_10
 
 * [OWASP Top 10 2017 German Version (PPTX)](https://github.com/OWASP/Top10/blob/master/2017/de/OWASP%20Top%2010-2017_de_V1.0.pptx)
 * [OWASP Top 10 2017 German Version (PDF)](https://github.com/OWASP/Top10/blob/master/2017/de/OWASP%20Top%2010-2017_de_V1.0.pdf)

diff --git a/2017/en/0x01-about-owasp.md b/2017/en/0x01-about-owasp.md
@@ -9,11 +9,11 @@ At OWASP, you'll find free and open:
 * Application security tools and standards.
 * Complete books on application security testing, secure code development, and secure code review.
 * Presentations and [videos](https://www.youtube.com/user/OWASPGLOBAL).
-* [Cheat sheets](https://www.owasp.org/index.php/OWASP_Cheat_Sheet_Series) on many common topics.
+* [Cheat sheets](https://wiki.owasp.org/index.php/OWASP_Cheat_Sheet_Series) on many common topics.
 * Standard security controls and libraries.
-* [Local chapters worldwide](https://www.owasp.org/index.php/OWASP_Chapter).
+* [Local chapters worldwide](https://wiki.owasp.org/index.php/OWASP_Chapter).
 * Cutting edge research.
-* Extensive [conferences worldwide](https://www.owasp.org/index.php/Category:OWASP_AppSec_Conference).
+* Extensive [conferences worldwide](https://wiki.owasp.org/index.php/Category:OWASP_AppSec_Conference).
 * [Mailing lists](https://lists.owasp.org/mailman/listinfo).
 
 Learn more at: [https://www.owasp.org](https://www.owasp.org).

diff --git a/2017/en/0x02-foreword.md b/2017/en/0x02-foreword.md
@@ -6,7 +6,7 @@ A great deal of feedback was received during the creation of the OWASP Top 10 -
 
 Although the original goal of the OWASP Top 10 project was simply to raise awareness amongst developers and managers, it has become the de facto application security standard. 
 
-In this release, issues and recommendations are written concisely and in a testable way to assist with the adoption of the OWASP Top 10 in application security programs. We encourage large and high performing organizations to use the [OWASP Application Security Verification Standard (ASVS)](https://www.owasp.org/index.php/ASVS) if a true standard is required, but for most, the OWASP Top 10 is a great start on the application security journey.
+In this release, issues and recommendations are written concisely and in a testable way to assist with the adoption of the OWASP Top 10 in application security programs. We encourage large and high performing organizations to use the [OWASP Application Security Verification Standard (ASVS)](https://wiki.owasp.org/index.php/ASVS) if a true standard is required, but for most, the OWASP Top 10 is a great start on the application security journey.
 
 We have written up a range of suggested next steps for different users of the OWASP Top 10, including "What's Next for Developers", "What's Next for Security Testers", "What's Next for Organizations“, which is suitable for CIOs and CISOs, and "What's Next for Application Managers", which is suitable for application managers or anyone responsible for the lifecycle of the application.
 
@@ -18,7 +18,7 @@ We hope that the OWASP Top 10 is useful to your application security efforts. Pl
 
 You can find the OWASP Top 10 project and translations here:
 
-* [https://www.owasp.org/index.php/top10](https://www.owasp.org/index.php/top10)
+* [https://wiki.owasp.org/index.php/top10](https://wiki.owasp.org/index.php/top10)
 
 Lastly, we wish to thank the founding leadership of the OWASP Top 10 project, Dave Wichers and Jeff Williams, for all their efforts, and believing in us to get this finished with the community's help. Thank you!
 

diff --git a/2017/en/0x05-introduction.md b/2017/en/0x05-introduction.md
@@ -10,15 +10,15 @@ A primary aim of the OWASP Top 10 is to educate developers, designers, architect
 
 ## Roadmap for future activities
 
-**Don't stop at 10**. There are hundreds of issues that could affect the overall security of a web application as discussed in the [OWASP Developer's Guide](https://www.owasp.org/index.php/OWASP_Guide_Project) and the [OWASP Cheat Sheet Series](https://www.owasp.org/index.php/Category:Cheatsheets). These are essential reading for anyone developing web applications and APIs. Guidance on how to effectively find vulnerabilities in web applications and APIs is provided in the [OWASP Testing Guide](https://www.owasp.org/index.php/OWASP_Testing_Project).
+**Don't stop at 10**. There are hundreds of issues that could affect the overall security of a web application as discussed in the [OWASP Developer's Guide](https://wiki.owasp.org/index.php/OWASP_Guide_Project) and the [OWASP Cheat Sheet Series](https://wiki.owasp.org/index.php/Category:Cheatsheets). These are essential reading for anyone developing web applications and APIs. Guidance on how to effectively find vulnerabilities in web applications and APIs is provided in the [OWASP Testing Guide](https://wiki.owasp.org/index.php/OWASP_Testing_Project).
 
 **Constant change**. The OWASP Top 10 will continue to change. Even without changing a single line of your application's code, you may become vulnerable as new flaws are discovered and attack methods are refined. Please review the advice at the end of the Top 10 in What's Next For Developers, Testers, Organizations and Application Managers for more information.
 
-**Think positive**. When you're ready to stop chasing vulnerabilities and focus on establishing strong application security controls, the [OWASP Proactive Controls](https://www.owasp.org/index.php/OWASP_Proactive_Controls) project provides a starting point to help developers build security into their applications and the [OWASP Application Security Verification Standard (ASVS)](https://www.owasp.org/index.php/ASVS) is a guide for organizations and application reviewers on what to verify.
+**Think positive**. When you're ready to stop chasing vulnerabilities and focus on establishing strong application security controls, the [OWASP Proactive Controls](https://wiki.owasp.org/index.php/OWASP_Proactive_Controls) project provides a starting point to help developers build security into their applications and the [OWASP Application Security Verification Standard (ASVS)](https://wiki.owasp.org/index.php/ASVS) is a guide for organizations and application reviewers on what to verify.
 
 **Use tools wisely**. Security vulnerabilities can be quite complex and deeply buried in code. In many cases, the most cost-effective approach for finding and eliminating these weaknesses is human experts armed with advanced tools. Relying on tools alone provides a false sense of security and is not recommended.
 
-**Push left, right, and everywhere**. Focus on making security an integral part of your culture throughout your development organization. Find out more in the [OWASP Software Assurance Maturity Model (SAMM)](https://www.owasp.org/index.php/OWASP_SAMM_Project).
+**Push left, right, and everywhere**. Focus on making security an integral part of your culture throughout your development organization. Find out more in the [OWASP Software Assurance Maturity Model (SAMM)](https://wiki.owasp.org/index.php/OWASP_SAMM_Project).
 
 ## Attribution
 

diff --git a/2017/en/0x06-release-notes.md b/2017/en/0x06-release-notes.md
@@ -12,7 +12,7 @@ Over the last few years, the fundamental technology and architecture of applicat
 
 ## New issues, supported by data
 
-* **A4:2017-XML External Entities (XXE)** is a new category primarily supported by source code analysis security testing tools ([SAST](https://www.owasp.org/index.php/Source_Code_Analysis_Tools)) data sets.
+* **A4:2017-XML External Entities (XXE)** is a new category primarily supported by source code analysis security testing tools ([SAST](https://wiki.owasp.org/index.php/Source_Code_Analysis_Tools)) data sets.
 
 ## New issues, supported by the community
 
@@ -24,7 +24,7 @@ We asked the community to provide insight into two forward looking weakness cate
 ## Merged or retired, but not forgotten
 
 * **A4-Insecure Direct Object References** and **A7-Missing Function Level Access Control** merged into **A5:2017-Broken Access Control**.
-* **A8-Cross-Site Request Forgery (CSRF)**, as many frameworks include [CSRF defenses](https://www.owasp.org/index.php/Cross-Site_Request_Forgery_(CSRF)), it was found in only 5% of applications.
+* **A8-Cross-Site Request Forgery (CSRF)**, as many frameworks include [CSRF defenses](https://wiki.owasp.org/index.php/Cross-Site_Request_Forgery_(CSRF)), it was found in only 5% of applications.
 * **A10-Unvalidated Redirects and Forwards**, while found in approximately in 8% of applications, it was edged out overall by XXE.
 
 ![0x06-release-notes-1](images/0x06-release-notes-1.png)
diff --git a/2017/en/0x10-app-security-risks.md b/2017/en/0x10-app-security-risks.md
@@ -10,7 +10,7 @@ Sometimes these paths are trivial to find and exploit, and sometimes they are ex
 
 ## What's My Risk
 
-The [OWASP Top 10](https://www.owasp.org/index.php/Top10) focuses on identifying the most serious web application security risks for a broad array of organizations. For each of these risks, we provide generic information about likelihood and technical impact using the following simple ratings scheme, which is based on the OWASP Risk Rating Methodology.  
+The [OWASP Top 10](https://wiki.owasp.org/index.php/Top10) focuses on identifying the most serious web application security risks for a broad array of organizations. For each of these risks, we provide generic information about likelihood and technical impact using the following simple ratings scheme, which is based on the OWASP Risk Rating Methodology.  
 
 | Threat Agents | Exploitability | Weakness Prevalence | Weakness Detectability | Technical Impacts | Business Impacts |
 | -- | -- | -- | -- | -- | -- |
@@ -28,8 +28,8 @@ Where possible, the names of the risks in the Top 10 are aligned with [Common We
 
 ### OWASP
 
-* [OWASP Risk Rating Methodology](https://www.owasp.org/index.php/OWASP_Risk_Rating_Methodology)
-* [Article on Threat/Risk Modeling](https://www.owasp.org/index.php/Threat_Risk_Modeling)
+* [OWASP Risk Rating Methodology](https://wiki.owasp.org/index.php/OWASP_Risk_Rating_Methodology)
+* [Article on Threat/Risk Modeling](https://wiki.owasp.org/index.php/Threat_Risk_Modeling)
 
 ### External
 

diff --git a/2017/en/0xa1-injection.md b/2017/en/0xa1-injection.md
@@ -3,7 +3,7 @@
 | Threat agents/Attack vectors | Security Weakness           | Impacts               |
 | -- | -- | -- |
 | Access Lvl : Exploitability 3 | Prevalence 2 : Detectability 3 | Technical 3 : Business |
-| Almost any source of data can be an injection vector, environment variables, parameters, external and internal web services, and all types of users. [Injection flaws](https://www.owasp.org/index.php/Injection_Flaws) occur when an attacker can send hostile data to an interpreter. | Injection flaws are very prevalent, particularly in legacy code. Injection vulnerabilities are often found in SQL, LDAP, XPath, or NoSQL queries, OS commands, XML parsers, SMTP headers, expression languages, and ORM queries. Injection flaws are easy to discover when examining code. Scanners and fuzzers can help attackers find injection flaws. |Injection can result in data loss, corruption, or disclosure to unauthorized parties, loss of accountability, or denial of access. Injection can sometimes lead to complete host takeover. The business impact depends on the needs of the application and data.|
+| Almost any source of data can be an injection vector, environment variables, parameters, external and internal web services, and all types of users. [Injection flaws](https://wiki.owasp.org/index.php/Injection_Flaws) occur when an attacker can send hostile data to an interpreter. | Injection flaws are very prevalent, particularly in legacy code. Injection vulnerabilities are often found in SQL, LDAP, XPath, or NoSQL queries, OS commands, XML parsers, SMTP headers, expression languages, and ORM queries. Injection flaws are easy to discover when examining code. Scanners and fuzzers can help attackers find injection flaws. |Injection can result in data loss, corruption, or disclosure to unauthorized parties, loss of accountability, or denial of access. Injection can sometimes lead to complete host takeover. The business impact depends on the needs of the application and data.|
 
 
 ## Is the Application Vulnerable?
@@ -14,7 +14,7 @@ An application is vulnerable to attack when:
 * Dynamic queries or non-parameterized calls without context-aware escaping are used directly in the interpreter.  
 * Hostile data is used within object-relational mapping (ORM) search parameters to extract additional, sensitive records.
 * Hostile data is directly used or concatenated, such that the SQL or command contains both structure and hostile data in dynamic queries, commands, or stored procedures.
-* Some of the more common injections are SQL, NoSQL, OS command, Object Relational Mapping (ORM), LDAP, and Expression Language (EL) or Object Graph Navigation Library (OGNL) injection. The concept is identical among all interpreters. Source code review is the best method of detecting if applications are vulnerable to injections, closely followed by thorough automated testing of all parameters, headers, URL, cookies, JSON, SOAP, and XML data inputs. Organizations can include static source ([SAST](https://www.owasp.org/index.php/Source_Code_Analysis_Tools)) and dynamic application test ([DAST](https://www.owasp.org/index.php/Category:Vulnerability_Scanning_Tools)) tools into the CI/CD pipeline to identify newly introduced injection flaws prior to production deployment.
+* Some of the more common injections are SQL, NoSQL, OS command, Object Relational Mapping (ORM), LDAP, and Expression Language (EL) or Object Graph Navigation Library (OGNL) injection. The concept is identical among all interpreters. Source code review is the best method of detecting if applications are vulnerable to injections, closely followed by thorough automated testing of all parameters, headers, URL, cookies, JSON, SOAP, and XML data inputs. Organizations can include static source ([SAST](https://wiki.owasp.org/index.php/Source_Code_Analysis_Tools)) and dynamic application test ([DAST](https://wiki.owasp.org/index.php/Category:Vulnerability_Scanning_Tools)) tools into the CI/CD pipeline to identify newly introduced injection flaws prior to production deployment.
 
 ## How To Prevent
 
@@ -23,7 +23,6 @@ Preventing injection requires keeping data separate from commands and queries.
 * The preferred option is to use a safe API, which avoids the use of the interpreter entirely or provides a parameterized interface, or migrate to use Object Relational Mapping Tools (ORMs). **Note**: Even when parameterized, stored procedures can still introduce SQL injection if PL/SQL or T-SQL concatenates queries and data, or executes hostile data with EXECUTE IMMEDIATE or exec().
 * Use positive or "whitelist" server-side input validation. This is not a complete defense as many applications require special characters, such as text areas or APIs for mobile applications.
 * For any residual dynamic queries, escape special characters using the specific escape syntax for that interpreter. **Note**: SQL structure such as table names, column names, and so on cannot be escaped, and thus user-supplied structure names are dangerous. This is a common issue in report-writing software.
-* Use LIMIT and other SQL controls within queries to prevent mass disclosure of records in case of SQL injection.
 
 ## Example Attack Scenarios
 
@@ -35,24 +34,24 @@ Preventing injection requires keeping data separate from commands and queries.
 
 `Query HQLQuery = session.createQuery("FROM accounts WHERE custID='" + request.getParameter("id") + "'");`
 
-In both cases, the attacker modifies the ‘id’ parameter value in their browser to send:  ' or '1'='1. For example:
+In both cases, the attacker modifies the ‘id’ parameter value in their browser to send:  ' UNION SELECT SLEEP(10);--. For example:
 
-`http://example.com/app/accountView?id=' or '1'='1`
+`http://example.com/app/accountView?id=' UNION SELECT SLEEP(10);--`
 
 This changes the meaning of both queries to return all the records from the accounts table. More dangerous attacks could modify or delete data, or even invoke stored procedures.
 
 ## References
 
 ### OWASP
 
-* [OWASP Proactive Controls: Parameterize Queries](https://www.owasp.org/index.php/OWASP_Proactive_Controls#2:_Parameterize_Queries)
-* [OWASP ASVS: V5 Input Validation and Encoding](https://www.owasp.org/index.php/ASVS_V5_Input_validation_and_output_encoding)
-* [OWASP Testing Guide: SQL Injection](https://www.owasp.org/index.php/Testing_for_SQL_Injection_(OTG-INPVAL-005)), [Command Injection](https://www.owasp.org/index.php/Testing_for_Command_Injection_(OTG-INPVAL-013)), [ORM injection](https://www.owasp.org/index.php/Testing_for_ORM_Injection_(OTG-INPVAL-007))
-* [OWASP Cheat Sheet: Injection Prevention](https://www.owasp.org/index.php/Injection_Prevention_Cheat_Sheet)
-* [OWASP Cheat Sheet: SQL Injection Prevention](https://www.owasp.org/index.php/SQL_Injection_Prevention_Cheat_Sheet)
-* [OWASP Cheat Sheet: Injection Prevention in Java](https://www.owasp.org/index.php/Injection_Prevention_Cheat_Sheet_in_Java)
-* [OWASP Cheat Sheet: Query Parameterization](https://www.owasp.org/index.php/Query_Parameterization_Cheat_Sheet)
-* [OWASP Automated Threats to Web Applications – OAT-014](https://www.owasp.org/index.php/OWASP_Automated_Threats_to_Web_Applications)
+* [OWASP Proactive Controls: Parameterize Queries](https://wiki.owasp.org/index.php/OWASP_Proactive_Controls#2:_Parameterize_Queries)
+* [OWASP ASVS: V5 Input Validation and Encoding](https://wiki.owasp.org/index.php/ASVS_V5_Input_validation_and_output_encoding)
+* [OWASP Testing Guide: SQL Injection](https://wiki.owasp.org/index.php/Testing_for_SQL_Injection_(OTG-INPVAL-005)), [Command Injection](https://wiki.owasp.org/index.php/Testing_for_Command_Injection_(OTG-INPVAL-013)), [ORM injection](https://wiki.owasp.org/index.php/Testing_for_ORM_Injection_(OTG-INPVAL-007))
+* [OWASP Cheat Sheet: Injection Prevention](https://wiki.owasp.org/index.php/Injection_Prevention_Cheat_Sheet)
+* [OWASP Cheat Sheet: SQL Injection Prevention](https://wiki.owasp.org/index.php/SQL_Injection_Prevention_Cheat_Sheet)
+* [OWASP Cheat Sheet: Injection Prevention in Java](https://wiki.owasp.org/index.php/Injection_Prevention_Cheat_Sheet_in_Java)
+* [OWASP Cheat Sheet: Query Parameterization](https://wiki.owasp.org/index.php/Query_Parameterization_Cheat_Sheet)
+* [OWASP Automated Threats to Web Applications – OAT-014](https://wiki.owasp.org/index.php/OWASP_Automated_Threats_to_Web_Applications)
 
 ### External