The GCP Cloud NAT Codeless Connector for Microsoft Sentinel enables seamless integration of GCP Cloud NAT logs with Microsoft Sentinel without the need for custom code. Developed as part of the Codeless Connector Platform(CCP), this connector simplifies the process of collecting and ingesting Cloud NAT logs from Google Cloud Platform into Microsoft Sentinel.
The below mentioned resources are required to connect GCP with Sentinel.
- Project ID
- Project Number
- GCP Subscription Name
- Workload Identity Pool ID
- Service Account
- Workload Identity Provider ID
To generate the above resources, you must execute the following terraform scripts.
- Log Setup File
- Authentication setup file
To access the terraform script for Log Setup Click here.
-
Launch the cloud shell in Google Cloud Console.
-
Execute the below mentioned commands.
-
create a directory
mkdir <dir_name>
-
Navigate to the directory
cd <dir_name>
-
Copy the github raw link of the Terraform script and get the content of the file into a shell using the following command:
wget <raw link of the file> -O <filename.tf>
-
Initializes your terraform working directory, downloads provider plugins, and configures the backend for state storage.
terraform init
-
Creates an execution plan to show what actions terraform will take to achieve the desired state of your infrastructure.
terraform plan
Once you execute this command it will ask to "Enter your project ID". Please enter your GCP Project ID.
-
Executes the actions proposed in the Terraform plan to create, update, or destroy resources in your infrastructure.
terraform apply
Once you execute this command it will again ask to "Enter your project ID". Please enter your GCP Project ID one more time.
-
After successfully executing the Log Setup file,
topic name
,subscription name
is generated in the GCP Project. Save those details for future reference.
- If the Authentication setup file is previously executed in the project while configuring any other GCP data connectors, there is no need to execute the Authentication setup file again. You can use the existing
Workload Identity Pool ID
andWorkload Identity Provider ID
for authentication purpose. - If these fields are not generated previously, execute the Authentication Setup file with the same commands mentioned above.
- To access the Authentication Setup file Click Here.
- To Execute the Authentication Setup file Click Here.
- After executing the authentication setup file,
Workload Identity Pool ID
andWorkload Identity Provider ID
are generated in the project.