182 找到的項目

弱點

AWS CloudFormation Misconfiguration: Insecure RDS Storage

JSON
YAML

Abstract

範本將定義一個沒有加密的 Amazon RDS 執行個體。

Explanation

依預設，Amazon RDS 執行個體不會加密。這會將資料暴露於潛在竊取和未經授權存取的風險。


"Resources": {
    "RDSDBExample": {
        "Type": "AWS::RDS::DBInstance",
        "Properties": {
            "StorageEncrypted": false,
            "DBName": "Test DB",
            "DBInstanceClass": "db.m4.large"
        }
    }
}

References

[1] Amazon Web Services Encrypting Amazon RDS resources

[2] Amazon Web Services Security in Amazon RDS

[3] Standards Mapping - CIS Azure Kubernetes Service Benchmark 3

[4] Standards Mapping - CIS Microsoft Azure Foundations Benchmark partial

[5] Standards Mapping - CIS Amazon Elastic Kubernetes Service Benchmark 5

[6] Standards Mapping - CIS Amazon Web Services Foundations Benchmark 1

[7] Standards Mapping - CIS Google Kubernetes Engine Benchmark confidentiality

[8] Standards Mapping - CIS Kubernetes Benchmark complete

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

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

[11] Standards Mapping - FIPS200 MP

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

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

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

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

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

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

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

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

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

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

[22] 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)

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

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

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

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

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

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

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

[30] 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

[31] 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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

desc.structural.json.aws_cloudformation_misconfiguration_insecure_rds_storage.base

Abstract

範本將定義一個沒有加密的 Amazon RDS 執行個體。

Explanation

依預設，Amazon RDS 執行個體不會加密。這會將資料暴露於潛在竊取和未經授權存取的風險。

References

[1] Ansible project contributors community.aws.rds_instance – Manage RDS instances

[2] Amazon Web Services Encrypting Amazon RDS resources

[3] Amazon Web Services Security in Amazon RDS

[4] Standards Mapping - CIS Azure Kubernetes Service Benchmark 3

[5] Standards Mapping - CIS Microsoft Azure Foundations Benchmark partial

[6] Standards Mapping - CIS Amazon Elastic Kubernetes Service Benchmark 5

[7] Standards Mapping - CIS Amazon Web Services Foundations Benchmark 1

[8] Standards Mapping - CIS Google Kubernetes Engine Benchmark confidentiality

[9] Standards Mapping - CIS Kubernetes Benchmark complete

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

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

[12] Standards Mapping - FIPS200 MP

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

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

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

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

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

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

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

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

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

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

[23] 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)

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

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

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

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

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

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

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

[31] 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

[32] 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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

desc.structural.yaml.aws_cloudformation_misconfiguration_insecure_rds_storage.base

AWS CloudFormation Misconfiguration: Insecure Redshift Storage

JSON
YAML

Abstract

範本將定義一個沒有加密的 Amazon Redshift 叢集。

Explanation

依預設，Amazon Redshift 叢集不會加密。如此會使資料暴露於未經授權存取和潛在竊取的風險。

範例 1：以下範本將定義一個未啟用加密的 Redshift 叢集。


"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 - CIS Azure Kubernetes Service Benchmark 2

[3] Standards Mapping - CIS Microsoft Azure Foundations Benchmark partial

[4] Standards Mapping - CIS Amazon Elastic Kubernetes Service Benchmark 2

[5] Standards Mapping - CIS Amazon Web Services Foundations Benchmark 1

[6] Standards Mapping - CIS Google Kubernetes Engine Benchmark confidentiality

[7] Standards Mapping - CIS Kubernetes Benchmark complete

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

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

[10] Standards Mapping - FIPS200 MP

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

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

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

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

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

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

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

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

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

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

[21] 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)

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

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

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

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

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

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

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

[29] 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

[30] 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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

desc.structural.json.aws_cloudformation_misconfiguration_insecure_redshift_storage.base

Abstract

範本將定義一個沒有加密的 Amazon Redshift 叢集。

Explanation

依預設，Amazon Redshift 叢集不會加密。如此會使資料暴露於未經授權存取和潛在竊取的風險。

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 - CIS Azure Kubernetes Service Benchmark 2

[4] Standards Mapping - CIS Microsoft Azure Foundations Benchmark partial

[5] Standards Mapping - CIS Amazon Elastic Kubernetes Service Benchmark 2