Update rules metadata (#1095)

SonarSource · Jan 29, 2024 · f290db6 · f290db6
1 parent 36cf8be
commit f290db6
Show file tree

Hide file tree

Showing 89 changed files with 38 additions and 385 deletions.
diff --git a/iac-extensions/arm/sonarpedia.json b/iac-extensions/arm/sonarpedia.json
@@ -3,7 +3,7 @@
   "languages": [
     "AZURE_RESOURCE_MANAGER"
   ],
-  "latest-update": "2024-01-17T14:02:18.875712683Z",
+  "latest-update": "2024-01-29T14:21:01.576987Z",
   "options": {
     "no-language-in-filenames": true,
     "preserve-filenames": true

diff --git a/.../main/resources/org/sonar/l10n/azureresourcemanager/rules/azureresourcemanager/S1135.html b/.../main/resources/org/sonar/l10n/azureresourcemanager/rules/azureresourcemanager/S1135.html
@@ -1,8 +1,8 @@
 <h2>Why is this an issue?</h2>
 <p>Developers often use <code>TODO</code> tags to mark areas in the code where additional work or improvements are needed but are not implemented
-immediately. However, these <code>TODO</code> tags sometimes get overlooked or forgotten, leading to incomplete or unfinished code. This code smell
-class aims to identify and address such unattended <code>TODO</code> tags to ensure a clean and maintainable codebase. This description will explore
-why this is a problem and how it can be fixed to improve the overall code quality.</p>
+immediately. However, these <code>TODO</code> tags sometimes get overlooked or forgotten, leading to incomplete or unfinished code. This rule aims to
+identify and address unattended <code>TODO</code> tags to ensure a clean and maintainable codebase. This description explores why this is a problem
+and how it can be fixed to improve the overall code quality.</p>
 <h3>What is the potential impact?</h3>
 <p>Unattended <code>TODO</code> tags in code can have significant implications for the development process and the overall codebase.</p>
 <p>Incomplete Functionality: When developers leave <code>TODO</code> tags without implementing the corresponding code, it results in incomplete
@@ -11,8 +11,8 @@ <h3>What is the potential impact?</h3>
 Delayed bug fixes can result in more severe issues and increase the effort required to resolve them later.</p>
 <p>Impact on Collaboration: In team-based development environments, unattended <code>TODO</code> tags can hinder collaboration. Other team members
 might not be aware of the intended changes, leading to conflicts or redundant efforts in the codebase.</p>
-<p>Codebase Bloat: Accumulation of unattended <code>TODO</code> tags over time can clutter the codebase and make it difficult to distinguish between
-work in progress and completed code. This bloat can make it challenging to maintain an organized and efficient codebase.</p>
+<p>Codebase Bloat: The accumulation of unattended <code>TODO</code> tags over time can clutter the codebase and make it difficult to distinguish
+between work in progress and completed code. This bloat can make it challenging to maintain an organized and efficient codebase.</p>
 <p>Addressing this code smell is essential to ensure a maintainable, readable, reliable codebase and promote effective collaboration among
 developers.</p>
 <h3>Noncompliant code example</h3>

diff --git a/.../main/resources/org/sonar/l10n/azureresourcemanager/rules/azureresourcemanager/S4423.html b/.../main/resources/org/sonar/l10n/azureresourcemanager/rules/azureresourcemanager/S4423.html
@@ -186,9 +186,6 @@ <h3>Articles &amp; blog posts</h3>
 </ul>
 <h3>Standards</h3>
 <ul>
-  <li> OWASP - <a href="https://owasp.org/Top10/A02_2021-Cryptographic_Failures/">Top 10 2021 Category A2 - Cryptographic Failures</a> </li>
-  <li> OWASP - <a href="https://owasp.org/www-project-top-ten/2017/A6_2017-Security_Misconfiguration">Top 10 2017 Category A6 - Security
-  Misconfiguration</a> </li>
   <li> CWE - <a href="https://cwe.mitre.org/data/definitions/327">CWE-327 - Use of a Broken or Risky Cryptographic Algorithm</a> </li>
 </ul>
 
diff --git a/.../main/resources/org/sonar/l10n/azureresourcemanager/rules/azureresourcemanager/S6321.html b/.../main/resources/org/sonar/l10n/azureresourcemanager/rules/azureresourcemanager/S6321.html
@@ -89,8 +89,5 @@ <h3>Documentation</h3>
 <h3>Standards</h3>
 <ul>
   <li> CWE - <a href="https://cwe.mitre.org/data/definitions/284">CWE-284 - Improper Access Control</a> </li>
-  <li> OWASP - <a href="https://owasp.org/www-project-top-ten/2017/A5_2017-Broken_Access_Control">Top 10 2017 Category A5 - Broken Access Control</a>
-  </li>
-  <li> OWASP - <a href="https://owasp.org/Top10/A01_2021-Broken_Access_Control/">Top 10 2021 Category A1 - Broken Access Control</a> </li>
 </ul>
 
diff --git a/.../main/resources/org/sonar/l10n/azureresourcemanager/rules/azureresourcemanager/S6329.html b/.../main/resources/org/sonar/l10n/azureresourcemanager/rules/azureresourcemanager/S6329.html
@@ -233,15 +233,12 @@ <h2>Compliant Solution</h2>
 </pre>
 <h2>See</h2>
 <ul>
-  <li> OWASP - <a href="https://owasp.org/Top10/A01_2021-Broken_Access_Control/">Top 10 2021 Category A1 - Broken Access Control</a> </li>
   <li> <a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-instance-addressing.html">AWS Documentation</a> - Amazon EC2 instance IP
   addressing </li>
   <li> <a href="https://docs.aws.amazon.com/dms/latest/userguide/CHAP_ReplicationInstance.PublicPrivate.html">AWS Documentation</a> - Public and
   private replication instances </li>
   <li> <a href="https://docs.aws.amazon.com/vpc/latest/peering/what-is-vpc-peering.html">AWS Documentation</a> - VPC Peering </li>
   <li> CWE - <a href="https://cwe.mitre.org/data/definitions/284">CWE-284 - Improper Access Control</a> </li>
   <li> CWE - <a href="https://cwe.mitre.org/data/definitions/668">CWE-668 - Exposure of Resource to Wrong Sphere</a> </li>
-  <li> OWASP - <a href="https://owasp.org/www-project-top-ten/2017/A5_2017-Broken_Access_Control">Top 10 2017 Category A5 - Broken Access Control</a>
-  </li>
 </ul>
 
diff --git a/.../main/resources/org/sonar/l10n/azureresourcemanager/rules/azureresourcemanager/S6378.html b/.../main/resources/org/sonar/l10n/azureresourcemanager/rules/azureresourcemanager/S6378.html
@@ -71,9 +71,6 @@ <h2>Compliant Solution</h2>
 </pre>
 <h2>See</h2>
 <ul>
-  <li> OWASP - <a href="https://owasp.org/Top10/A05_2021-Security_Misconfiguration/">Top 10 2021 Category A5- Security Misconfiguration</a> </li>
-  <li> OWASP - <a href="https://owasp.org/www-project-top-ten/2017/A6_2017-Security_Misconfiguration">Top 10 2017 Category A6 - Security
-  Misconfiguration</a> </li>
   <li> <a href="https://docs.microsoft.com/en-us/azure/active-directory/managed-identities-azure-resources/overview">Azure AD Documentation - Managed
   Identities Overview</a> </li>
   <li> <a

diff --git a/.../main/resources/org/sonar/l10n/azureresourcemanager/rules/azureresourcemanager/S6380.html b/.../main/resources/org/sonar/l10n/azureresourcemanager/rules/azureresourcemanager/S6380.html
@@ -431,9 +431,6 @@ <h2>Compliant Solution</h2>
 </pre>
 <h2>See</h2>
 <ul>
-  <li> OWASP - <a href="https://owasp.org/Top10/A01_2021-Broken_Access_Control/">Top 10 2021 Category A1 - Boken Access Control</a> </li>
-  <li> OWASP - <a href="https://owasp.org/www-project-top-ten/2017/A5_2017-Broken_Access_Control">Top 10 2017 Category A5 - Broken Access Control</a>
-  </li>
   <li> CWE - <a href="https://cwe.mitre.org/data/definitions/668">CWE-668 - Exposure of Resource to Wrong Sphere</a> </li>
 </ul>
 
diff --git a/.../main/resources/org/sonar/l10n/azureresourcemanager/rules/azureresourcemanager/S6381.html b/.../main/resources/org/sonar/l10n/azureresourcemanager/rules/azureresourcemanager/S6381.html
@@ -83,10 +83,6 @@ <h2>Compliant Solution</h2>
 </pre>
 <h2>See</h2>
 <ul>
-  <li> OWASP - <a href="https://owasp.org/Top10/A01_2021-Broken_Access_Control/">Top 10 2021 Category A1 - Broken Access Control</a> </li>
-  <li> OWASP - <a href="https://owasp.org/Top10/A04_2021-Insecure_Design/">Top 10 2021 Category A4 - Insecure Design</a> </li>
-  <li> OWASP - <a href="https://owasp.org/www-project-top-ten/2017/A5_2017-Broken_Access_Control">Top 10 2017 Category A5 - Broken Access Control</a>
-  </li>
   <li> CWE - <a href="https://cwe.mitre.org/data/definitions/79">CWE-266 - Incorrect Privilege Assignment</a> </li>
   <li> <a href="https://docs.microsoft.com/en-us/azure/role-based-access-control/built-in-roles">Azure Documentation</a> - Azure built-in roles </li>
   <li> <a href="https://docs.microsoft.com/en-us/azure/role-based-access-control/best-practices">Azure Documentation</a> - Best practices for Azure

diff --git a/.../main/resources/org/sonar/l10n/azureresourcemanager/rules/azureresourcemanager/S6382.html b/.../main/resources/org/sonar/l10n/azureresourcemanager/rules/azureresourcemanager/S6382.html
@@ -482,9 +482,6 @@ <h2>Compliant Solution</h2>
 <h2>See</h2>
 <ul>
   <li> <a href="https://learn.microsoft.com/en-us/azure/templates/">Azure Resource Manager templates</a> </li>
-  <li> OWASP - <a href="https://owasp.org/Top10/A01_2021-Broken_Access_Control/">Top 10 2021 Category A1 - Boken Access Control</a> </li>
-  <li> OWASP - <a href="https://owasp.org/www-project-top-ten/2017/A5_2017-Broken_Access_Control">Top 10 2017 Category A5 - Broken Access Control</a>
-  </li>
   <li> CWE - <a href="https://cwe.mitre.org/data/definitions/668">CWE-668 - Exposure of Resource to Wrong Sphere</a> </li>
 </ul>
 
diff --git a/.../main/resources/org/sonar/l10n/azureresourcemanager/rules/azureresourcemanager/S6383.html b/.../main/resources/org/sonar/l10n/azureresourcemanager/rules/azureresourcemanager/S6383.html
@@ -135,9 +135,6 @@ <h2>Compliant Solution</h2>
 </pre>
 <h2>See</h2>
 <ul>
-  <li> OWASP - <a href="https://owasp.org/Top10/A01_2021-Broken_Access_Control/">Top 10 2021 Category A1 - Boken Access Control</a> </li>
-  <li> OWASP - <a href="https://owasp.org/www-project-top-ten/2017/A5_2017-Broken_Access_Control">Top 10 2017 Category A5 - Broken Access Control</a>
-  </li>
   <li> CWE - <a href="https://cwe.mitre.org/data/definitions/668">CWE-668 - Exposure of Resource to Wrong Sphere</a> </li>
 </ul>
 
diff --git a/.../main/resources/org/sonar/l10n/azureresourcemanager/rules/azureresourcemanager/S6385.html b/.../main/resources/org/sonar/l10n/azureresourcemanager/rules/azureresourcemanager/S6385.html
@@ -139,10 +139,6 @@ <h3>Documentation</h3>
 </ul>
 <h3>Standards</h3>
 <ul>
-  <li> OWASP - <a href="https://owasp.org/Top10/A01_2021-Broken_Access_Control/">Top 10 2021 Category A1 - Broken Access Control</a> </li>
-  <li> OWASP - <a href="https://owasp.org/Top10/A04_2021-Insecure_Design/">Top 10 2021 Category A4 - Insecure Design</a> </li>
-  <li> OWASP - <a href="https://owasp.org/www-project-top-ten/2017/A5_2017-Broken_Access_Control">Top 10 2017 Category A5 - Broken Access Control</a>
-  </li>
   <li> CWE - <a href="https://cwe.mitre.org/data/definitions/266">CWE-266 - Incorrect Privilege Assignment</a> </li>
 </ul>
 
diff --git a/.../main/resources/org/sonar/l10n/azureresourcemanager/rules/azureresourcemanager/S6387.html b/.../main/resources/org/sonar/l10n/azureresourcemanager/rules/azureresourcemanager/S6387.html
@@ -64,10 +64,6 @@ <h2>Compliant Solution</h2>
 </pre>
 <h2>See</h2>
 <ul>
-  <li> OWASP - <a href="https://owasp.org/Top10/A01_2021-Broken_Access_Control/">Top 10 2021 Category A1 - Broken Access Control</a> </li>
-  <li> OWASP - <a href="https://owasp.org/Top10/A04_2021-Insecure_Design/">Top 10 2021 Category A4 - Insecure Design</a> </li>
-  <li> OWASP - <a href="https://owasp.org/www-project-top-ten/2017/A5_2017-Broken_Access_Control">Top 10 2017 Category A5 - Broken Access Control</a>
-  </li>
   <li> CWE - <a href="https://cwe.mitre.org/data/definitions/266">CWE-266 - Incorrect Privilege Assignment</a> </li>
   <li> <a href="https://docs.microsoft.com/en-us/azure/role-based-access-control/scope-overview">Azure Documentation</a> - Understand scope for Azure
   RBAC </li>

diff --git a/.../main/resources/org/sonar/l10n/azureresourcemanager/rules/azureresourcemanager/S6388.html b/.../main/resources/org/sonar/l10n/azureresourcemanager/rules/azureresourcemanager/S6388.html
@@ -1967,14 +1967,7 @@ <h2>Compliant Solution</h2>
 </pre>
 <h2>See</h2>
 <ul>
-  <li> OWASP - <a href="https://owasp.org/Top10/A02_2021-Cryptographic_Failures/">Top 10 2021 Category A2 - Cryptographic Failures</a> </li>
-  <li> OWASP - <a href="https://owasp.org/Top10/A04_2021-Insecure_Design/">Top 10 2021 Category A4 - Insecure Design</a> </li>
-  <li> OWASP - <a href="https://owasp.org/Top10/A05_2021-Security_Misconfiguration/">Top 10 2021 Category A5 - Security Misconfiguration</a> </li>
   <li> <a href="https://docs.aws.amazon.com/efs/latest/ug/encryption.html">Data encryption in Amazon EFS</a> </li>
-  <li> OWASP - <a href="https://owasp.org/www-project-top-ten/2017/A3_2017-Sensitive_Data_Exposure">Top 10 2017 Category A3 - Sensitive Data
-  Exposure</a> </li>
-  <li> OWASP - <a href="https://owasp.org/www-project-top-ten/2017/A6_2017-Security_Misconfiguration">Top 10 2017 Category A6 - Security
-  Misconfiguration</a> </li>
   <li> CWE - <a href="https://cwe.mitre.org/data/definitions/311">CWE-311 - Missing Encryption of Sensitive Data</a> </li>
   <li> <a href="https://learn.microsoft.com/en-us/azure/backup/backup-encryption">Encryption in Azure Backup</a> </li>
   <li> <a href="https://learn.microsoft.com/en-us/azure/mysql/single-server/concepts-security">Security in Azure Database for MySQL</a> </li>

diff --git a/iac-extensions/cloudformation/sonarpedia.json b/iac-extensions/cloudformation/sonarpedia.json
@@ -3,7 +3,7 @@
   "languages": [
     "CLOUD_FORMATION"
   ],
-  "latest-update": "2024-01-17T14:02:24.681804021Z",
+  "latest-update": "2024-01-29T14:21:18.071364Z",
   "options": {
     "no-language-in-filenames": true,
     "preserve-filenames": true

diff --git a/...ormation/src/main/resources/org/sonar/l10n/cloudformation/rules/cloudformation/S1135.html b/...ormation/src/main/resources/org/sonar/l10n/cloudformation/rules/cloudformation/S1135.html
@@ -1,8 +1,8 @@
 <h2>Why is this an issue?</h2>
 <p>Developers often use <code>TODO</code> tags to mark areas in the code where additional work or improvements are needed but are not implemented
-immediately. However, these <code>TODO</code> tags sometimes get overlooked or forgotten, leading to incomplete or unfinished code. This code smell
-class aims to identify and address such unattended <code>TODO</code> tags to ensure a clean and maintainable codebase. This description will explore
-why this is a problem and how it can be fixed to improve the overall code quality.</p>
+immediately. However, these <code>TODO</code> tags sometimes get overlooked or forgotten, leading to incomplete or unfinished code. This rule aims to
+identify and address unattended <code>TODO</code> tags to ensure a clean and maintainable codebase. This description explores why this is a problem
+and how it can be fixed to improve the overall code quality.</p>
 <h3>What is the potential impact?</h3>
 <p>Unattended <code>TODO</code> tags in code can have significant implications for the development process and the overall codebase.</p>
 <p>Incomplete Functionality: When developers leave <code>TODO</code> tags without implementing the corresponding code, it results in incomplete
@@ -11,8 +11,8 @@ <h3>What is the potential impact?</h3>
 Delayed bug fixes can result in more severe issues and increase the effort required to resolve them later.</p>
 <p>Impact on Collaboration: In team-based development environments, unattended <code>TODO</code> tags can hinder collaboration. Other team members
 might not be aware of the intended changes, leading to conflicts or redundant efforts in the codebase.</p>
-<p>Codebase Bloat: Accumulation of unattended <code>TODO</code> tags over time can clutter the codebase and make it difficult to distinguish between
-work in progress and completed code. This bloat can make it challenging to maintain an organized and efficient codebase.</p>
+<p>Codebase Bloat: The accumulation of unattended <code>TODO</code> tags over time can clutter the codebase and make it difficult to distinguish
+between work in progress and completed code. This bloat can make it challenging to maintain an organized and efficient codebase.</p>
 <p>Addressing this code smell is essential to ensure a maintainable, readable, reliable codebase and promote effective collaboration among
 developers.</p>
 <h3>Noncompliant code example</h3>

diff --git a/...ormation/src/main/resources/org/sonar/l10n/cloudformation/rules/cloudformation/S4423.html b/...ormation/src/main/resources/org/sonar/l10n/cloudformation/rules/cloudformation/S4423.html
@@ -139,9 +139,6 @@ <h3>Articles &amp; blog posts</h3>
 </ul>
 <h3>Standards</h3>
 <ul>
-  <li> OWASP - <a href="https://owasp.org/Top10/A02_2021-Cryptographic_Failures/">Top 10 2021 Category A2 - Cryptographic Failures</a> </li>
-  <li> OWASP - <a href="https://owasp.org/www-project-top-ten/2017/A6_2017-Security_Misconfiguration">Top 10 2017 Category A6 - Security
-  Misconfiguration</a> </li>
   <li> CWE - <a href="https://cwe.mitre.org/data/definitions/327">CWE-327 - Use of a Broken or Risky Cryptographic Algorithm</a> </li>
 </ul>
 
diff --git a/...ormation/src/main/resources/org/sonar/l10n/cloudformation/rules/cloudformation/S5332.html b/...ormation/src/main/resources/org/sonar/l10n/cloudformation/rules/cloudformation/S5332.html
@@ -207,13 +207,6 @@ <h2>Compliant Solution</h2>
 </pre>
 <h2>See</h2>
 <ul>
-  <li> OWASP - <a href="https://owasp.org/Top10/A02_2021-Cryptographic_Failures/">Top 10 2021 Category A2 - Cryptographic Failures</a> </li>
-  <li> OWASP - <a href="https://owasp.org/www-project-top-ten/2017/A3_2017-Sensitive_Data_Exposure">Top 10 2017 Category A3 - Sensitive Data Exposure
-  </a> </li>
-  <li> OWASP - <a href="https://mobile-security.gitbook.io/masvs/security-requirements/0x10-v5-network_communication_requirements">Mobile AppSec
-  Verification Standard - Network Communication Requirements</a> </li>
-  <li> OWASP - <a href="https://owasp.org/www-project-mobile-top-10/2016-risks/m3-insecure-communication">Mobile Top 10 2016 Category M3 - Insecure
-  Communication</a> </li>
   <li> CWE - <a href="https://cwe.mitre.org/data/definitions/200">CWE-200 - Exposure of Sensitive Information to an Unauthorized Actor</a> </li>
   <li> CWE - <a href="https://cwe.mitre.org/data/definitions/319">CWE-319 - Cleartext Transmission of Sensitive Information</a> </li>
   <li> <a href="https://security.googleblog.com/2016/09/moving-towards-more-secure-web.html">Google, Moving towards more secure web</a> </li>

diff --git a/...ormation/src/main/resources/org/sonar/l10n/cloudformation/rules/cloudformation/S6245.html b/...ormation/src/main/resources/org/sonar/l10n/cloudformation/rules/cloudformation/S6245.html
@@ -50,13 +50,6 @@ <h2>Compliant Solution</h2>
 </pre>
 <h2>See</h2>
 <ul>
-  <li> OWASP - <a href="https://owasp.org/Top10/A04_2021-Insecure_Design/">Top 10 2021 Category A4 - Insecure Design</a> </li>
-  <li> OWASP - <a href="https://owasp.org/Top10/A05_2021-Security_Misconfiguration/">Top 10 2021 Category A5 - Security Misconfiguration</a> </li>
-  <li> CWE - <a href="https://cwe.mitre.org/data/definitions/311">CWE-311 - Missing Encryption of Sensitive Data</a> </li>
-  <li> OWASP - <a href="https://owasp.org/www-project-top-ten/2017/A3_2017-Sensitive_Data_Exposure">Top 10 2017 Category A3 - Sensitive Data
-  Exposure</a> </li>
-  <li> OWASP - <a href="https://owasp.org/www-project-top-ten/2017/A6_2017-Security_Misconfiguration">Top 10 2017 Category A6 - Security
-  Misconfiguration</a> </li>
   <li> <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/serv-side-encryption.html">AWS documentation</a> - Protecting data using
   server-side encryption </li>
 </ul>

diff --git a/...ormation/src/main/resources/org/sonar/l10n/cloudformation/rules/cloudformation/S6249.html b/...ormation/src/main/resources/org/sonar/l10n/cloudformation/rules/cloudformation/S6249.html
@@ -76,12 +76,6 @@ <h2>Compliant Solution</h2>
 </pre>
 <h2>See</h2>
 <ul>
-  <li> OWASP - <a href="https://owasp.org/Top10/A02_2021-Cryptographic_Failures/">Top 10 2021 Category A2 - Cryptographic Failures</a> </li>
-  <li> OWASP - <a href="https://owasp.org/Top10/A05_2021-Security_Misconfiguration/">Top 10 2021 Category A5 - Security Misconfiguration</a> </li>
-  <li> OWASP - <a href="https://owasp.org/www-project-top-ten/2017/A3_2017-Sensitive_Data_Exposure">Top 10 2017 Category A3 - Sensitive Data
-  Exposure</a> </li>
-  <li> OWASP - <a href="https://owasp.org/www-project-top-ten/2017/A6_2017-Security_Misconfiguration">Top 10 2017 Category A6 - Security
-  Misconfiguration</a> </li>
   <li> <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/security-best-practices.html#transit">AWS documentation</a> - Enforce encryption
   of data in transit </li>
   <li> <a href="https://docs.aws.amazon.com/securityhub/latest/userguide/securityhub-standards-fsbp-controls.html#fsbp-s3-5">AWS Foundational Security

diff --git a/...ormation/src/main/resources/org/sonar/l10n/cloudformation/rules/cloudformation/S6252.html b/...ormation/src/main/resources/org/sonar/l10n/cloudformation/rules/cloudformation/S6252.html
@@ -38,9 +38,6 @@ <h2>Compliant Solution</h2>
 </pre>
 <h2>See</h2>
 <ul>
-  <li> OWASP - <a href="https://owasp.org/Top10/A05_2021-Security_Misconfiguration/">Top 10 2021 Category A5 - Security Misconfiguration</a> </li>
-  <li> OWASP - <a href="https://owasp.org/www-project-top-ten/2017/A6_2017-Security_Misconfiguration">Top 10 2017 Category A6 - Security
-  Misconfiguration</a> </li>
   <li> <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/Versioning.html">AWS documentation</a> - Using versioning in S3 buckets </li>
 </ul>
 
diff --git a/...ormation/src/main/resources/org/sonar/l10n/cloudformation/rules/cloudformation/S6258.html b/...ormation/src/main/resources/org/sonar/l10n/cloudformation/rules/cloudformation/S6258.html
@@ -287,12 +287,8 @@ <h2>Compliant Solution</h2>
 </pre>
 <h2>See</h2>
 <ul>
-  <li> OWASP - <a href="https://owasp.org/Top10/A09_2021-Security_Logging_and_Monitoring_Failures/">Top 10 2021 Category A9 - Security Logging and
-  Monitoring Failures</a> </li>
   <li> <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/ServerLogs.html">AWS Documentation</a> - Logging requests using server access
   logging </li>
   <li> CWE - <a href="https://cwe.mitre.org/data/definitions/778">CWE-778 - Insufficient Logging</a> </li>
-  <li> OWASP - <a href="https://owasp.org/www-project-top-ten/2017/A10_2017-Insufficient_Logging%2526Monitoring">Top 10 2017 Category A10 -
-  Insufficient Logging &amp; Monitoring</a> </li>
 </ul>
 
diff --git a/...ormation/src/main/resources/org/sonar/l10n/cloudformation/rules/cloudformation/S6265.html b/...ormation/src/main/resources/org/sonar/l10n/cloudformation/rules/cloudformation/S6265.html
@@ -39,14 +39,11 @@ <h2>Compliant Solution</h2>
 </pre>
 <h2>See</h2>
 <ul>
-  <li> OWASP - <a href="https://owasp.org/Top10/A01_2021-Broken_Access_Control/">Top 10 2021 Category A1 - Broken Access Control</a> </li>
   <li> <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/acl-overview.html#canned-acl">AWS Documentation</a> - Access control list (ACL)
   overview (canned ACLs) </li>
   <li> <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/walkthrough1.html">AWS Documentation</a> - Controlling access to a bucket with
   user policies </li>
   <li> CWE - <a href="https://cwe.mitre.org/data/definitions/732">CWE-732 - Incorrect Permission Assignment for Critical Resource</a> </li>
   <li> CWE - <a href="https://cwe.mitre.org/data/definitions/284">CWE-284 - Improper Access Control</a> </li>
-  <li> OWASP - <a href="https://owasp.org/www-project-top-ten/2017/A5_2017-Broken_Access_Control">Top 10 2017 Category A5 - Broken Access Control</a>
-  </li>
 </ul>
 
diff --git a/...ormation/src/main/resources/org/sonar/l10n/cloudformation/rules/cloudformation/S6270.html b/...ormation/src/main/resources/org/sonar/l10n/cloudformation/rules/cloudformation/S6270.html
@@ -47,12 +47,9 @@ <h2>Compliant Solution</h2>
 </pre>
 <h2>See</h2>
 <ul>
-  <li> OWASP - <a href="https://owasp.org/Top10/A01_2021-Broken_Access_Control/">Top 10 2021 Category A1 - Broken Access Control</a> </li>
   <li> <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html#grant-least-privilege">AWS Documentation</a> - Grant least
   privilege </li>
   <li> CWE - <a href="https://cwe.mitre.org/data/definitions/732">CWE-732 - Incorrect Permission Assignment for Critical Resource</a> </li>
   <li> CWE - <a href="https://cwe.mitre.org/data/definitions/284">CWE-284 - Improper Access Control</a> </li>
-  <li> OWASP - <a href="https://owasp.org/www-project-top-ten/2017/A5_2017-Broken_Access_Control">Top 10 2017 Category A5 - Broken Access Control</a>
-  </li>
 </ul>