Cloud Defense Logo

Products

Solutions

Company

Book A Live Demo

Ensure VPC Flow Logs are Enabled

This rule checks if VPC flow logs are enabled to monitor network traffic within the Virtual Private Cloud.

RuleVPC flow logs should be enabled
FrameworkNIST 800-53 Revision 5
Severity
High

Rule Description:

The rule requires enabling VPC flow logs for compliance with the NIST 800-53 Revision 5 security standard. VPC flow logs capture information about the IP traffic in your virtual private cloud (VPC), providing insights into network communications and aiding in security analysis and troubleshooting.

Troubleshooting Steps:

If VPC flow logs are not enabled, follow these steps to troubleshoot and enable them:

  1. 1.

    Verify AWS CloudTrail logging:

    • Confirm that AWS CloudTrail logging is enabled in your AWS account.
    • To enable CloudTrail, go to the AWS Management Console, navigate to the CloudTrail service, and follow the instructions to enable it.
  2. 2.

    Check IAM permissions:

    • Ensure that you have sufficient IAM permissions to enable VPC flow logs.
    • You need the necessary permissions to modify VPC flow logs settings and create associated resources.
    • If you don't have the required permissions, contact your AWS account administrator.
  3. 3.

    Verify VPC configuration:

    • Check if your VPC has the required configurations to enable flow logs.
    • Ensure that your VPC has an associated flow log resource.
    • If there is no flow log resource associated with the VPC, follow the remediation steps mentioned below.
  4. 4.

    Review flow log configurations:

    • If VPC flow logs are already enabled but not complying with NIST 800-53 Revision 5, review the configurations to ensure they meet compliance requirements.
    • Check if you are capturing the required information such as source/destination IP addresses, ports, protocols, etc.
  5. 5.

    Apply remediation steps:

    • If VPC flow logs are not currently enabled or not compliant, perform the remediation steps mentioned below.

Remediation Steps:

To enable VPC flow logs for NIST 800-53 Revision 5 compliance, follow the steps below:

  1. 1.

    Open the AWS Management Console:

    • Sign in to the AWS Management Console using your AWS account credentials.
  2. 2.

    Navigate to Amazon VPC service:

    • In the AWS Management Console, search and select the "VPC" service or navigate to it from the services menu.
  3. 3.

    Select the desired VPC:

    • From the VPC dashboard, select the specific VPC for which you want to enable flow logs.
  4. 4.

    Click on "Flow Logs":

    • In the "Details" tab for the selected VPC, click on the "Flow Logs" option.
  5. 5.

    Click "Create Flow Log":

    • In the Flow Logs page, click on the "Create Flow Log" button.
  6. 6.

    Configure the flow log settings:

    • Provide a unique name for the flow log in the "Flow Log Name" field.
    • Select the target where the flow logs should be delivered (e.g., an Amazon S3 bucket or CloudWatch Logs group).
    • Choose whether to capture all traffic or specific subnets, network interfaces, or VPC endpoints.
    • Specify the IAM role that grants necessary permissions for delivering the flow logs.
    • Optionally, choose to enable or disable "Accept traffic from peered VPCs."
    • Ensure the "Enabled" checkbox is selected.
  7. 7.

    Click "Create":

    • Once you have configured the desired settings, click on the "Create" button.
  8. 8.

    Verify flow log creation:

    • Confirm that the flow log has been created and appears in the list of flow logs for the selected VPC.
  9. 9.

    Validate flow logs:

    • Review the flow logs to ensure they are functioning correctly.
    • Confirm that the flow logs capture the required information specified in the NIST 800-53 guidelines.

Conclusion:

By following the above steps, you can enable VPC flow logs for NIST 800-53 Revision 5 compliance. It is essential to regularly review and validate the flow logs to ensure ongoing compliance and maximize the security of your VPC.

Is your System Free of Underlying Vulnerabilities?
Find Out Now