Skip to content

Commit 78053fd

Browse files
committed
fix link and typo
1 parent 06296f6 commit 78053fd

File tree

2 files changed

+1
-8
lines changed

2 files changed

+1
-8
lines changed

draft/05-requirements/toc.md

Lines changed: 0 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -26,12 +26,6 @@ permalink: /draft/requirements/
2626

2727
## 3. Requirements
2828

29-
Referring to the OWASP [Top Ten Proactive Controls][control1], security requirements are statements of
30-
security functionality that ensure the different security properties of a software application are being satisfied.
31-
Security requirements are derived from industry standards, applicable laws, and a history of past vulnerabilities.
32-
Security requirements define new features or additions to existing features to solve a specific security problem
33-
or eliminate potential vulnerabilities.
34-
3529
Security requirements also provide a foundation of vetted security functionality for an application.
3630
Instead of creating a custom approach to security for every application,
3731
standard security requirements allow developers to reuse the definition of security controls and best practices;
@@ -61,7 +55,6 @@ Sections:
6155
The OWASP Developer Guide is a community effort; if there is something that needs changing
6256
then [submit an issue][issue0500] or [edit on GitHub][edit0500].
6357

64-
[control1]: https://owasp.org/www-project-proactive-controls/v3/en/c1-security-requirements
6558
[edit0500]: https://github.com/OWASP/www-project-developer-guide/blob/main/draft/05-requirements/toc.md
6659
[issue0500]: https://github.com/OWASP/www-project-developer-guide/issues/new?labels=enhancement&template=request.md&title=Update:%2005-requirements/00-toc
6760
[samm]: https://owaspsamm.org/about/

draft/06-design/02-web-app-checklist/03-secure-database-access.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ permalink: /draft/design/web_app_checklist/secure_database_access/
1616

1717
Ensure that access to all data stores is secure, including both relational databases and NoSQL databases.
1818

19-
Refer to proactive control [C3: Validate all Input & Handle Excpetions][control3] and its [cheatsheets][csproactive-c3]
19+
Refer to proactive control [C3: Validate all Input & Handle Exceptions][control3] and its [cheatsheets][csproactive-c3]
2020
for more context from the OWASP Top 10 Proactive Controls project,
2121
and use the list below as suggestions for a checklist that has been tailored for the individual project.
2222

0 commit comments

Comments
 (0)