Cloud Defense Logo

Products

Solutions

Company

Book A Live Demo

Rule: Lambda Functions in a VPC

Guideline stating that Lambda functions must be configured within a VPC for security purposes.

RuleLambda functions should be in a VPC
FrameworkHIPAA
Severity
Low

HIPAA Compliance Rule: Lambda Functions in VPC

Description:

In order to maintain compliance with the Health Insurance Portability and Accountability Act (HIPAA), Lambda functions should be deployed within a Virtual Private Cloud (VPC) to ensure data privacy and security. This rule ensures that Lambda functions, which may process or store protected health information (PHI), are isolated within a secure network environment, meeting the confidentiality and integrity requirements of HIPAA.

Troubleshooting Steps:

  1. 1.
    Ensure that the Lambda function is not already deployed within a default VPC. Default VPCs are not suitable for HIPAA compliance as they may have public access and lack the required network isolation.
  2. 2.
    Verify that the Lambda function is accessing or processing PHI. If it doesn't handle PHI, then moving it to a VPC may not be necessary for compliance.

Necessary Codes:

No specific code is required for this rule; however, you will need to modify the Lambda function's configuration to include it within a VPC.

Step-by-Step Guide for Remediation:

Follow these steps to ensure compliance by configuring your Lambda function to run within a VPC:

  1. 1.
    Open the AWS Management Console and navigate to the Lambda service page.
  2. 2.
    Identify the Lambda function that needs to be deployed within a VPC.
  3. 3.
    Click on the function's name to access its configuration details.
  4. 4.
    Scroll down to the "Network" section and click on the "Edit" button.
  5. 5.
    Choose the VPC where your Lambda function should reside from the available list of VPCs.
  6. 6.
    Select the desired subnet(s) within the chosen VPC to associate with the Lambda function.
  7. 7.
    If your Lambda function needs internet access, ensure that it is associated with a subnet having a NAT Gateway attached.
  8. 8.
    Optionally, specify the security groups required for your Lambda function's network access. Ensure that these security groups align with the required HIPAA-compliant networking principles.
  9. 9.
    Save the changes by clicking on the "Save" button.

Following these steps will associate your Lambda function with one or more subnets within a VPC, ensuring compliance with HIPAA regulations.

Note: Make sure you thoroughly test your Lambda function within the VPC to ensure proper functionality, as network restrictions might affect its execution.

By adhering to the Lambda function in VPC rule for HIPAA compliance, you guarantee that PHI is handled securely and maintain the data integrity mandated by HIPAA.

Is your System Free of Underlying Vulnerabilities?
Find Out Now