f4696dbf01
* Remove AWS specific words * Add Azure code samples * Add Azure link * Add missing tags * Add samples * Update rules/S6321/metadata.json Co-authored-by: Loris S. <91723853+loris-s-sonarsource@users.noreply.github.com> * Update rules/S6321/terraform/metadata.json Co-authored-by: Loris S. <91723853+loris-s-sonarsource@users.noreply.github.com> * Remove AWS tag * Make description more generic * Update rules/S6321/description.adoc Co-authored-by: Loris S. <91723853+loris-s-sonarsource@users.noreply.github.com> * Remove GCP tag * Update rules/S6321/see.adoc Co-authored-by: Loris S. <91723853+loris-s-sonarsource@users.noreply.github.com> * Remove Azure tag Co-authored-by: Loris S. <91723853+loris-s-sonarsource@users.noreply.github.com> Co-authored-by: Nils Werner <64034005+nils-werner-sonarsource@users.noreply.github.com>
2 lines
384 B
Plaintext
2 lines
384 B
Plaintext
Cloud platforms such as AWS, Azure, or GCP support virtual firewalls that can be used to restrict access to services by controlling inbound and outbound traffic. +
|
|
Any firewall rule allowing traffic from all IP addresses to standard network ports on which administration services traditionally listen, such as 22 for SSH, can expose these services to exploits and unauthorized access. |