forked from aquasecurity/cloudsploit
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merging SAAS 05-25 (aquasecurity#729)
* merging saas * fixes Co-authored-by: Gio Rodriguez <[email protected]>
- Loading branch information
1 parent
5786960
commit 66c25ad
Showing
5 changed files
with
63 additions
and
12 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,19 +1,70 @@ | ||
# CloudSploit For Google Cloud Platform (GCP) | ||
|
||
## Cloud Provider Configuration | ||
## Create Security Audit Role | ||
|
||
1. Log into your Google Cloud console and "Activate" your Cloud Shell. | ||
1. Create a new file called aqua-security-audit-role.yaml. You can use: ``nano aqua-security-audit-role.yaml``. | ||
1. Copy and paste the following yaml code in the file on your Cloud Shell, press Ctrl + X and type "Y" to save the file. | ||
``` | ||
name: roles/AquaCSPMSecurityAudit | ||
title: Aqua CSPM Security Audit | ||
- includedPermissions: | ||
- cloudkms.cryptoKeys.list | ||
- cloudkms.keyRings.list | ||
- cloudsql.instances.list | ||
- cloudsql.users.list | ||
- compute.autoscalers.list | ||
- compute.backendServices.list | ||
- compute.disks.list | ||
- compute.firewalls.list | ||
- compute.healthChecks.list | ||
- compute.instanceGroups.list | ||
- compute.instances.getIamPolicy | ||
- compute.instances.list | ||
- compute.networks.list | ||
- compute.projects.get | ||
- compute.securityPolicies.list | ||
- compute.subnetworks.list | ||
- compute.targetHttpProxies.list | ||
- container.clusters.list | ||
- dns.managedZones.list | ||
- iam.serviceAccountKeys.list | ||
- iam.serviceAccounts.list | ||
- logging.logMetrics.list | ||
- logging.sinks.list | ||
- monitoring.alertPolicies.list | ||
- resourcemanager.folders.get | ||
- resourcemanager.folders.getIamPolicy | ||
- resourcemanager.folders.list | ||
- resourcemanager.hierarchyNodes.listTagBindings | ||
- resourcemanager.organizations.get | ||
- resourcemanager.organizations.getIamPolicy | ||
- resourcemanager.projects.get | ||
- resourcemanager.projects.getIamPolicy | ||
- resourcemanager.projects.list | ||
- resourcemanager.resourceTagBindings.list | ||
- resourcemanager.tagKeys.get | ||
- resourcemanager.tagKeys.getIamPolicy | ||
- resourcemanager.tagKeys.list | ||
- resourcemanager.tagValues.get | ||
- resourcemanager.tagValues.getIamPolicy | ||
- resourcemanager.tagValues.list | ||
- storage.buckets.getIamPolicy | ||
- storage.buckets.list | ||
stage: GA | ||
``` | ||
4. Run the following command to create the role, use your Organization Id to create the Role at the Org Level: ``gcloud iam roles create AquaCSPMSecurityAudit --organization=YOUR_ORGANIZATION_ID --file=aqua-security-audit-role.yaml`` | ||
|
||
## Create Service Account | ||
|
||
1. Log into your Google Cloud console and navigate to IAM Admin > Service Accounts. | ||
1. Click on "Create Service Account". | ||
1. Enter "CloudSploit" in the "Service account name", then enter "CloudSploit API Access" in the description. | ||
1. Click on Continue. | ||
1. Select the role: Project > Viewer. | ||
1. Select the role: Custom > Aqua CSPM Security Audit. | ||
1. Click on Continue. | ||
1. Click on "Create Key". | ||
1. Leave the default JSON selected. | ||
1. Click on "Create". | ||
1. The key will be downloaded to your machine. | ||
1. Open the JSON key file, in a text editor and copy the Project Id, Client Email and Private Key values into the `index.js` file or move the JSON key file to a safe location; you can reference it in your `config.js` file later. | ||
1. Enter the APIs & Services category. | ||
1. Select Enable APIS & SERVICES at the top of the page | ||
1. Search for DNS, then Select the option that appears and Enable it. | ||
1. Enable all the APIs used to run scans, they are as follows: Stackdriver Monitoring, Stackdriver Logging, Compute, Cloud Key Management, Cloud SQL Admin, Kubernetes, Service Management, and Service Networking. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -93,4 +93,4 @@ module.exports = { | |
callback(null, results, source); | ||
}); | ||
} | ||
}; | ||
}; |