Kingdom: Encapsulation

Encapsulation is about drawing strong boundaries. In a web browser that might mean ensuring that your mobile code cannot be abused by other mobile code. On the server it might mean differentiation between validated data and unvalidated data, between one user's data and another's, or between data users are allowed to see and data that they are not.

AWS CloudFormation Misconfiguration: Insecure Neptune DB Storage

JSON
YAML

Abstract

The template defines a Neptune DB cluster without encryption of data at rest.

Explanation

By default, Neptune DB clusters are not encrypted. This exposes the data to potential theft and unauthorized access by attackers.

Example 1: The following example template fails to enable encryption at rest.


{
    "AWSTemplateFormatVersion": "2010-09-09",
    "Description": "My Neptune DB cluster",
    "Resources": {
        "NeptuneDBCluster": {
            "Type": "AWS::Neptune::DBCluster",
            "Properties": {
                "BackupRetentionPeriod": 10,
                "DBClusterIdentifier": "MyDBClusterIdentifier",
                "DBClusterParameterGroupName": "MyNeptuneDBClusterParameterGroup",
                "DBSubnetGroupName": "MyNeptuneDBSubnetGroup",
                "IamAuthEnabled": true,
                "Port": 8080,
                "PreferredBackupWindow": "NeptuneDBClusterPreferredBackupWindow",
                "PreferredMaintenanceWindow": "NeptuneDBClusterPreferredMaintenanceWindow"
            }
        }
    }
}

References

[1] AWS AWS Documentation: Encrypting Neptune Resources at Rest

[2] AWS AWS Documentation: Protecting Data at Rest

[3] AWS AWS Documentation: Data Protection in Neptune

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

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

[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 - 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 APP3500 CAT II

[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_neptune_db_storage.base

Abstract

The template defines a Neptune DB cluster without encryption of data at rest.

Explanation


AWSTemplateFormatVersion: 2010-09-09
Description: My Neptune DB cluster
Resources:
  NeptuneDBCluster:
    Type: "AWS::Neptune::DBCluster"
    Properties:
      BackupRetentionPeriod: 10
      DBClusterIdentifier: MyDBClusterIdentifier
      DBClusterParameterGroupName: MyNeptuneDBClusterParameterGroup
      DBSubnetGroupName: MyNeptuneDBSubnetGroup
      IamAuthEnabled: true
      Port: 8080
      PreferredBackupWindow: NeptuneDBClusterPreferredBackupWindow
      PreferredMaintenanceWindow: NeptuneDBClusterPreferredMaintenanceWindow