Skip to content

Commit

Permalink
Wrong word
Browse files Browse the repository at this point in the history
  • Loading branch information
tghosth authored Dec 12, 2024
1 parent a16206f commit 0bc8d48
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion 5.0/en/0x03-Using-ASVS.md
Original file line number Diff line number Diff line change
Expand Up @@ -42,7 +42,7 @@ In version 4.0, Levels 1 and 2 both had around 120 requirements and Level 3 had

### Definition of the Levels

By moving to a priority based evaluation of each requirement, the levels become more of a reflection of the application security maturity of the organization and the application. Rather than the ASVS prescriptively stating what level an application should be at, an organization should decide what level it believes feels it should be at, depending on the sensitivity of the application and of course the expectations of the application's users.
By moving to a priority based evaluation of each requirement, the levels become more of a reflection of the application security maturity of the organization and the application. Rather than the ASVS prescriptively stating what level an application should be at, an organization should decide what level it believes it should be at, depending on the sensitivity of the application and of course the expectations of the application's users.

For example, an early stage startup which is only collecting limited sensitive data may decide that Level 1 is sufficient but a bank may have difficulty justifying anything less than Level 3 to its customers for its online banking application.

Expand Down

0 comments on commit 0bc8d48

Please sign in to comment.