Reino: Encapsulation

La encapsulación consiste en crear límites fuertes. En un explorador web esto puede suponer la seguridad de que tu codificación móvil no se vea comprometido por otro código móvil. En el servidor puede significar la diferenciación entre los datos validados y los que no lo están, entre los datos de un usuario y los de otro, o entre los diferentes usuarios, los datos que pueden ver y los que no.

AWS CloudFormation Misconfiguration: Insecure Redshift Storage

JSON
YAML

Abstract

La plantilla define un clúster de Amazon Redshift sin cifrado.

Explanation

De forma predeterminada, los clústeres de Amazon Redshift no están cifrados. Esto expone los datos al acceso no autorizado y posible robo.

Ejemplo 1: La siguiente plantilla define un clúster de Redshift sin cifrado habilitado.


"Resources": {
    "RedshiftClusterTest": {
        "Type": "AWS::Redshift::Cluster",
        "Properties": {
            "DBName": "mydb",
            "MasterUsername": "master",
            "MasterUserPassword": "masterPass",
            "NodeType": "ds2.xlarge",
            "ClusterType": "single-node",
        }
    }

References

[1] Amazon Web Services Amazon Redshift database encryption

[2] Standards Mapping - Common Weakness Enumeration CWE ID 311

[3] Standards Mapping - DISA Control Correlation Identifier Version 2 CCI-002475

[4] Standards Mapping - FIPS200 MP

[5] Standards Mapping - General Data Protection Regulation (GDPR) Insufficient Data Protection

[6] Standards Mapping - NIST Special Publication 800-53 Revision 4 SC-28 Protection of Information at Rest (P1)

[7] Standards Mapping - NIST Special Publication 800-53 Revision 5 SC-28 Protection of Information at Rest

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

[9] Standards Mapping - OWASP Application Security Verification Standard 4.0 2.6.3 Look-up Secret Verifier Requirements (L2 L3), 6.2.1 Algorithms (L1 L2 L3), 8.1.6 General Data Protection (L3)

[10] Standards Mapping - OWASP Mobile 2014 M2 Insecure Data Storage

[11] Standards Mapping - OWASP Top 10 2004 A8 Insecure Storage

[12] Standards Mapping - OWASP Top 10 2007 A8 Insecure Cryptographic Storage

[13] Standards Mapping - OWASP Top 10 2010 A7 Insecure Cryptographic Storage

[14] Standards Mapping - OWASP Top 10 2013 A6 Sensitive Data Exposure

[15] Standards Mapping - OWASP Top 10 2017 A3 Sensitive Data Exposure

[16] Standards Mapping - OWASP Top 10 2021 A02 Cryptographic Failures

[17] Standards Mapping - Payment Card Industry Data Security Standard Version 3.0 Requirement 6.5.3

[18] Standards Mapping - Payment Card Industry Data Security Standard Version 3.1 Requirement 6.5.3

[19] Standards Mapping - Payment Card Industry Data Security Standard Version 3.2 Requirement 6.5.3

[20] Standards Mapping - Payment Card Industry Data Security Standard Version 3.2.1 Requirement 6.5.3

[21] Standards Mapping - Payment Card Industry Data Security Standard Version 4.0 Requirement 6.2.4, Requirement 3.5.1

[22] Standards Mapping - Payment Card Industry Software Security Framework 1.0 Control Objective 6.3 - Sensitive Data Protection, Control Objective 7 - Use of Cryptography

[23] Standards Mapping - Payment Card Industry Software Security Framework 1.1 Control Objective 6.3 - Sensitive Data Protection, Control Objective 7 - Use of Cryptography, Control Objective B.2.5 - Terminal Software Design

[24] Standards Mapping - Payment Card Industry Software Security Framework 1.2 Control Objective 6.3 - Sensitive Data Protection, Control Objective 7 - Use of Cryptography, Control Objective B.2.5 - Terminal Software Design

[25] Standards Mapping - SANS Top 25 2010 Porous Defenses - CWE ID 311

[26] Standards Mapping - SANS Top 25 2011 Porous Defenses - CWE ID 311

[27] Standards Mapping - Security Technical Implementation Guide Version 3.1 APP3210.1 CAT II, APP3310 CAT I, APP3340 CAT I

[28] Standards Mapping - Security Technical Implementation Guide Version 3.4 APP3210.1 CAT II, APP3340 CAT I

[29] Standards Mapping - Security Technical Implementation Guide Version 3.5 APP3210.1 CAT II, APP3340 CAT I

[30] Standards Mapping - Security Technical Implementation Guide Version 3.6 APP3210.1 CAT II, APP3340 CAT I

[31] Standards Mapping - Security Technical Implementation Guide Version 3.7 APP3210.1 CAT II, APP3340 CAT I

[32] Standards Mapping - Security Technical Implementation Guide Version 3.9 APP3210.1 CAT II, APP3340 CAT I

[33] Standards Mapping - Security Technical Implementation Guide Version 3.10 APP3210.1 CAT II, APP3340 CAT I

[34] Standards Mapping - Security Technical Implementation Guide Version 4.2 APSC-DV-002340 CAT II

[35] Standards Mapping - Security Technical Implementation Guide Version 4.3 APSC-DV-002340 CAT II

[36] Standards Mapping - Security Technical Implementation Guide Version 4.4 APSC-DV-002340 CAT II

[37] Standards Mapping - Security Technical Implementation Guide Version 4.5 APSC-DV-002340 CAT II

[38] Standards Mapping - Security Technical Implementation Guide Version 4.6 APSC-DV-002340 CAT II

[39] Standards Mapping - Security Technical Implementation Guide Version 4.7 APSC-DV-002340 CAT II

[40] Standards Mapping - Security Technical Implementation Guide Version 4.8 APSC-DV-002340 CAT II

[41] Standards Mapping - Security Technical Implementation Guide Version 4.9 APSC-DV-002340 CAT II

[42] Standards Mapping - Security Technical Implementation Guide Version 4.10 APSC-DV-002340 CAT II

[43] Standards Mapping - Security Technical Implementation Guide Version 4.11 APSC-DV-002340 CAT II

[44] Standards Mapping - Security Technical Implementation Guide Version 4.1 APSC-DV-002340 CAT II

[45] Standards Mapping - Security Technical Implementation Guide Version 5.1 APSC-DV-002340 CAT II

[46] Standards Mapping - Security Technical Implementation Guide Version 5.2 APSC-DV-002340 CAT II

[47] Standards Mapping - Security Technical Implementation Guide Version 5.3 APSC-DV-002340 CAT II

[48] Standards Mapping - Security Technical Implementation Guide Version 6.1 APSC-DV-002340 CAT II

[49] Standards Mapping - Web Application Security Consortium Version 2.00 Information Leakage (WASC-13)

desc.structural.json.aws_cloudformation_misconfiguration_insecure_redshift_storage.base

Abstract

La plantilla define un clúster de Amazon Redshift sin cifrado.

Explanation

De forma predeterminada, los clústeres de Amazon Redshift no están cifrados. Esto expone los datos al acceso no autorizado y posible robo.

References

[1] Ansible project contributors community.aws.redshift – create, delete, or modify an Amazon Redshift instance

[2] Amazon Web Services Amazon Redshift database encryption

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

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

[5] Standards Mapping - FIPS200 MP

[6] Standards Mapping - General Data Protection Regulation (GDPR) Insufficient Data Protection

[7] Standards Mapping - NIST Special Publication 800-53 Revision 4 SC-28 Protection of Information at Rest (P1)

[8] Standards Mapping - NIST Special Publication 800-53 Revision 5 SC-28 Protection of Information at Rest

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

[10] Standards Mapping - OWASP Application Security Verification Standard 4.0 2.6.3 Look-up Secret Verifier Requirements (L2 L3), 6.2.1 Algorithms (L1 L2 L3), 8.1.6 General Data Protection (L3)

[11] Standards Mapping - OWASP Mobile 2014 M2 Insecure Data Storage

[12] Standards Mapping - OWASP Top 10 2004 A8 Insecure Storage

[13] Standards Mapping - OWASP Top 10 2007 A8 Insecure Cryptographic Storage

[14] Standards Mapping - OWASP Top 10 2010 A7 Insecure Cryptographic Storage

[15] Standards Mapping - OWASP Top 10 2013 A6 Sensitive Data Exposure

[16] Standards Mapping - OWASP Top 10 2017 A3 Sensitive Data Exposure

[17] Standards Mapping - OWASP Top 10 2021 A02 Cryptographic Failures

[18] Standards Mapping - Payment Card Industry Data Security Standard Version 3.0 Requirement 6.5.3

[19] Standards Mapping - Payment Card Industry Data Security Standard Version 3.1 Requirement 6.5.3

[20] Standards Mapping - Payment Card Industry Data Security Standard Version 3.2 Requirement 6.5.3

[21] Standards Mapping - Payment Card Industry Data Security Standard Version 3.2.1 Requirement 6.5.3

[22] Standards Mapping - Payment Card Industry Data Security Standard Version 4.0 Requirement 6.2.4, Requirement 3.5.1

[23] Standards Mapping - Payment Card Industry Software Security Framework 1.0 Control Objective 6.3 - Sensitive Data Protection, Control Objective 7 - Use of Cryptography

[24] Standards Mapping - Payment Card Industry Software Security Framework 1.1 Control Objective 6.3 - Sensitive Data Protection, Control Objective 7 - Use of Cryptography, Control Objective B.2.5 - Terminal Software Design

[25] Standards Mapping - Payment Card Industry Software Security Framework 1.2 Control Objective 6.3 - Sensitive Data Protection, Control Objective 7 - Use of Cryptography, Control Objective B.2.5 - Terminal Software Design

[26] Standards Mapping - SANS Top 25 2010 Porous Defenses - CWE ID 311

[27] Standards Mapping - SANS Top 25 2011 Porous Defenses - CWE ID 311

[28] Standards Mapping - Security Technical Implementation Guide Version 3.1 APP3210.1 CAT II, APP3310 CAT I, APP3340 CAT I

[29] Standards Mapping - Security Technical Implementation Guide Version 3.4 APP3210.1 CAT II, APP3340 CAT I

[30] Standards Mapping - Security Technical Implementation Guide Version 3.5 APP3210.1 CAT II, APP3340 CAT I

[31] Standards Mapping - Security Technical Implementation Guide Version 3.6 APP3210.1 CAT II, APP3340 CAT I

[32] Standards Mapping - Security Technical Implementation Guide Version 3.7 APP3210.1 CAT II, APP3340 CAT I

[33] Standards Mapping - Security Technical Implementation Guide Version 3.9 APP3210.1 CAT II, APP3340 CAT I

[34] Standards Mapping - Security Technical Implementation Guide Version 3.10 APP3210.1 CAT II, APP3340 CAT I

[35] Standards Mapping - Security Technical Implementation Guide Version 4.2 APSC-DV-002340 CAT II

[36] Standards Mapping - Security Technical Implementation Guide Version 4.3 APSC-DV-002340 CAT II

[37] Standards Mapping - Security Technical Implementation Guide Version 4.4 APSC-DV-002340 CAT II

[38] Standards Mapping - Security Technical Implementation Guide Version 4.5 APSC-DV-002340 CAT II

[39] Standards Mapping - Security Technical Implementation Guide Version 4.6 APSC-DV-002340 CAT II

[40] Standards Mapping - Security Technical Implementation Guide Version 4.7 APSC-DV-002340 CAT II

[41] Standards Mapping - Security Technical Implementation Guide Version 4.8 APSC-DV-002340 CAT II

[42] Standards Mapping - Security Technical Implementation Guide Version 4.9 APSC-DV-002340 CAT II

[43] Standards Mapping - Security Technical Implementation Guide Version 4.10 APSC-DV-002340 CAT II

[44] Standards Mapping - Security Technical Implementation Guide Version 4.11 APSC-DV-002340 CAT II

[45] Standards Mapping - Security Technical Implementation Guide Version 4.1 APSC-DV-002340 CAT II

[46] Standards Mapping - Security Technical Implementation Guide Version 5.1 APSC-DV-002340 CAT II

[47] Standards Mapping - Security Technical Implementation Guide Version 5.2 APSC-DV-002340 CAT II

[48] Standards Mapping - Security Technical Implementation Guide Version 5.3 APSC-DV-002340 CAT II

[49] Standards Mapping - Security Technical Implementation Guide Version 6.1 APSC-DV-002340 CAT II

[50] Standards Mapping - Web Application Security Consortium Version 2.00 Information Leakage (WASC-13)

desc.structural.yaml.aws_ansible_misconfiguration_insecure_redshift_storage.base