0.5.0 • Published 12 months ago

@cloudgraph/policy-pack-aws-cis-1.3.0 v0.5.0

Weekly downloads
-
License
MPL-2.0
Repository
github
Last release
12 months ago

CIS Amazon Web Services Foundations 1.3.0

Policy Pack based on the AWS Foundations 1.3.0 benchmark provided by the Center for Internet Security (CIS)

First Steps

  1. Install Cloud Graph CLI.
  2. Set up the AWS Provider for CG with the cg init aws command.
  3. Add Policy Pack for CIS Amazon Web Services Foundations benchmark using cg policy add aws-cis-1.3.0 command.
  4. Execute the ruleset using the scan command cg scan aws.
  5. Query the findings using the different options:

    5a. Querying findings by provider:

    query {
      queryawsFindings {
        CISFindings {
          id
          resourceId
          result
        }
      }
    }

    5b. Querying findings by specific benchmark:

    query {
      queryawsCISFindings {
        id
        resourceId
        result
      }
    }

    5c. Querying findings by resource:

    query {
      queryawsIamUser {
        id
        arn
        accountId
        CISFindings {
          id
          resourceId
          result
        }
      }
    }

Available Ruleset

RuleDescription
AWS CIS 1.1Maintain current contact details
AWS CIS 1.2Ensure security contact information is registered
AWS CIS 1.3Ensure security questions are registered in the AWS account
AWS CIS 1.4Ensure no 'root' user account access key exists
AWS CIS 1.5Ensure MFA is enabled for the 'root user' account
AWS CIS 1.6Ensure hardware MFA is enabled for the 'root' user account
AWS CIS 1.7Eliminate use of the root user for administrative and daily tasks
AWS CIS 1.8Ensure IAM password policy requires minimum length of 14 or greater
AWS CIS 1.9Ensure IAM password policy prevents password reuse
AWS CIS 1.10Ensure multi-factor authentication (MFA) is enabled for all IAM users that have a console password
AWS CIS 1.11Do not setup access keys during initial user setup for all IAM users that have a console password
AWS CIS 1.12Ensure credentials unused for 90 days or greater are disabled
AWS CIS 1.13Ensure there is only one active access key available for any single IAM user
AWS CIS 1.14Ensure access keys are rotated every 90 days or less
AWS CIS 1.15Ensure IAM Users Receive Permissions Only Through Groups
AWS CIS 1.16Ensure IAM policies that allow full ":" administrative privileges are not attached
AWS CIS 1.17Ensure a support role has been created to manage incidents with AWS Support
AWS CIS 1.18Ensure IAM instance roles are used for AWS resource access from instances
AWS CIS 1.19Ensure that all the expired SSL/TLS certificates stored in AWS IAM are removed
AWS CIS 1.20Ensure that S3 Buckets are configured with 'Block public access (bucket settings)'
AWS CIS 1.21Ensure that IAM Access analyzer is enabled
AWS CIS 1.22Ensure IAM users are managed centrally via identity federation or AWS Organizations for multi-account environments
AWS CIS 2.1.1Ensure all S3 buckets employ encryption-at-rest
AWS CIS 2.1.2Ensure S3 Bucket Policy allows HTTPS requests
AWS CIS 2.2.1Ensure EBS volume encryption is enabled
AWS CIS 3.1Ensure CloudTrail is enabled in all regions
AWS CIS 3.2Ensure CloudTrail log file validation is enabled
AWS CIS 3.3Ensure the S3 bucket used to store CloudTrail logs is not publicly accessible
AWS CIS 3.4Ensure CloudTrail trails are integrated with CloudWatch Logs
AWS CIS 3.5Ensure AWS Config is enabled in all regions
AWS CIS 3.6Ensure S3 bucket access logging is enabled on the CloudTrail S3 bucket
AWS CIS 3.7Ensure CloudTrail logs are encrypted at rest using KMS CMKs
AWS CIS 3.8Ensure rotation for customer created CMKs is enabled
AWS CIS 3.9Ensure VPC flow logging is enabled in all VPCs
AWS CIS 3.10Ensure that Object-level logging for write events is enabled for S3 bucket
AWS CIS 3.11Ensure that Object-level logging for read events is enabled for S3 bucket
AWS CIS 4.1Ensure a log metric filter and alarm exist for unauthorized API calls
AWS CIS 4.2Ensure a log metric filter and alarm exist for Management Console sign-in without MFA
AWS CIS 4.3Ensure a log metric filter and alarm exist for usage of 'root' account
AWS CIS 4.4Ensure a log metric filter and alarm exist for IAM policy changes
AWS CIS 4.5Ensure a log metric filter and alarm exist for CloudTrail configuration changes
AWS CIS 4.6Ensure a log metric filter and alarm exist for AWS Management Console authentication failures
AWS CIS 4.7Ensure a log metric filter and alarm exist for disabling or scheduled deletion of customer created CMKs
AWS CIS 4.8Ensure a log metric filter and alarm exist for S3 bucket policy changes
AWS CIS 4.9Ensure a log metric filter and alarm exist for AWS Config configuration changes
AWS CIS 4.10Ensure a log metric filter and alarm exist for security group changes
AWS CIS 4.11Ensure a log metric filter and alarm exist for changes to Network Access Control Lists (NACL)
AWS CIS 4.12Ensure a log metric filter and alarm exist for changes to network gateways
AWS CIS 4.13Ensure a log metric filter and alarm exist for route table changes
AWS CIS 4.14Ensure a log metric filter and alarm exist for VPC changes
AWS CIS 4.15Ensure a log metric filter and alarm exists for AWS Organizations changes
AWS CIS 5.1Ensure no Network ACLs allow ingress from 0.0.0.0/0 to remote server administration ports
AWS CIS 5.2Ensure no security groups allow ingress from 0.0.0.0/0 to remote server administration ports
AWS CIS 5.3Ensure the default security group of every VPC restricts all traffic
AWS CIS 5.4Ensure routing tables for VPC peering are "least access"
0.5.1-alpha.1

12 months ago

0.5.1-alpha.2

12 months ago

0.5.0

1 year ago

0.4.1-alpha.1

1 year ago

0.3.0

2 years ago

0.2.1

2 years ago

0.2.0

2 years ago

0.4.0

2 years ago

0.3.1

2 years ago

0.2.2

2 years ago

0.1.0

2 years ago