INTEGRATING YOUR ASSETS ON CYBERVERGENT
Amazon Web Services (AWS)
Create a user, with the SecurityAudit policy.
- Log into your AWS account as an admin or with permission to create IAM resources.
- Navigate to the IAM console.
- Click on Users
- Create a new user (Add user)
- Enter the username
- Set the access type to "Programmatic access", click Next.
- Select "Attach existing policies directly" and select the SecurityAudit policy.
- Click "Create policy" to create a supplemental policy (some permissions are not included in SecurityAudit).
- Click the "JSON" tab and paste the following permission set.
- Click "Review policy."
- Provide a <name> and click "Create policy."
- Return to the "Create user" page and attach the newly-created policy. Click "Next: tags."
- Set tags as needed and then click on "Create user".
- Make sure you safely store the Access key ID and Secret access key.
- Paste them into the corresponding input on the Cybervergent Integration Page.
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"ses:DescribeActiveReceiptRuleSet",
"athena:GetWorkGroup",
"logs:DescribeLogGroups",
"logs:DescribeMetricFilters",
"elastictranscoder:ListPipelines",
"elasticfilesystem:DescribeFileSystems",
"servicequotas:ListServiceQuotas"
],
"Resource": "*"
}
]
}
Microsoft Azure
- Log into your Azure Portal and navigate to the Azure Active Directory service.
- Select App registrations and then click on New registration.
- Enter <name> and/or a descriptive name in the Name field, take note of it, it will be used again in step 3.
- Leave the "Supported account types" default: "Accounts in this organizational directory only (YOURDIRECTORYNAME)".
- Click on Register.
- Copy the Application ID and Paste it below.
- Copy the Directory ID and Paste it below.
- Click on Certificates & secrets.
- Under Client secrets, click on New client secret.
- Enter a Description and select Expires "In 1 year".
- Click on Add.
- The Client secret value appears only once, make sure you store it safely.
- Navigate to Subscriptions.
- Click on the relevant Subscription ID, copy and paste the ID below.
- Click on "Access Control (IAM)".
- Go to the Role assignments tab.
- Click on "Add", then "Add role assignment".
- In the "Role" drop-down, select "Security Reader".
- Leave the "Assign access to" default value.
- In the "Select" drop-down, type the name of the app registration you created and select it.
- Click "Save".
- Repeat the process for the role "Log Analytics Reader"
- Paste them into the corresponding input on the Cybervergent Integration Page.
Okay, I got that
Google Cloud Platform (GCP)
- Log into your Google Cloud console and "Activate" your Cloud Shell.
- Create a new file called aqua-security-audit-role.yaml. You can use:
nano cyv-security-audit-role.yaml. - Copy and paste the following yaml code in the file on your Cloud Shell, press Ctrl + X and type "Y" to save the file. Note! Exclude all rows starting with 'resourcemanager' if you do not use Organization.
Plain Text
Plain Textname: roles/CyvDSPMSecurityAudit
title: CYV DSPM Security Audit
includedPermissions:
- cloudasset.assets.listResource
- 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
- deploymentmanager.deployments.list
- dataproc.clusters.list
- artifactregistry.repositories.list
- composer.environments.list
stage: GA
- Run the following command to create the role, use your Organization Id to create the Role at the Org Level:
gcloud iam roles create CyvDSPMSecurityAudit --organization=YOUR_ORGANIZATION_ID --file=cyv-security-audit-role.yaml- You can use
--project=YOUR_PROJECT_IDinstead of--organization=<YOUR_ORGANIZATION_ID>
- You can use
Create Service Account
- Log into your Google Cloud console and navigate to IAM Admin > Service Accounts.
- Click on "Create Service Account".
- Enter <name> in the "Service account name", then enter <description> in the description.
- Click on Continue.
- Select the role: Custom > CYV DSPM Security Audit.
- Click on Continue.
- Click on "Create Key".
- Leave the default JSON selected.
- Click on "Create".
- The key will be downloaded to your machine.
- Open the JSON key file, in a text editor and copy the Project Id, Client Email and Private Key values into the corresponding input on the Cybervergent Integration Page.
GitHub
You need a GitHub personal access token for an organization owner with read-only access. You can read more about the permission model below. Follow these steps:
- Log into your GitHub organization account as an owner
- Create a new machine (generic) user (depending on your organization's configuration, you may need to impersonate the user to get access to its settings page). NOTE: You can optionally use an existing organization owner for this token, but we strongly recommend creating a new user.
- Ensure the user is added as an owner of the Git organization.
- Log into GitHub as this user.
- Navigate to "Settings" > "Developer Settings" > "Personal Access Tokens"
- Click "Generate new token" and give it a description.
- Check the following permissions:
- repo
- repo:status
- repo_deployment
- public_repo
- repo:invite
- admin:org
- write:org
- read:org
- admin:public_key
- write:public_key
- read:public_key
- admin:repo_hook
- write:repo_hook
- read:repo_hook
- admin:org_hook
- gist
- notifications
- user
- read:user
- user:email
- user:follow
- delete_repo
- write:discussion
- read:discussion
- admin:business
- manage_billing:business
- read:business
- admin:gpg_key
- write:gpg_key
- read:gpg_key
- Save the permissions to obtain a token. Copy this token into the corresponding input on the Cybervergent Integration Page.