Skip to content

Commit

Permalink
Merge pull request #3 from cybernot/patch-1
Browse files Browse the repository at this point in the history
Fixing a typo and trying a PR, should trigger PDF production and create release automatically
  • Loading branch information
JeffreyShran committed May 23, 2024
2 parents cd451bd + c010988 commit 5764dfb
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions document/0.1/03-Using_the_TASVS.md
Original file line number Diff line number Diff line change
Expand Up @@ -44,12 +44,12 @@ The standard is divided into various groups labelled `TASVS-{word}` that represe

## Application Security Verification Levels

We folow the same levelling methodology as the [Web Application Security Verification Standard](https://github.com/OWASP/ASVS/tree/master). It defines three security verification levels, with each level increasing in depth.
We follow the same levelling methodology as the [Web Application Security Verification Standard](https://github.com/OWASP/ASVS/tree/master). It defines three security verification levels, with each level increasing in depth.

- L1 - TASVS Level 1 is for low assurance levels and is completely verifiable through penetration testing.
- L2 - TASVS Level 2 is for applications that contain sensitive data, which requires protection and is the recommended level for most apps.
- L3 - TASVS Level 3 is intended for the most critical applications, such as those handling high-value transactions, containing sensitive medical data, or any application demanding the highest level of trust.



\newpage{}
\newpage{}

0 comments on commit 5764dfb

Please sign in to comment.