Multiple Cloud Functions Should Not Use Same IAM Role
More Info:
Multiple Cloud Functions should not have same IAM roles.Risk Level
MediumAddress
SecurityCompliance Standards
CBPTriage and Remediation
Remediation
Using Console
Using Console
To remediate the misconfiguration “Multiple Cloud Functions Should Not Use Same IAM Role” for GCP using the GCP console, follow these steps:
- Login to the GCP console: https://console.cloud.google.com/
- Navigate to the Cloud Functions page by clicking on the hamburger menu on the top left corner and selecting “Cloud Functions” under the “Compute” section.
- Select the function that is using the same IAM role as another function.
- Click on the “Edit” button on the top of the Cloud Function page.
- Scroll down to the “Cloud Function Details” section and click on the “Show Advanced Settings” button.
- Under the “Cloud Function IAM” section, click on the “Change” button next to the “Service account” field.
- In the “Select a service account” dialog box, select “Create a new service account” and give it a name.
- Click on the “Create” button and wait for the service account to be created.
- Select the newly created service account from the drop-down list and click on the “Save” button at the bottom of the page.
- Repeat the above steps for all the other functions that are using the same IAM role.
Using CLI
Using CLI
To remediate the misconfiguration “Multiple Cloud Functions Should Not Use Same IAM Role” for GCP using GCP CLI, follow the below steps:Replace [ROLE_NAME] with the name of the new IAM role, [PROJECT_ID] with the ID of the project, and [ROLE_DEFINITION_FILE_PATH] with the path to the JSON file that defines the new role.Replace [FUNCTION_NAME] with the name of the Cloud Function, [MEMBER] with the email address or service account of the member that you want to grant access to, and [ROLE_NAME] with the name of the new IAM role.Replace [FUNCTION_NAME] with the name of the Cloud Function, [MEMBER] with the email address or service account of the member that you want to revoke access from, and [OLD_ROLE_NAME] with the name of the old IAM role.Repeat these steps for all the Cloud Functions that are sharing the same IAM role.
- Open the Google Cloud Console and navigate to the Cloud Functions page.
- Identify the Cloud Functions that are using the same IAM role.
- Create a new IAM role for each Cloud Function that is currently sharing a role.
- Assign the newly created IAM role to the respective Cloud Function.
- Remove the old IAM role from the Cloud Function.
- Open the GCP CLI and run the command below to list all the Cloud Functions:
- Identify the Cloud Functions that are using the same IAM role.
- Create a new IAM role for each Cloud Function that is currently sharing a role using the command below:
- Assign the newly created IAM role to the respective Cloud Function using the command below:
- Remove the old IAM role from the Cloud Function using the command below:
Using Python
Using Python
To remediate the misconfiguration “Multiple Cloud Functions Should Not Use Same IAM Role” for GCP using python, you can follow the below steps:Note: You will need to authenticate with GCP before running the above code. You can refer to the GCP documentation for more information on how to authenticate with GCP using python.
- Create a new IAM role for each cloud function that needs to be deployed.
- Assign the appropriate permissions to the IAM role based on the requirements of the cloud function.
- Update the cloud function deployment script to include the newly created IAM role for each function.
- Update the cloud function configuration to use the newly created IAM role for each function.