Publish Latest 2025-06-28 (#450)

wstgbot · web-flow · commit 406b101319cb · 2025-06-28T06:37:27.000-04:00
Updates based on OWASP/wstg@5085711
diff --git a/latest/0-Foreword/README.md b/latest/0-Foreword/README.md
@@ -9,9 +9,9 @@ tags: WSTG
 {% include breadcrumb.html %}
 # Foreword by Eoin Keary
 
-The problem of insecure software is perhaps the most important technical challenge of our time. The dramatic rise of web applications enabling business, social networking etc has only compounded the requirements to establish a robust approach to writing and securing our Internet, Web Applications and Data.
+The problem of insecure software is perhaps the most important technical challenge of our time. The dramatic rise of web applications enabling business, social networking etc has only compounded the requirements to establish a robust approach to writing and securing our internet, web applications, and data.
 
-At the Open Web Application Security Project® (OWASP®), we're trying to make the world a place where insecure software is the anomaly, not the norm. The OWASP Testing Guide has an important role to play in solving this serious issue. It is vitally important that our approach to testing software for security issues is based on the principles of engineering and science. We need a consistent, repeatable and defined approach to testing web applications. A world without some minimal standards in terms of engineering and technology is a world in chaos.
+At the Open Worldwide Application Security Project® (OWASP®), we're trying to make the world a place where insecure software is the anomaly, not the norm. The OWASP Testing Guide has an important role to play in solving this serious issue. It is vitally important that our approach to testing software for security issues is based on the principles of engineering and science. We need a consistent, repeatable and defined approach to testing web applications. A world without some minimal standards in terms of engineering and technology is a world in chaos.
 
 It goes without saying that you can't build a secure application without performing security testing on it. Testing is part of a wider approach to build a secure system. Many software development organizations do not include security testing as part of their standard software development process. What is even worse is that many security vendors deliver testing with varying degrees of quality and rigor.
 
@@ -64,4 +64,4 @@ Thank you to all the past and future contributors to this guide, your work will
 
 --Eoin Keary, OWASP Board Member, April 19, 2013
 
-Open Web Application Security Project and OWASP are registered trademarks of the OWASP Foundation, Inc.
+Open Worldwide Application Security Project and OWASP are registered trademarks of the OWASP Foundation, Inc.
diff --git a/latest/0-Foreword/index.md b/latest/0-Foreword/index.md
@@ -9,9 +9,9 @@ tags: WSTG
 {% include breadcrumb.html %}
 # Foreword by Eoin Keary
 
-The problem of insecure software is perhaps the most important technical challenge of our time. The dramatic rise of web applications enabling business, social networking etc has only compounded the requirements to establish a robust approach to writing and securing our Internet, Web Applications and Data.
+The problem of insecure software is perhaps the most important technical challenge of our time. The dramatic rise of web applications enabling business, social networking etc has only compounded the requirements to establish a robust approach to writing and securing our internet, web applications, and data.
 
-At the Open Web Application Security Project® (OWASP®), we're trying to make the world a place where insecure software is the anomaly, not the norm. The OWASP Testing Guide has an important role to play in solving this serious issue. It is vitally important that our approach to testing software for security issues is based on the principles of engineering and science. We need a consistent, repeatable and defined approach to testing web applications. A world without some minimal standards in terms of engineering and technology is a world in chaos.
+At the Open Worldwide Application Security Project® (OWASP®), we're trying to make the world a place where insecure software is the anomaly, not the norm. The OWASP Testing Guide has an important role to play in solving this serious issue. It is vitally important that our approach to testing software for security issues is based on the principles of engineering and science. We need a consistent, repeatable and defined approach to testing web applications. A world without some minimal standards in terms of engineering and technology is a world in chaos.
 
 It goes without saying that you can't build a secure application without performing security testing on it. Testing is part of a wider approach to build a secure system. Many software development organizations do not include security testing as part of their standard software development process. What is even worse is that many security vendors deliver testing with varying degrees of quality and rigor.
 
@@ -64,4 +64,4 @@ Thank you to all the past and future contributors to this guide, your work will
 
 --Eoin Keary, OWASP Board Member, April 19, 2013
 
-Open Web Application Security Project and OWASP are registered trademarks of the OWASP Foundation, Inc.
+Open Worldwide Application Security Project and OWASP are registered trademarks of the OWASP Foundation, Inc.
diff --git a/latest/1-Frontispiece/README.md b/latest/1-Frontispiece/README.md
@@ -95,7 +95,7 @@ This document is released under the [Creative Commons 4.0 License](https://creat
 - Merriam-Webster is a trademark of Merriam-Webster, Inc.
 - Microsoft is a registered trademark of Microsoft Corporation.
 - Octave is a service mark of Carnegie Mellon University.
-- Open Web Application Security Project and OWASP are registered trademarks of the OWASP Foundation, Inc.
+- Open Worldwide Application Security Project and OWASP are registered trademarks of the OWASP Foundation, Inc.
 - VeriSign and Thawte are registered trademarks of VeriSign, Inc.
 - Visa is a registered trademark of VISA USA.
 
diff --git a/latest/1-Frontispiece/index.md b/latest/1-Frontispiece/index.md
@@ -95,7 +95,7 @@ This document is released under the [Creative Commons 4.0 License](https://creat
 - Merriam-Webster is a trademark of Merriam-Webster, Inc.
 - Microsoft is a registered trademark of Microsoft Corporation.
 - Octave is a service mark of Carnegie Mellon University.
-- Open Web Application Security Project and OWASP are registered trademarks of the OWASP Foundation, Inc.
+- Open Worldwide Application Security Project and OWASP are registered trademarks of the OWASP Foundation, Inc.
 - VeriSign and Thawte are registered trademarks of VeriSign, Inc.
 - Visa is a registered trademark of VISA USA.
 
diff --git a/latest/6-Appendix/B-Suggested_Reading.md b/latest/6-Appendix/B-Suggested_Reading.md
@@ -48,7 +48,7 @@ tags: WSTG
 - [McAfee Free Tools](https://www.mcafee.com/enterprise/en-us/downloads/free-tools.html)
 - [OASIS Web Application Security (WAS) TC](https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=was)
 - [SANS Internet Storm Center (ISC)](https://isc.sans.edu/)
-- [The Open Web Application Application Security Project (OWASP)](https://owasp.org)
+- [The Open Worldwide Application Application Security Project (OWASP)](https://owasp.org)
 - [Pentestmonkey - Pen Testing Cheat Sheets](https://pentestmonkey.net/cheat-sheet)
 - [Secure Coding Guidelines for the .NET Framework 4.5](https://docs.microsoft.com/en-us/dotnet/standard/security/secure-coding-guidelines)
 - [Security in the Java platform](https://docs.oracle.com/javase/6/docs/technotes/guides/security/overview/jsoverview.html)
