ben.carrasco/prowler
1
0
Fork 0
mirror of https://github.com/prowler-cloud/prowler.git synced 2026-07-24 21:11:53 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: readme points to docs.prowler.com to learn everything (#3707)

Browse Source 
Co-authored-by: Sergio <sergio@prowler.com>
Co-authored-by: Sergio Garcia <38561120+sergargar@users.noreply.github.com>
This commit is contained in:
Pepe Fagoaga
2024-04-09 16:28:01 +02:00
committed by GitHub
parent 9c9d270053
commit 417131fa36
9 changed files with 83 additions and 212 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/tutorials/aws/cloudshell.md
+1 -1
View File
@@ -7,7 +7,7 @@ sudo bash
adduser prowler
su prowler
pip install prowler
cd /tmp || exit
cd /tmp
prowler aws
```
docs/tutorials/aws/v2_to_v3_checks_mapping.md
+4 -4
View File
@@ -1,11 +1,11 @@
# Check mapping between Prowler v3 and v2
# Check mapping between Prowler v4/v3 and v2
Prowler v3 comes with different identifiers but we maintained the same checks that were implemented in v2. The reason for this change is because in previous versions of Prowler, check names were mostly based on CIS Benchmark for AWS. In v3 all checks are independent from any security framework and they have its own name and ID.
Prowler v3 comes with different identifiers but we maintained the same checks that were implemented in v2. The reason for this change is because in previous versions of Prowler, check names were mostly based on CIS Benchmark for AWS. In v4 and v3 all checks are independent from any security framework and they have its own name and ID.
If you need more information about how new compliance implementation works in Prowler v3 see [Compliance](../compliance.md) section.
If you need more information about how new compliance implementation works in Prowler v4 and v3 see [Compliance](../compliance.md) section.
```
checks_v3_to_v2_mapping = {
checks_v4_v3_to_v2_mapping = {
"accessanalyzer_enabled_without_findings": "extra769",
"account_maintain_current_contact_details": "check117",
"account_security_contact_information_is_registered": "check118",