Reino: Environment

Esta seção contém tudo o que fica fora do código-fonte, porém que é essencial para a segurança do produto que está sendo criado. Como os problemas tratados neste domínio não são diretamente relacionados com o código-fonte, nós o separamos dos demais domínios.

GCP Terraform Misconfiguration: Insufficient GKE Cluster Logging

Abstract

Uma configuração do Terraform desabilita o serviço de registro em log de um cluster do Google Kubernetes Engine.

Explanation

Por padrão, um cluster do Google Kubernetes Engine (GKE) grava logs no Stackdriver Kubernetes Engine Logging Service. A configuração do Terraform configura um cluster do GKE e desabilita explicitamente o serviço de registro em log. Os logs contêm dados valiosos usados para identificar incidentes de segurança, monitorar violações de políticas e auxiliar nos controles de não repúdio.

Exemplo 1: O exemplo a seguir mostra uma configuração do Terraform que desabilita o serviço de registro em log de um cluster do GKE definindo logging_service como none.


resource "google_container_cluster" "cluster-demo" {
    name            = "name-demo"
    location        = "us-central1-a"
    logging_service = "none"
    ...
}

References

[1] HashiCorp google_container_cluster

[2] Google Cloud Configuring Cloud Operations for GKE

[3] Standards Mapping - Common Weakness Enumeration CWE ID 778

[4] Standards Mapping - DISA Control Correlation Identifier Version 2 CCI-000172

[5] Standards Mapping - FIPS200 CM

[6] Standards Mapping - General Data Protection Regulation (GDPR) Indirect Access to Sensitive Data

[7] Standards Mapping - NIST Special Publication 800-53 Revision 4 AU-12 Audit Generation (P1)

[8] Standards Mapping - NIST Special Publication 800-53 Revision 5 AU-12 Audit Record Generation

[9] Standards Mapping - OWASP API 2023 API8 Security Misconfiguration

[10] Standards Mapping - OWASP Application Security Verification Standard 4.0 7.1.3 Log Content Requirements (L2 L3), 7.1.4 Log Content Requirements (L2 L3), 7.2.1 Log Processing Requirements (L2 L3), 7.2.2 Log Processing Requirements (L2 L3)

[11] Standards Mapping - OWASP Top 10 2017 A6 Security Misconfiguration, A10 Insufficient Logging and Monitoring

[12] Standards Mapping - OWASP Top 10 2021 A09 Security Logging and Monitoring Failures

[13] Standards Mapping - Payment Card Industry Data Security Standard Version 3.2.1 Requirement 10.2.1, Requirement 10.2.4, Requirement 10.3.4

[14] Standards Mapping - Payment Card Industry Data Security Standard Version 4.0 Requirement 10.2.1, Requirement 10.2.1.4, Requirement 10.2.2

[15] Standards Mapping - Payment Card Industry Data Security Standard Version 4.0.1 Requirement 10.2.1, Requirement 10.2.1.4, Requirement 10.2.2

[16] Standards Mapping - Payment Card Industry Software Security Framework 1.0 Control Objective 8.2 - Activity Tracking

[17] Standards Mapping - Payment Card Industry Software Security Framework 1.1 Control Objective 8.2 - Activity Tracking

[18] Standards Mapping - Payment Card Industry Software Security Framework 1.2 Control Objective 8.2 - Activity Tracking

[19] Standards Mapping - Security Technical Implementation Guide Version 4.11 APSC-DV-000830 CAT II

[20] Standards Mapping - Security Technical Implementation Guide Version 5.1 APSC-DV-000830 CAT II

[21] Standards Mapping - Security Technical Implementation Guide Version 5.2 APSC-DV-000830 CAT II

[22] Standards Mapping - Security Technical Implementation Guide Version 5.3 APSC-DV-000830 CAT II

[23] Standards Mapping - Security Technical Implementation Guide Version 6.1 APSC-DV-000830 CAT II

[24] Standards Mapping - Security Technical Implementation Guide Version 6.2 APSC-DV-000830 CAT II

desc.structural.hcl.gcp_terraform_misconfiguration_insufficient_gke_cluster_logging