google.iam.admin.v1.UndeleteServiceAccount

​

Event Information

• The google.iam.admin.v1.UndeleteServiceAccount event in GCP for GCPIAM refers to the action of restoring a deleted service account in Google Cloud Identity and Access Management (IAM).
• This event indicates that a previously deleted service account has been successfully recovered and is now available for use again.
• It is important to note that this event is specific to GCP’s IAM service and is triggered when a service account is undeleted using the IAM API.

​

Examples

1. Unauthorized access: If the google.iam.admin.v1.UndeleteServiceAccount permission is misconfigured or granted to unauthorized users or roles, it can lead to unauthorized access to deleted service accounts. This can potentially expose sensitive data and resources to malicious actors.

2. Privilege escalation: If an attacker gains access to the google.iam.admin.v1.UndeleteServiceAccount permission, they can potentially restore deleted service accounts and gain elevated privileges within the GCP environment. This can allow them to perform unauthorized actions, access sensitive information, or modify critical resources.

3. Data breaches: If a deleted service account is restored using the google.iam.admin.v1.UndeleteServiceAccount permission without proper validation or monitoring, it can result in data breaches. The restored service account may have access to sensitive data or resources, which can be exploited by attackers to exfiltrate or manipulate data. It is crucial to ensure that only authorized personnel have the necessary permissions to restore deleted service accounts.

​

Remediation

​

Using Console

1. Example 1: Ensure that all users have a strong password policy in GCP IAM.

• Step 1: Log in to the GCP Console.
• Step 2: Navigate to the IAM & Admin section.
• Step 3: Click on “IAM” to view the list of users.
• Step 4: Select the user for whom you want to enforce a strong password policy.
• Step 5: Click on the “Edit” button next to the user’s name.
• Step 6: Scroll down to the “Password” section and enable the option for a strong password policy.
• Step 7: Save the changes.

2. Example 2: Ensure that multi-factor authentication (MFA) is enabled for all users in GCP IAM.

• Step 1: Log in to the GCP Console.
• Step 2: Navigate to the IAM & Admin section.
• Step 3: Click on “IAM” to view the list of users.
• Step 4: Select the user for whom you want to enable MFA.
• Step 5: Click on the “Edit” button next to the user’s name.
• Step 6: Scroll down to the “Multi-factor authentication” section and enable the option for MFA.
• Step 7: Save the changes.

3. Example 3: Ensure that unused service accounts are disabled in GCP IAM.

• Step 1: Log in to the GCP Console.
• Step 2: Navigate to the IAM & Admin section.
• Step 3: Click on “Service accounts” to view the list of service accounts.
• Step 4: Select the service account that you want to disable.
• Step 5: Click on the “Disable” button next to the service account’s name.
• Step 6: Confirm the action to disable the service account.
• Step 7: Repeat steps 4-6 for any other unused service accounts that need to be disabled.

​

Using CLI

To remediate the issues related to GCP GCPIAM using GCP CLI, you can follow these steps:

1. Enable multi-factor authentication (MFA) for IAM users:

   • Use the gcloud command to enable MFA for a specific user:

     gcloud auth login
     gcloud auth application-default login
     

   • Follow the prompts to complete the MFA setup.

2. Implement least privilege access:

   • Use the gcloud command to create a custom IAM role with the necessary permissions:

     gcloud iam roles create <role_name> --project=<project_id> --title="<role_title>" --description="<role_description>" --permissions=<comma_separated_permissions>
     

   • Assign the custom IAM role to the appropriate users or service accounts:

     gcloud projects add-iam-policy-binding <project_id> --member=<member> --role=<role_name>
     

3. Regularly review and rotate service account keys:

   • Use the gcloud command to list all service accounts in a project:

     gcloud iam service-accounts list --project=<project_id>
     

   • Use the gcloud command to create a new key for a service account:

     gcloud iam service-accounts keys create <output_file> --iam-account=<service_account_email> --project=<project_id>
     

   • Remove the old keys from the service account:

     gcloud iam service-accounts keys delete <key_id> --iam-account=<service_account_email> --project=<project_id>
     

Please note that the actual commands may vary depending on your specific requirements and configurations. Make sure to replace the placeholders (<role_name>, <project_id>, <member>, <output_file>, <service_account_email>, <key_id>) with the appropriate values.

​

Using Python

To remediate GCP GCPIAM issues using Python, you can utilize the Google Cloud Identity and Access Management (GCPIAM) API. Here are three examples of how you can use Python to remediate GCPIAM issues:

1. Granting a User Role:

from google.cloud import iam

def grant_user_role(project_id, user_email, role_name):
    client = iam.IAMClient()
    policy = client.get_policy(request={"resource": f"projects/{project_id}"})
    
    binding = next((b for b in policy.bindings if b.role == role_name), None)
    if binding:
        binding.members.append(f"user:{user_email}")
    else:
        binding = iam.Policy.Types.Binding(
            role=role_name,
            members=[f"user:{user_email}"]
        )
        policy.bindings.append(binding)
    
    client.set_policy(request={"resource": f"projects/{project_id}", "policy": policy})

2. Revoking a User Role:

from google.cloud import iam

def revoke_user_role(project_id, user_email, role_name):
    client = iam.IAMClient()
    policy = client.get_policy(request={"resource": f"projects/{project_id}"})
    
    binding = next((b for b in policy.bindings if b.role == role_name), None)
    if binding:
        binding.members = [m for m in binding.members if m != f"user:{user_email}"]
    
    client.set_policy(request={"resource": f"projects/{project_id}", "policy": policy})

3. Creating a Custom Role:

from google.cloud import iam

def create_custom_role(project_id, role_id, title, description, permissions):
    client = iam.IAMClient()
    
    role = iam.Role(
        title=title,
        description=description,
        included_permissions=permissions
    )
    
    client.create_role(request={"parent": f"projects/{project_id}", "role_id": role_id, "role": role})

Please note that you need to have the necessary permissions and authentication set up to execute these scripts successfully.