From c0109880313dfc2c58ddaeb938c28181dcc3f83f Mon Sep 17 00:00:00 2001 From: Louis Nadeau Date: Wed, 22 May 2024 15:54:22 -0400 Subject: [PATCH] Fixing a typo and trying a PR --- document/0.1/03-Using_the_TASVS.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/document/0.1/03-Using_the_TASVS.md b/document/0.1/03-Using_the_TASVS.md index bdece89..9e74737 100644 --- a/document/0.1/03-Using_the_TASVS.md +++ b/document/0.1/03-Using_the_TASVS.md @@ -44,7 +44,7 @@ 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. @@ -52,4 +52,4 @@ We folow the same levelling methodology as the [Web Application Security Verific -\newpage{} \ No newline at end of file +\newpage{}