# 1.2 Scans
Source: https://docs.zero-x.cloud/zerox/connectors/1.2-Scans
Home > Connectors > Scans
### Step 4: Clicked on Integration Now, You can see your scanned here.
### List of AWS Scanner
1.CSPM
2.Container Image
3.Inventory sync
4.Compliance
5.CIEM
6.Attack path
### List of AWS Cross Account Scanner
1.CSPM
2.Container Image
3.Inventory sync
4.Compliance
5.CIEM
6.Attack path
### List of GCP Scanner
1.CSPM
2.Inventory sync
3.Compliance
4.CIEM
### List of Azure Scanner
1.CSPM
2.Inventory sync
3.Compliance
4.CIEM
### List of AZURE EKS Scanner
1.KSPM
2.K8s Inventory
3.K8s Secrets
4.K8s Vulnerability
### List of Github Account Scanner
1.SAST
2.Secrets
3.Vulnerability
4.Iac
5.Dependencies and SBOM
6.Inventory sync
7.Malware
8.Compliance
### List of Gitlab Account Scanner
1.SAST
2.Secrets
3.Vulnerability
4.Iac
5.Dependencies and SBOM
6.Inventory sync
7.Malware
8.Compliance
### List of Bitbucket Account Scanner
1.SAST
2.Secrets
3.Vulnerability
4.Iac
5.Dependencies and SBOM
6.Inventory sync
7.Malware
8.Compliance
### List of AzureDevops Account Scanner
1.SAST
2.Secrets
3.Vulnerability
4.Iac
5.Dependencies and SBOM
6.Inventory sync
7.Malware
### List of O365 Account Scanner
1.CIEM
2.Compliance
3.Inventory sync
### List of UTHO Account Scanner
1.Inventory sync
### List of Atera Account Scanner
1.Inventory sync
### List of OCI Account Scanner
1.CIEM
2.Compliance
3.Inventory sync
### List of E2E Account Scanner
1.CSPM
2.Inventory sync
### List of Intune Account Scanner
1.Inventory sync
### List of SonarQube Account Scanner
1.Inventory sync
### Note : Once the scan is completed, you can view all the findings and inventory, along with their synchronization status.
# 1.3.Finding
Source: https://docs.zero-x.cloud/zerox/connectors/1.3.Finding
### Finding Overview Steps
**Step 1:** You can see Finding option left menu bar and click Inventory.
**Step 2:** View all your Findings data resources.
**Step 3:** Select a data source from the filter, such as **AWS** or **GCP**, to view the corresponding Findings.
**Step 4:** Click on any finding item to view the **Graph, Similar Affected Resources, Activity History and Remediation**.
## Security Findings Graph
The **Security Findings Graph** provides a visual representation of the relationships between cloud resources, CSPM findings, and compliance findings. It enables security analysts to quickly understand which findings are associated with a resource and how they are grouped.
### Graph Components
#### Resource Node
The graph begins with the selected cloud resource. In this example, an **Amazon S3 Bucket** is displayed.
The resource node contains:
* Resource name
* Resource type
* Cloud provider icon
* Region
* Severity counters
* Number of connected findings
Selecting the resource highlights all associated security findings.
***
#### CSPM Findings Cluster
The **CSPM Findings** cluster groups all Cloud Security Posture Management findings related to the selected resource.
Each card represents an individual security finding, such as:
* S3 Access Block should block publick ACL
* S3 Bucket Logging should block public policy
* S3 data should be version
* S3 Encryption should ignore public ACL
The cluster can be expanded or collapsed using the **Collapse** button in the upper-right corner.
Grouping findings reduces visual clutter while preserving the relationship between the resource and its findings.
***
#### Compliance Findings
Compliance findings are displayed as a separate expandable cluster beneath the resource.
The cluster displays:
* Total number of compliance findings
* Expand option to view individual findings
Selecting the compliance cluster reveals all compliance-related issues associated with the selected resource.
***
### Relationship Lines
Purple connector lines represent relationships between:
* Cloud resources
* CSPM findings
* Compliance findings
These relationships help visualize:
* Which findings affect a resource
* Resource-to-finding dependencies
* Security impact paths
***
## Interacting with the Graph
### Expand or Collapse Finding Groups
Use the **Collapse** button in the CSPM Findings group to hide or show individual findings.
Benefits include:
* Reduced graph complexity
* Improved navigation
* Easier visualization of large environments
***
### View Individual Findings
Each finding card displays:
* Finding title
* Finding category
* Associated service
Selecting a finding opens its detailed information, including severity, description, and remediation guidance.
***
### Review Compliance Findings
Click the **Compliance Findings** cluster to expand and display all compliance findings related to the selected resource.
This helps determine whether the resource violates organizational or regulatory compliance requirements.
***
## Example Workflow
1. Open the **Graph** tab.
2. Select a cloud resource.
3. Review connected CSPM findings.
4. Expand the CSPM Findings cluster if additional details are required.
5. Expand the Compliance Findings cluster to review compliance issues.
6. Select an individual finding to view detailed information and remediation guidance.
***
# 1.4 Inventory
Source: https://docs.zero-x.cloud/zerox/connectors/1.4-Inventory
### Inventory Overview Steps
**Step 1:** You can see inventory option left menu bar click on Explore and click Inventory
**Step 2:** View all your inventory data resources.
**Step 3:** Select a data source from the filter, such as **AWS** or **GCP**, to view the corresponding inventory.
**Step 4:** Click the **AI Inventory** filter to view AI-related inventory.
**Step 5:** Click on any inventory item to view the **Resource Graph, Resource Information, Findings, and AI Fixes**.
# 1.5 CloudAutofix
Source: https://docs.zero-x.cloud/zerox/connectors/1.5-CloudAutofix
title: Cloud Autofix
description: Identify, review, simulate, execute, and monitor automated remediation actions for cloud security findings.
***
## Overview
**Cloud Autofix** helps users identify and remediate supported cloud security findings directly from Zero-X Cloud.
Instead of manually opening the cloud provider console and changing the configuration, Cloud Autofix provides a guided workflow to review the finding, simulate the proposed change, execute the remediation, and monitor the result.
The typical workflow is:
# How to Use Cloud Autofix
## Step 1: Open Cloud Autofix
1. Sign in to **Zero-X Cloud**.
2. Open the **Cloud Autofix** module.
3. The **Fix Available Findings** tab is displayed.
4. Review the available findings.
***
## Step 2: Locate the Finding
Use the available filters to find the security issue you want to remediate.
Available filters may include:
* Filter by Date
* Categories
* Accounts
* Cloud Resource
* Severity
* Resource Types
* Compliance
* Region
You can also use:
* **Search** to find a specific finding or resource.
* **Columns** to customize the displayed columns.
* **Saved Views** to save frequently used filter configurations.
* **Grouping** to organize findings.
***
## Step 3: Review the Finding
Before executing any remediation:
1. Review the finding description.
2. Verify the affected resource.
3. Check the cloud provider.
4. Check the resource type.
5. Review the risk score.
6. Review the severity.
7. Confirm that the finding is appropriate for remediation.
***
# Step 4: Open AutoFix
1. Locate the required finding.
2. Click **AutoFix**.
The **Remediate Finding** page opens.
The page provides information about the target resource and the remediation actions available for that finding.
***
# Remediate Finding
The Remediate Finding screen contains three main sections:
### Target Resource
This section identifies the resource that will be affected.
It can display:
* Resource ID or resource name
* Finding description
* Severity
* Cloud provider
* Resource type
**Details**
* Severity: High
* Cloud Provider: AWS
* Resource Type: EBS Volume
> **Always verify the target resource before executing a remediation.**
***
# Available Actions
Depending on the finding, Cloud Autofix may provide the following actions:
1. **Run Dry Run**
2. **Execute Remediation**
3. **Execute Rollback**
***
# Run Dry Run
## What is a Dry Run?
A **Dry Run** simulates the remediation without applying the change to the live cloud resource.
It allows you to review the expected action before making an actual change.
### Steps
1. Open the required finding.
2. Click **AutoFix**.
3. Review the **Remediate Finding** page.
4. Click **Run Dry Run**.
5. Wait for the simulation to complete.
6. Review the Dry Run result.
7. Verify that the proposed change is expected.
### Important
A successful Dry Run indicates that the remediation can be simulated successfully. It does **not** mean that the live resource has already been changed.
***
# Execute Remediation
## What is Execute Remediation?
**Execute Remediation** applies the supported security fix directly to the target cloud resource.
This action can make a live change.
### Before executing
Verify:
* Correct finding
* Correct target resource
* Correct cloud account
* Correct region
* Correct resource type
* Expected remediation action
* Dry Run result, where available
### Steps
1. Open the required finding.
2. Click **AutoFix**.
3. Review the target resource.
4. Run the **Dry Run** when available.
5. Review the Dry Run result.
6. Select **Execute Remediation**.
7. Review the confirmation information.
8. Confirm the remediation.
9. Wait for the execution result.
10. Review the execution logs.
After the remediation is successfully executed, Zero-X verifies the finding according to its scanning and remediation workflow.
> **Warning:** Execute Remediation can modify a live cloud resource. Make sure the proposed change is approved before execution.
***
# Execute Rollback
## What is Rollback?
**Execute Rollback** is used to reverse a supported infrastructure change created by a previous remediation.
Rollback availability depends on the remediation type.
### Steps
1. Open the relevant remediation workflow.
2. Select **Execute Rollback**.
3. Review the rollback information.
4. Confirm the rollback.
5. Wait for the rollback execution to complete.
6. Review the execution logs.
7. Verify the resource and finding status.
> **Note:** Not every remediation supports rollback.
***
# Remediation Execution Logs
The **Remediation Execution Logs** tab provides a history of remediation operations.
Use the logs to review:
* Remediation action
* Target resource
* Execution status
* Execution time
* Execution result
* Error information
* Rollback activity
* Previous remediation attempts
### Troubleshooting a Failed Remediation
If a remediation fails:
1. Open **Remediation Execution Logs**.
2. Locate the failed execution.
3. Review the error details.
4. Verify the cloud account connection.
5. Verify the required permissions.
6. Confirm that the resource still exists.
7. Run a Dry Run again, if available.
8. Retry the remediation after resolving the underlying issue.
***
# Finding Details
The **Details** option provides additional information about the finding and affected resource.
Review the details before executing a remediation, especially for:
* Critical findings
* Production resources
* Network-related findings
* Encryption findings
* Shared cloud resources
* Resources with dependencies
***
# Playbook
The **Playbook** option provides remediation guidance associated with the finding.
Use the Playbook to understand:
* Why the finding was generated
* What security configuration needs to be changed
* What remediation action is proposed
* What impact the change may have
***
### Remediation Process
1. Open **Cloud Autofix**.
2. Go to **Fix Available Findings**.
3. Locate the EBS encryption finding.
4. Click **AutoFix**.
5. Verify the target resource.
6. Click **Run Dry Run**.
7. Review the simulation result.
8. If the proposed change is acceptable, click **Execute Remediation**.
9. Confirm the action.
10. Monitor the execution.
11. Open **Remediation Execution Logs**.
12. Verify that the finding is resolved.
If the remediation needs to be reverted and rollback is supported:
1. Open the remediation workflow.
2. Click **Execute Rollback**.
3. Confirm the rollback.
4. Review the execution logs.
5. Verify the resource state.
***
# Finding Status After Remediation
After remediation, the finding may move through different states depending on the execution and verification process.
| Status | Description |
| - | - |
| **Failed** | The remediation could not be completed. |
| **Resolved** | The security issue has been verified as resolved. |
| **Auto-Resolved** | Zero-X detected that the underlying security issue is no longer present. |
***
## Dry Run Fails
Check the following:
1. Cloud account connectivity.
2. Required permissions.
3. Target resource availability.
4. Cloud region.
5. Remediation execution logs.
***
## Remediation Fails
Follow these steps:
1. Open **Remediation Execution Logs**.
2. Review the error message.
3. Verify cloud permissions.
4. Verify that the target resource still exists.
5. Check the cloud account connection.
6. Run the Dry Run again.
7. Retry the remediation after resolving the issue.
***
## Finding Is Still Visible After Remediation
A finding may remain visible until Zero-X verifies the updated cloud configuration.
Check:
* Remediation execution status.
* Finding details.
* Latest scan result.
* Remediation execution logs.
If the issue still exists after the next scan, investigate the resource configuration and remediation result.
***
### During Remediation
* Execute remediation only on the intended resource.
* Review the confirmation information.
* Monitor execution status.
* Keep track of important remediation operations.
### After Remediation
* Verify the remediation result.
* Review execution logs.
* Verify the finding status.
* Check the cloud resource configuration when necessary.
* Confirm the finding does not reappear after the next scan.
***
# Security Considerations
Cloud Autofix can make changes to connected cloud environments.
Before executing a remediation:
* Confirm the target resource.
* Understand the expected change.
* Review the Dry Run result.
* Verify the required cloud permissions.
* Follow your organization's change-management process.
* Use additional caution for production resources.
***
# Quick Reference
| Action | Purpose | Changes Live Resource |
| - | - | - |
| **AutoFix** | Opens the remediation workflow | No |
| **Run Dry Run** | Simulates the remediation | No |
| **Execute Remediation** | Applies the security fix | **Yes** |
| **Execute Rollback** | Reverts a supported remediation | **Yes** |
| **Details** | Shows additional finding information | No |
| **Playbook** | Provides remediation guidance | No |
| **Tour** | Explains the Autofix workflow | No |
| **Logs** | Shows remediation execution history | No |
***
# 1.6 Reports
Source: https://docs.zero-x.cloud/zerox/connectors/1.6-Reports
title: "Reports"
description: "Generate and review security, compliance, vulnerability, inventory, remediation, and other reports in Zero-X Cloud."
## Overview
The **Reports** module in Zero-X Cloud provides a centralized location for generating and reviewing different types of security and compliance reports.
Reports help users analyze security findings, vulnerabilities, cloud inventory, compliance status, remediation activity, SLA performance, and software dependencies.
The Reports page provides the following report types:
* **Licenses & SBOM**
* **Vulnerability Report**
* **SCA Report**
* **Compliance Report**
* **Jira Report**
* **Remediation Report**
* **SLA Report**
* **Security Findings Report**
* **Inventory Report**
***
# Access Reports
To access the Reports module:
1. Sign in to **Zero-X Cloud**.
2. From the left navigation menu, select **Reports**.
3. The Reports dashboard opens.
4. Select the report you want to generate or view.
***
# Reports Dashboard
The Reports dashboard displays available report types as individual cards.
Each report card contains:
* Report name
* Report description
* Report-specific information
Select the required report card to continue.
***
# Report Types
## 1. Licenses & SBOM
The **Licenses & SBOM** report provides information about open-source software licenses and software components identified in connected repositories.
### Purpose
Use this report to:
* Identify open-source licenses.
* Review software component information.
* Analyze potential license-related risks.
* Export license information.
### Available Information
The report can provide:
* License information
* Software component information
* Repository-related data
* Potential license risks
License data can also be exported to a **CSV** file where supported.
### Steps
1. Open **Reports**.
2. Select **Licenses & SBOM**.
3. Select the required repository or data source.
4. Configure the available report options.
5. Generate the report.
6. Review the license and SBOM information.
7. Export the data when required.
***
# 2. Vulnerability Report
The **Vulnerability Report** provides a detailed view of vulnerabilities identified in code repositories.
### Purpose
Use this report to understand:
* Total vulnerabilities
* Vulnerability severity
* Security findings
* Repository vulnerability distribution
### Steps
1. Open **Reports**.
2. Select **Vulnerability Report**.
3. Select the required repository or data source.
4. Configure the available filters or options.
5. Generate the report.
6. Review the vulnerability findings and severity breakdown.
***
# 3. SCA Report
The **SCA Report** provides a detailed **Software Composition Analysis (SCA)** report for repositories.
It helps users identify vulnerabilities associated with software dependencies.
### Purpose
Use the SCA report to:
* Review software dependencies.
* Identify dependency vulnerabilities.
* Analyze vulnerability severity.
* Understand the security posture of third-party components.
### Steps
1. Open **Reports**.
2. Select **SCA Report**.
3. Select the required repository.
4. Configure the available report options.
5. Generate the report.
6. Review dependencies and associated vulnerabilities.
7. Review the severity breakdown.
***
# 4. Compliance Report
The **Compliance Report** provides detailed information about compliance checks performed against connected data sources.
### Purpose
Use the report to:
* Review compliance status.
* Identify failed compliance checks.
* Review individual compliance controls.
* Analyze security compliance posture.
### Steps
1. Open **Reports**.
2. Select **Compliance Report**.
3. Select the required data source or account.
4. Configure the available compliance options.
5. Generate the report.
6. Review the overall compliance status.
7. Review individual compliance checks.
***
# 5. Jira Report
The **Jira Report** provides reporting information for Jira-related security and repository data.
The report can include information related to:
* Code repositories
* Cloud data sources
* Accounts
* Severity mappings
* Jira-related findings
### Steps
1. Open **Reports**.
2. Select **Jira Report**.
3. Select the required repositories or cloud data sources.
4. Configure the available options.
5. Generate the report.
6. Review the generated Jira information.
***
# 6. Remediation Report
The **Remediation Report** provides information about resolved security findings and remediation activity.
### Purpose
Use the Remediation Report to:
* Track resolved security findings.
* Review historical remediation activity.
* Monitor remediation efforts.
* Understand security posture improvements over time.
### Steps
1. Open **Reports**.
2. Select **Remediation Report**.
3. Configure the required accounts, resources, dates, or other available filters.
4. Generate the report.
5. Review resolved findings.
6. Review historical remediation activity.
### Recommended Use
Use the Remediation Report after performing security remediation to verify and track the progress of security improvements.
***
# 7. SLA Report
The **SLA Report** provides information about Service Level Agreement compliance for security findings.
### Purpose
Use the SLA report to track:
* SLA compliance
* Findings resolved within SLA
* Findings that breached SLA
* Mean time to resolution
* Resolution performance by severity
### Steps
1. Open **Reports**.
2. Select **SLA Report**.
3. Configure the required reporting period.
4. Select the required severity or finding filters where available.
5. Generate the report.
6. Review SLA compliance.
7. Review within-SLA and breached findings.
8. Review mean time to resolution.
***
# 8. Security Findings Report
The **Security Findings Report** provides a detailed overview of security findings identified across connected resources.
### Purpose
Use this report to understand:
* Total security findings
* Finding severity
* Resolved findings
* Security posture
* Resolution percentage
### Steps
1. Open **Reports**.
2. Select **Security Findings Report**.
3. Select the required data source, account, or resource.
4. Configure the available filters.
5. Generate the report.
6. Review the total findings.
7. Review findings by severity.
8. Review the resolved percentage.
***
# 9. Inventory Report
The **Inventory Report** provides a detailed overview of assets discovered across connected environments.
It can provide visibility into:
* Cloud assets
* Code assets
* Kubernetes assets
* Asset distribution
* Security posture
### Steps
1. Open **Reports**.
2. Select **Inventory Report**.
3. Select the required cloud account, data source, or environment.
4. Configure the available report options.
5. Generate the report.
6. Review the inventory information.
7. Analyze the asset breakdown and security posture.
***
***
# Choosing the Right Report
| Report | Primary Purpose |
| - | - |
| **Licenses & SBOM** | Review software components and open-source licenses |
| **Vulnerability Report** | Analyze repository vulnerabilities |
| **SCA Report** | Analyze dependency vulnerabilities |
| **Compliance Report** | Review compliance status and checks |
| **Jira Report** | Review Jira-related repository and cloud security information |
| **Remediation Report** | Track resolved findings and remediation activity |
| **SLA Report** | Monitor SLA compliance and resolution performance |
| **Security Findings Report** | Analyze security findings and severity |
| **Inventory Report** | Review cloud, code, and Kubernetes assets |
***
# Best Practices
## Before Generating a Report
* Confirm that the required data source is connected.
* Select the correct repository, account, or environment.
* Configure the required filters.
* Select an appropriate reporting period when available.
* Confirm that the required scan or data collection has completed.
## While Reviewing a Report
* Check the total number of findings.
* Review severity distribution.
* Investigate critical and high-severity findings.
* Compare resolved and unresolved findings.
* Review trends or historical information when available.
## After Generating a Report
* Download or export the report when required.
* Share the report with relevant security or compliance teams.
* Track remediation activities for unresolved findings.
* Retain reports required for audit or compliance purposes.
***
# Summary
The **Reports** module provides a centralized reporting area for analyzing security and compliance information in Zero-X Cloud.
The available reports cover:
* Software licenses and SBOM
* Vulnerabilities
* Software dependencies
* Compliance
* Jira-related information
* Remediation
* SLA performance
* Security findings
* Asset inventory
The standard process is:
**Open Reports → Select Report → Configure Scope → Generate → Review → Export/Download**
# 1.7 Pentest
Source: https://docs.zero-x.cloud/zerox/connectors/1.7-Pentest
The **Pentest Overview** page provides a centralized view of penetration testing activities, discovered security findings, affected targets, severity distribution, recent assessments, and findings that require action.
## Accessing Pentest Overview
Navigate to:
**Pentest → Overview**
The Overview page contains the following sections.
## 1. Pentest Control Center
The **Pentest Control Center** is the main section of the page. It provides access to autonomous security testing and active discovery.
Click **Start Pentesting** to initiate a new penetration testing activity.
## 2. Starting a Pentest
To start a new penetration test:
1. Navigate to **Pentest → Overview**.
2. Click **Start Pentesting**.
3. Select or configure the required target and assessment details.
4. Start the penetration testing process.
5. Monitor the assessment progress from the **Recent Assessments** section.
6. Review discovered issues in the **Findings** and **Action Needed** sections.
The **Overview** page can be used as the primary dashboard for monitoring the overall status of penetration testing activities and security findings.
## 3. Summary Cards
The summary cards provide a quick overview of the current pentesting status.
| Metric | Description |
| - | - |
| **Total Findings** | Displays the total number of security findings identified during penetration testing. |
| **Scanned Targets** | Displays the number of targets that have been scanned. |
| **Affected URLs** | Displays the number of URLs affected by identified security issues. |
| **Open Findings** | Displays the number of findings that are currently open and require attention. |
| **Validated Findings** | Displays the number of findings that have been validated. |
| **Resolved Findings** | Displays the number of findings that have been resolved. |
## 4. Severity Distribution
The **Severity Distribution** section categorizes findings according to their severity level.
* **Critical** – Highest-priority security findings requiring immediate attention.
* **High** – Serious security findings that should be addressed promptly.
* **Medium** – Security issues requiring remediation based on their potential impact.
* **Low** – Lower-impact security issues that should still be reviewed.
* **Info** – Informational observations that may not require immediate remediation.
The count displayed beside each severity represents the number of findings in that category.
## 5. Recent Assessments
The **Recent Assessments** section displays the latest penetration testing assessments.
Each assessment can display:
* Assessment name
* Target URL
* Assessment progress or status
* Number of findings identified
* Last updated information
Assessment statuses may include:
* **In Progress** – Assessment is currently running.
* **Finished** – Assessment has completed successfully.
* **Failed** – Assessment did not complete successfully.
* **0% Complete** – Assessment has not yet progressed.
Click **View All** to view the complete list of penetration testing assessments.
## 6. Action Needed
The **Action Needed** section highlights security findings that require attention.
Each finding may display:
* **Finding title**
* **Severity**
* **Finding status**
* **Affected URL or target**
* **Detection date**
Examples of findings may include:
* Broken Access Control
* Weak Cryptography
* Weak TLS Cipher Suites
Use this section to quickly identify findings that require investigation or remediation.
## 7. Pentest Navigation
The Pentest module provides the following navigation options:
| Tab | Description |
| - | - |
| **Overview** | Provides a summary of pentesting activities, findings, targets, and required actions. |
| **Assessments** | Displays and manages penetration testing assessments. |
| **Targets** | Displays the targets configured for penetration testing. |
| **Findings** | Displays detailed security findings discovered during assessments. |
# AWS Cross account
Source: https://docs.zero-x.cloud/zerox/connectors/datasource/1.1.1-AWS-Cross-account-role
# Connect AWS Cross Account
Follow these simple steps to complete the setup modal and securely integrate your AWS environment for AI-driven analysis.
## 1. Basic Configuration Follow below steps
1. Once you logged in you will navigate to **Dashboard**.
2. Go to the integration and click on **Connect** button to add AWS Datasource.
3. Enter **Account Name** (e.g., Production-AWS Cross).
4. **Environment**: Click the dropdown menu and select the environment type (e.g., Production, Staging, Development).
5. On Authentication Method Click on Cross account toggle button .
6. Enter **Role ARN** and **External ID** (Click on view guide to generate Role ARN and External ID)
***
title: AWS Cross Integration Setup
description: Set up AWS Cross Integration in Zero-X using a CloudFormation stack and IAM Role.
***
# AWS Cross Integration Setup
Follow the steps below to connect your AWS account with Zero-X.
## Prerequisites
Before starting, make sure you have:
* Access to your AWS account with permission to create CloudFormation stacks.
* Access to your Zero-X account.
* The required AWS region selected for the integration.
## Step 1: Download the CloudFormation Template
Download the CloudFormation template from Zero-X.
The template is used to create the necessary IAM Role required for the AWS Cross Integration.
> **Note:** Keep the downloaded CloudFormation template available for the next step.
## Step 2: Create a CloudFormation Stack
1. Sign in to your AWS account.
2. Open **CloudFormation**.
3. Create a new CloudFormation stack.
4. Upload or select the CloudFormation template downloaded from Zero-X.
5. Follow the AWS CloudFormation steps to create the stack.
The stack will create the IAM Role required by Zero-X.
## Step 3: Generate External ID
Generate the **External ID** from Zero-X.
Copy the generated External ID and paste it into the CloudFormation stack's **ExternalId** parameter.
> **Important:** The External ID entered in AWS must exactly match the External ID generated by Zero-X.
## Step 4: Copy the Role ARN
After the CloudFormation stack is successfully created:
1. Open the **Outputs** tab of the CloudFormation stack.
2. Locate the generated **Role ARN**.
3. Copy the Role ARN.
4. Return to Zero-X and paste the Role ARN into the AWS Cross Integration setup.
7. Select the AWS **Region** in Zero-X.
8. Click **Verify** to validate the provided AWS details.
9. After successful verification, click **Connect**.
# AWS EKS account
Source: https://docs.zero-x.cloud/zerox/connectors/datasource/1.1.1-AWS-EKS-account
# Connect AWS EKS Account
Follow these simple steps to complete the setup modal and securely integrate your AWS environment for AI-driven analysis.
## 1. Basic Configuration Follow below steps
1. Once you logged in you will navigate to **Dashboard**.
2. Go to the integration and click on **Connect** button to add AWS EKS Datasource.
3. Enter **Account Name** (e.g., Production-AWS, Staging-Environment).
4. **Environment**: Click the dropdown menu and select the environment type (e.g., Production, Staging, Development).
5. Enter **Access Key** and **Secret Key** (Click on view guide to generate Access key and secret keys)
# How to generate keys follow below steps
# AWS IAM User Setup for Zero-X EKS Read-Only Access
Follow the steps below to create an AWS IAM user with read-only access for the Zero-X EKS integration.
## Step 1 — Create the IAM User (AWS Console)
1. Sign in to the **AWS Console** as an account administrator.
2. Navigate to **IAM → Users → Create user**.
3. Enter a user name, for example:
`zero-x-eks-readonly`
4. Do **not** select **Provide user access to the AWS Management Console**. This user only requires programmatic access.
5. Click **Next**.
## Step 2 — Attach the EKS MCP Read-Only Policy (AWS Console)
6. On the **Set permissions** screen, select **Attach policies directly**.
7. In the policy search box, enter:
`AmazonEKSMCPReadOnlyAccess`
8. Select the checkbox next to the policy.
9. Click **Next**.
10. Review the permission summary and click **Create user**.
> **Note:** This policy provides read-only observability and troubleshooting access to the EKS MCP service. It does not provide permission to modify EKS clusters, node groups, or workloads.
## Step 3 — Generate the Access Key and Secret Key (AWS Console)
11. From the **IAM Users** list, select the newly created user:
`zero-x-eks-readonly`
12. Open the **Security credentials** tab.
13. Scroll to the **Access keys** section and click **Create access key**.
14. Select **Third-party service** as the use case.
15. Check the confirmation box and click **Next**.
16. Optionally add a description tag, for example:
`Zero-X EKS integration`
17. Click **Create access key**.
18. On the resulting screen, copy the following values:
* **Access Key ID**
* **Secret Access Key**
19. Alternatively, click **Download .csv file** to save the credentials.
> ⚠️ **Important:** The Secret Access Key is displayed only once. Copy or download both credentials immediately and store them securely in a password manager or secrets vault before closing the window.
## Security Recommendation
Never commit AWS access keys or secret keys to source code, Git repositories, configuration files, or public documentation. Store credentials securely using an approved secrets-management solution.
# AWS account
Source: https://docs.zero-x.cloud/zerox/connectors/datasource/1.1.1-AWS-account
# Connect AWS Account
Follow these simple steps to complete the setup modal and securely integrate your AWS environment for AI-driven analysis.
## 1. Basic Configuration Follow below steps
1. Once you logged in you will navigate to **Dashboard**.
2. Go to the integration and click on **Connect** button to add AWS Datasource.
3. Enter **Account Name** (e.g., Production-AWS, Staging-Environment).
4. **Environment**: Click the dropdown menu and select the environment type (e.g., Production, Staging, Development).
5. Enter **Access Key** and **Secret Key** (Click on view guide to generate Access key and secret keys)
# How to generate keys follow below steps
## Step 1: Create the IAM User
1. Sign in to the **AWS Management Console**.
2. Navigate to **IAM** → **Users**.
3. Click **Create user**.
4. Enter a username (for example, `security-audit-user`).
5. Click **Next**.
***
## Step 2: Assign Permissions
1. Select **Attach policies directly**.
2. Search for and attach the following AWS managed policies:
| Policy | Description |
| - | - |
| ✅ **SecurityAudit** | Provides read-only access to AWS security services such as IAM, CloudTrail, AWS Config, GuardDuty, Security Hub, and more. |
| ✅ **ViewOnlyAccess** | Provides read-only access to most AWS resources across your AWS account. |
3. Verify that both policies are selected.
4. Click **Next**.
5. Review the configuration.
6. Click **Create user**.
***
## Step 3: Create an Access Key
1. Open the newly created IAM user.
2. Navigate to the **Security credentials** tab.
3. Scroll down to the **Access keys** section.
4. Click **Create access key**.
***
## Step 4: Select the Access Key Use Case
1. Choose **Command Line Interface (CLI)** (recommended).
2. Click **Next**.
***
## Step 5: Add a Description (Optional)
You can add a description to identify the purpose of the access key.
**Example:**
```text theme={null}
Security Audit Automation
```
Click **Create access key**.
***
## Step 6: Save the Credentials
After the access key is created, AWS displays the following credentials:
| Credential | Example |
| - | - |
| **Access Key ID** | `AKIAxxxxxxxxxxxxxxxx` |
| **Secret Access Key** | `xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx` |
:::warning
The **Secret Access Key** is displayed **only once**. AWS will not show it again after you leave this page.
:::
6. Click **Verify** to validate the provided AWS details.
7. After successful verification, click **Connect**.
# UTHO Integration
Source: https://docs.zero-x.cloud/zerox/connectors/datasource/1.1.10-UTHO
Follow these simple steps to complete the setup modal and securely integrate your AWS environment for AI-driven analysis.
## 1. Basic Configuration Follow below steps
1. Once you logged in you will navigate to **Dashboard**.
2. Go to the integration and click on **Connect** button to add UTHO Datasource.
3. Enter **Account Name** (e.g., Production-UTHO).
4. **Environment**: Click the dropdown menu and select the environment type (e.g., Production, Staging, Development).
5. Enter UTHO API Key (Click on View Guide to generate UTHO API Key).
6. Enter Base URL.
### Utho API Key
1. Obtain your API key or personal access token from your Utho Cloud account settings under **API Management**.
2. Paste the token into the **Utho API Key** field.
***
### Base URL (Optional)
If you are using a custom endpoint or specific proxy URL, enter it in the **Base URL** field. Otherwise, leave this field empty to use the default Utho API base URL.
7. Click on Verify Integration Button .
8. Click on Connect Button.
# E2E Integration
Source: https://docs.zero-x.cloud/zerox/connectors/datasource/1.1.11-E2E
# Connect E2E Cloud Integration
Enter your E2E Cloud API credentials to enable the integration.
### Step 1: General Configuration
1. Go to the integration and click on **Connect** button to add E2E Datasource.
2. Enter **Account Name** (e.g., Production-E2E).
3. Enter your **E2E API key**.(How to generate E2E API key refer user guide)
4. Enter your **E2E Authentication** token.(How to generate E2E Authentication key refer user guide)
5. Enter your **E2E Project ID**.(How to generate E2E project ID refer user guide)
6. Enter your **E2E Location**.(How to generate E2E location refer user guide)
# How to generate keys follow below steps
***
title: E2E Cloud Integration Setup
description: Configure E2E Cloud credentials and project details for integration with Zero-X.
***
# E2E Cloud Integration Setup
Follow the steps below to collect the required E2E Cloud credentials and configure the E2E Cloud integration in Zero-X.
## 1. Sign In to E2E Cloud
1. Open the **E2E Cloud / MyAccount** portal.
2. Sign in using your E2E Cloud account.
3. Make sure your account has permission to:
* Manage API tokens.
* Access the E2E Cloud project you want to scan.
E2E Cloud uses a **Bearer API token** for API authentication. The E2E CLI documentation also refers to the **API Key** and **Auth Token** generated from the MyAccount portal.
***
## 2. Open the API / Token Section
1. Open your **MyAccount** dashboard.
2. Locate the **API** or **API Tokens** section.
3. If you do not already have an API token, create a new token.
4. Enter a descriptive name for the token.
### Example
```text theme={null}
Zero-X Cloud Integration
```
5. Generate the token.
> **Note:** API tokens can be generated and rotated from the E2E Cloud dashboard.
***
## 3. Collect Required E2E Credentials
The Zero-X E2E integration requires the following values:
| API Field | Where It Comes From |
| - | - |
| **API Key** | E2E MyAccount → API/API Token section |
| **Auth Token** | E2E MyAccount → API/API Token section |
| **Project ID** | E2E Cloud → Project |
| **Location** | E2E Cloud project/resource region |
E2E API requests use an API key together with an authorization Bearer token.
***
## 4. Get Your API Key
After creating the API token, E2E provides the credentials associated with the token.
The E2E CLI documentation refers to the **API Key** and **Auth Token** obtained from the E2E MyAccount portal.
Record your **API Key**.
### Example
```text theme={null}
abc123...
```
> **Important:** Treat the API key as sensitive information.
Do not:
* Commit it to Git.
* Put it directly in source code.
* Include it in application logs.
* Share it in screenshots.
* Share it through unsecured communication channels.
***
## 5. Get Your Auth Token
From the same API/token creation process, copy the **Auth Token**.
The E2E API uses this token as a **Bearer token**.
### Authorization Format
```text theme={null}
Authorization: Bearer
```
### Example
```text theme={null}
Authorization: Bearer eyJhbGciOi...
```
> **Important:** The Auth Token is a secret. Store it securely and do not expose it in source code, logs, screenshots, or documentation.
***
## 6. Get Your Project ID
The **Project ID** identifies the E2E Cloud project that Zero-X should access.
1. Open your **E2E Cloud / MyAccount** dashboard.
2. Open the project you want to connect.
3. Locate the **Project ID**.
4. Copy the numeric Project ID.
### Example
```text theme={null}
Project Name: Production Cloud
Project ID: 12345
```
Use the **numeric Project ID**, not only the project name.
Your integration should receive:
```text theme={null}
projectId = 12345
```
> **Note:** E2E APIs use `project_id` to scope API requests to a specific project.
***
## 7. Get Your Location
The **Location** identifies the E2E Cloud region where the project or resources are deployed.
1. Open your E2E Cloud project.
2. Review the project or resource configuration.
3. Identify the associated region.
4. Use the corresponding location value in Zero-X.
For the current MyAccount API documentation, supported locations include:
* **Delhi**
* **Chennai**
> **Important:** Mumbai has been discontinued for the current API operations according to the referenced E2E documentation.
### Example
```text theme={null}
Delhi
```
or
```text theme={null}
Chennai
```
> **Important:** Do not select a location by guessing. Use the location associated with the E2E Cloud project or resources you are connecting.
***
## 8. Final Values for Zero-X
After collecting all required information, your Zero-X E2E integration should contain the following:
| Field | Value |
| - | - |
| **Integration Name** | Production E2E Cloud |
| **API Key** | `` |
| **Auth Token** | `` |
| **Project ID** | `` |
| **Location** | `` |
7. Click **Verify** to validate the provided AWS details.
8. After successful verification, click **Connect**.
# Intune Integration
Source: https://docs.zero-x.cloud/zerox/connectors/datasource/1.1.12-Intune-Integration
# Connect Intune Integration
Enter your Intune application details to enable integration with your system.
***
## Configuration Steps
1. Once you logged in you will navigate to **Dashboard**.
2. Go to the integration and click on **Connect** button to add INTUNE Datasource.
3. Enter **Account Name** (e.g., Production-INTUNE).
4. **Environment**: Click the dropdown menu and select the environment type (e.g., Production, Staging, Development).
5. Enter Tenant ID (Click on View Guide to generate Tenant ID).
6. Enter Client ID (Click on View Guide to generate Tenant ID).
7. Enter Client Secret (Click on View Guide to generate Tenant ID).
# JIRA account
Source: https://docs.zero-x.cloud/zerox/connectors/datasource/1.1.15-JIRA-Integration
# Connect Slack Account
Follow these simple steps to complete the setup modal and securely integrate your Slack environment for AI-driven analysis.
## 1. Basic Configuration Follow below steps
1. Once you logged in you will navigate to **Dashboard**.
2. Go to the integration and click on **Connect** button to add JIRA Integration.
3. Enter **Integration Name** (e.g.,JIRA).
4. Enter **Bot User OAuth Token** (Click on view guide to generate Bot User OAuth Token).
Below is the guide you should use for your actual configuration.
Jira Credentials – ZeroX Setup Guide
**Step 1: Open Jira**
Open your Jira Cloud site:
Jira Cloud
1. Sign in to your Atlassian account.
2. Make sure you have access to the Jira site.
3. Make sure you have permission to access the Jira project that will be used by ZeroX.
**Step 2: Create a Jira API Token**
For the ZeroX integration, you need a Jira API Token.
Open the official Atlassian API Token page:
Atlassian API Tokens
Link:
[https://id.atlassian.com/login?continue=https%3A%2F%2Fid.atlassian.com%2Fmanage-profile%2Fsecurity%2Fapi-tokens%3Futm\_source%3D](https://id.atlassian.com/login?continue=https%3A%2F%2Fid.atlassian.com%2Fmanage-profile%2Fsecurity%2Fapi-tokens%3Futm_source%3D)
1. Sign in to your Atlassian account.
2. Click Create API token.
3. Enter a name for the token.
Example:
ZeroX Jira Integration
4. Select the required expiration period.
5. Click Create.
6. Click Copy to clipboard.
7. Save the token securely.
Atlassian states that API tokens are used with an Atlassian account email for REST API
authentication, and current tokens have an expiration period of up to one year.
Important: You cannot recover the token after leaving the creation screen, so save it
securely.
**Step 3: Get the Jira Email**
The Jira Email should be the email address of the Atlassian account that created the API
token.
Example:
Jira Email: [ssingh@infimatrix.com](mailto:ssingh@infimatrix.com)
The email and API token are used together for Jira REST API authentication.
**Step 4: Get the Jira Host URL**
Your Jira Host URL is your Jira Cloud site URL.
For your example:
Jira Host URL: [https://xyz.atlassian.net](https://xyz.atlassian.net)
Do not add /rest/api/... to the Host URL.
Use:
[https://xyz.atlassian.net](https://xyz.atlassian.net)
**Step 5: Create or Select the Jira Project**
ZeroX also requires a Jira Project Key.
1. Log in to Jira.
2. Click Projects.
3. Select Create project if you need a new project.
4. Select the required project template.
5. Enter the project name.
Example:
Project Name: ZeroX
6. Create the project.
7. Note the Project Key.
Example:
Project Name: ZeroX
Project Key: ZRX
**Important**
The Project Name and Project Key are different.
For example:
Project Name: ZeroX Security
Project Key: ZRX
The Project Key is the value ZeroX needs when creating Jira issues.
**Step 6: Verify the Project Key**
Open the Jira project and check the project details/settings.
For your configuration, the required value is:
Jira Project Key: ZRX
The Project Key can also appear in Jira URLs and issue keys.
For example:
ZRX-123
Here:
ZRX
is the Project Key.
**Step 7: Configure ZeroX Jira Credentials**
The ZeroX configuration should contain the following values:
Provider: JIRA
Name: Jira Account
Jira Host URL: [https://xyz.atlassian.net](https://xyz.atlassian.net)
Jira Email: \
Jira API Token: \
Jira Project Key: ZRX
Example
Provider: JIRA
Name: Jira Account
Jira Host URL: [https://xyz.atlassian.net](https://xyz.atlassian.net)
Jira Email: [abc@gmail.com](mailto:abc@gmail.com)
Jira API Token: \
Jira Project Key: ZRX
Do not use the API token that you pasted in this conversation. Generate a new one.
**Step 8: Verify the Jira Credentials**
You can test the credentials using Jira's REST API.
Example:
curl --request GET \
\--url "[https://xyz.atlassian.net/rest/api/3/myself](https://xyz.atlassian.net/rest/api/3/myself)" \
\--user "[abc@gmail.com](mailto:abc@gmail.com):\" \
\--header "Accept: application/json"
If the credentials are correct, Jira should return information about the authenticated Atlassian
user.
Atlassian officially documents this email + API-token authentication method for Jira Cloud
REST APIs.
**Step 9: Verify the Jira Project**
You can also test whether the authenticated user can access the ZRX project:
curl --request GET \
\--url "[https://xyz.atlassian.net/rest/api/3/project/ZRX](https://xyz.atlassian.net/rest/api/3/project/ZRX)" \
\--user "[abc@gmail.com](mailto:abc@gmail.com):\" \
\--header "Accept: application/json"
If successful, Jira should return information about the ZRX project.
If you receive a 401, check the email/API token.
If you receive a 403, check the user's Jira permissions.
If you receive a 404, check whether the project key is correct and whether the user has
access to the project.
Final Information Required for ZeroX
The user needs to provide:
Jira Host URL:
[https://xyz.atlassian.net](https://xyz.atlassian.net)
Jira Email:
\
Jira API Token:
\
Jira Project Key:
ZRX
Important
For your current ZeroX configuration, you do not need:
Client ID
Client Secret
Callback URL
OAuth 2.0
Authorization Code
Those are for the OAuth 2.0 (3LO) approach.
Your current configuration uses:
Jira Email
* Jira API Token
* Jira Host URL
* Jira Project Key
Atlassian documents this API-token-based Basic Auth approach for scripts and other REST
API clients.
Official Links
Create Jira API Token:
Atlassian API Tokens
Jira Basic Authentication:
Jira Cloud Basic Auth Documentation
Jira REST API:
Jira Cloud REST API Documentation
Your Jira Site:
Jira Cloud Site
One security action I strongly recommend: revoke the API token you pasted above and
create a fresh one before using it in ZeroX.
# OCI Integration
Source: https://docs.zero-x.cloud/zerox/connectors/datasource/1.1.16-OCI-Integration
# Connect OCI Account
Follow these simple steps to complete the setup modal and securely integrate your OCI environment for AI-driven analysis.
## 1. Basic Configuration Follow below steps
1. Once you logged in you will navigate to **Dashboard**.
2. Go to the integration and click on **Connect** button to add OCI Datasource.
3. Enter **Account Name** (e.g., Production-OCI).
4. **Environment**: Click the dropdown menu and select the environment type (e.g., Production, Staging, Development).
5. Enter OCI Tenancy ID (To generate OCI ID refer user guide).
6. Enter OCI User ID (To generate OCI User ID refer user guide).
7. Enter OCI Fingerprint (To generate OCI Fingerprint refer user guide).
8. Enter OCI Private key (To generate OCI Private key refer user guide).
9. Enter OCI Compartment ID (To generate Compartment ID refer user guide).
# Oracle Cloud Integration Setup
Follow the steps below to collect the required OCI credentials and configure your Oracle Cloud account for Zero-X scanning.
## 1. Sign In to Oracle Cloud
1. Open the **Oracle Cloud Console**.
2. Sign in using a user account that can create API keys.
* Typically, an administrator account.
* Or a user with IAM permissions to manage their own API keys.
## 2. Open Your User Profile
1. Click the **Profile** icon in the top-right corner.
2. Select **My Profile** or **User Settings**.
This page contains the information required for API authentication.
## 3. Collect Required OCIDs
You need the following OCIDs:
| API Field | Where to Find It |
| - | - |
| **OCI Tenancy ID** | **User Profile** page or **Administration → Tenancy Details** |
| **OCI User ID** | **User Profile** page |
Both values begin with `ocid1.`.
### Example
```text theme={null}
ocid1.user.oc1..aaaaaaa...
ocid1.tenancy.oc1..aaaaaaa...
```
Copy both values exactly as displayed in the OCI Console.
## 4. Create an API Key
The API key provides the **Fingerprint** and **Private Key** required for authentication.
### Steps
1. Navigate to **My Profile**.
2. Open **API Keys** under **Resources**.
3. Click **Add API Key**.
4. Select **Generate API Key Pair**.
5. Download the generated private key (`.pem`) file.
6. Complete the wizard.
> **Important:** Oracle displays the private key only once during creation. Store the downloaded `.pem` file securely.
### Required Values
After creating the API key, Oracle displays a fingerprint similar to:
```text theme={null}
aa:bb:cc:dd:ee:ff:00:11:22:33:44:55:66:77:88:99
```
Record the following values:
| API Field | Source |
| - | - |
| `fingerprint` | Displayed after API key creation |
| `privateKey` | Contents of the downloaded `.pem` file |
### Example Private Key
```text theme={null}
-----BEGIN PRIVATE KEY-----
MIIE...
...
-----END PRIVATE KEY-----
```
When sending the private key in JSON, either:
* Paste the complete PEM content, or
* Replace line breaks with `\n`.
### JSON Example
```json theme={null}
{
"privateKey": "-----BEGIN PRIVATE KEY-----\nMIIE...\n-----END PRIVATE KEY-----"
}
```
## 5. Get Your Home Region
Identify the **OCI Home Region** for your tenancy.
### Option 1
Go to:
**Administration → Region Management**
### Option 2
Use the **Region Selector** in the top navigation bar.
The Home Region is the region where the tenancy was originally created.
> **Important:** Use the **Region Identifier**, not the display name.
### Example
```text theme={null}
ap-mumbai-1
```
## 6. Get Your Compartment ID
1. Sign in to the **OCI Console**.
2. Open the **☰ Navigation Menu**.
3. Go to **Identity & Security → Compartments**.
4. Locate the compartment you want to scan.
5. Click the compartment.
6. On the compartment details page, copy the **OCID**.
The Compartment ID looks like:
```text theme={null}
ocid1.compartment.oc1..aaaaaaa...
```
## Permissions Required for Full Scanning
To perform comprehensive cloud inventory and security scans, additional read permissions may be required for services such as:
* Identity and Access Management (IAM)
* Compute
* Networking
* Storage
* Database Services
* Monitoring
The exact permissions depend on the resources and services being scanned.
> **Note:** Grant only the permissions required by your organization's security and access-control policies.
## Required Information Checklist
Before configuring the OCI integration in Zero-X, make sure you have the following:
| Required Information | Available From |
| - | - |
| OCI Tenancy ID | User Profile / Tenancy Details |
| OCI User ID | User Profile |
| Fingerprint | API Key creation |
| Private Key | Downloaded `.pem` file |
| Home Region | Region Management / Region Selector |
| Compartment ID | Compartment Details |
Once all required values are collected, they can be entered in the Zero-X OCI integration configuration.
# GCP account
Source: https://docs.zero-x.cloud/zerox/connectors/datasource/1.1.2-GCP-Project
# Connect GCP Project
Follow these simple steps to complete the setup modal and securely input your GCP project details and JSON key.
## 1. Basic Configuration Follow below steps
1. Once you logged in you will navigate to **Dashboard**.
2. Go to the integration and click on **Connect** button to add GCP Datasource.
3. Enter **Data Source Name** (e.g., Production-AWS, Staging-Environment).
4. **Select Environment**: Click the dropdown menu and select the environment type (e.g., Production, Staging, Development).
5. Enter **GCP Project ID** (For details click on view guide).
6. **Select Regions** from dropdown.
7. Enter **Service Account JSON**.(For details click on view guide ).
8. Click on **Verify Integration**.
## How to generate GCP Project ID
## Step 1 : Find the Project ID
1. Sign in to the **Google Cloud Console**.
2. Select your project from the **Project Selector**.
3. On the **Dashboard** or **Project Info** page, copy the **Project ID**.
**Example**
| Field | Example |
| - | - |
| Project Name | Production |
| Project ID | `my-production-project-123456` |
| Project Number | `123456789012` |
Enter the **Project ID** in the integration form.
```text theme={null}
my-production-project-123456
```
***
## Step 2: Select Regions
Choose the regions where your GCP resources are deployed.
Common regions include:
* `us-central1`
* `us-east1`
* `us-west1`
* `europe-west1`
* `asia-south1` (Mumbai)
* `asia-east1`
* `asia-southeast1`
> **Note:** If you're unsure which regions your resources use, select **All Regions** (if supported by your application).
***
## Step 3: Create a Service Account
1. Open **Google Cloud Console**.
2. Navigate to **IAM & Admin → Service Accounts**.
3. Click **Create Service Account**.
4. Enter a service account name (for example, `security-audit-sa`).
5. Click **Create and Continue**.
***
## Step 4: Assign Read-Only Roles
Grant only the minimum permissions required for security scanning.
Assign the following roles:
| Role | Purpose |
| - | - |
| **Viewer** (`roles/viewer`) | Read-only access to most Google Cloud resources. |
| **Security Reviewer** (`roles/iam.securityReviewer`) | View IAM policies and security configurations. |
| **Browser** (`roles/browser`) *(Optional)* | Basic visibility of project resources. |
> **Note:** If your security platform requires additional permissions, assign only the roles documented by the platform.
***
## Step 5: Create the JSON Key
1. Open the newly created **Service Account**.
2. Go to the **Keys** tab.
3. Click **Add Key** → **Create New Key**.
4. Select **JSON**.
5. Click **Create**.
6. A JSON key file will be downloaded automatically.
> **Important:** Store the JSON key securely. It provides access to your GCP project and should never be shared publicly.
***
## Final Step
Return to your application and provide:
* **Project ID**
* **Selected Region(s)**
* **Upload the downloaded JSON Key file**
Click **Connect** to complete the GCP integration.Create a new Google Cloud Project or select an existing project that you want to integrate with Zero-X.
### 2. Create a Service Account
1. In the Google Cloud Console, navigate to **IAM & Admin → Service Accounts**.
2. Create a Service Account with **Viewer** (or the required read-only) permissions.
3. Ensure the account has access to the resources you want Zero-X to analyze.
### 3. Generate Service Account JSON Key
1. Open the created Service Account.
2. Go to the **Keys** tab.
3. Click **Add Key → Create New Key**.
4. Select **JSON**.
5. Download the generated Service Account JSON key securely.
# Azure account
Source: https://docs.zero-x.cloud/zerox/connectors/datasource/1.1.3-Azure-subscription
# Connect Azure Account
Follow these simple steps to complete the setup modal and securely integrate your AWS environment for AI-driven analysis.
## 1. Basic Configuration Follow below steps
1. Once you logged in you will navigate to **Dashboard**.
2. Go to the integration and click on **Connect** button to add AZURE Datasource.
3. Enter **Account Name** (e.g., Production-AZURE, Staging-Environment).
4. **Environment**: Click the dropdown menu and select the environment type (e.g., Production, Staging, Development).
5. Enter **Tenanat ID** (Click on view guide to generate Tenant ID)
6. Enter **Subscription ID**(Click on view guide to generate Subscription ID)
7. Enter **Client ID** (Click on view guide to generate Client ID)
8. Enter **Client Secret** (Click on view guide to generate Client Secret)
## Step 1: Get the Tenant ID
1. Sign in to the **Azure Portal**.
2. Go to **Microsoft Entra ID**.
3. Select **Overview**.
4. Copy the **Tenant ID**.
**Example**
```text theme={null}
Tenant ID
xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
```
***
## Step 2: Get the Subscription ID
1. Go to **Subscriptions**.
2. Select your subscription.
3. Copy the **Subscription ID**.
**Example**
```text theme={null}
Subscription ID
xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
```
***
## Step 3: Create an App Registration
If you already have an App Registration, you can skip this step.
1. Go to **Microsoft Entra ID**.
2. Select **App registrations**.
3. Click **New registration**.
4. Enter a name (for example, **SecurityAuditApp**).
5. Leave the default **Supported account types** unless you have a specific requirement.
6. Click **Register**.
7. After the app is created, copy the following value:
* **Application (Client) ID** → This is your **Azure Client ID**.
***
## Step 4: Create the Client Secret
1. Open your **App Registration**.
2. Go to **Certificates & secrets**.
3. Select **Client secrets**.
4. Click **New client secret**.
5. Enter a description (for example, **Audit Secret**).
6. Choose an expiration period.
7. Click **Add**.
8. Immediately copy the **Value** of the client secret.
> **Important**
>
> Azure displays the client secret value only once. Store it securely before leaving the page.
***
## Step 5: Assign Required Permissions
To allow the application to perform a security audit with read-only access:
1. Go to **Subscriptions**.
2. Select your subscription.
3. Open **Access control (IAM)**.
4. Click **Add** → **Add role assignment**.
5. Assign the following roles:
| Role | Purpose |
| - | - |
| **Reader** | Read-only access to Azure resources |
| **Security Reader** *(Optional)* | Read-only access to Microsoft Defender for Cloud and security information |
6. Under **Member**, select **User, group, or service principal**.
7. Search for your App Registration (for example, **SecurityAuditApp**).
8. Select the app and click **Review + assign**.
***
9. Click **Verify** to validate the provided AWS details.
10. After successful verification, click **Connect**.
# Azure devops
Source: https://docs.zero-x.cloud/zerox/connectors/datasource/1.1.4-Azure-devops
# Connect Azure DevOps
To integrate Azure DevOps with your environment, follow the step-by-step instructions below.
***
## 1. Basic Configuration Follow below steps
1. Once you logged in you will navigate to **Dashboard**.
2. Go to the integration and click on **Connect** button to add Azure Devops Datasource.
3. Enter **Account Name** (e.g., Production-Azure-devops).
4. **Environment**: Click the dropdown menu and select the environment type (e.g., Production, Staging, Development).
5. Enter **Organization URL** (e.g. [https://dev.azure.com/your-organization](https://dev.azure.com/your-organization)).
6. Enter Personal Access Token (Click on view guide to generate Personal Access Token).
7. Click on Verify Credential Button.
8. Click on Connect button .
## Step-by-Step Azure DevOps Credential Generation
### Step 3.1: Locate Your Organization URL
* Navigate to [https://dev.azure.com](https://dev.azure.com) and sign in.
* Select your **Organization** from the left sidebar.
* Note your **Organization URL** from the browser address bar. It follows one of two standard formats:
**Modern format:**
```text theme={null}
https://dev.azure.com/{YourOrganization}
```
Example:
```text theme={null}
https://dev.azure.com/acme-corp
```
**Legacy format:**
```text theme={null}
https://{YourOrganization}.visualstudio.com
```
Example:
```text theme={null}
https://acme-corp.visualstudio.com
```
### Step 3.2: Open User Settings
* In the top-right corner of the Azure DevOps interface, click the **User Settings** icon (gear icon next to your profile avatar).
* Select **Personal access tokens** from the dropdown menu.
### Step 3.3: Create a New Personal Access Token (PAT)
* Click **+ New Token**.
* In the **Create a personal access token** panel, configure the following:
| Field | Configuration |
| - | - |
| **Name** | `Zero-X-Integration` |
| **Organization** | Select your target organization or **All accessible organizations** |
| **Expiration (UTC)** | Choose an expiration policy according to your company security policy, such as 90 days, 180 days, or Custom |
### Step 3.4: Configure Token Scopes & Permissions
Under the **Scopes** section, select **Custom defined** and enable the following **Read** scopes:
| Scope Name | Internal Scope ID | Access Level | Purpose |
| - | - | - | - |
| **Project and Team** | `vso.project` | Read | Enumerate projects, teams, and project-level settings. |
| **Code** | `vso.code` | Read | Enumerate Git repositories, branches, and commit metadata. |
| **Build** | `vso.build` | Read | Inspect build definitions, CI pipeline configs, and run history. |
| **Release** | `vso.release` | Read | Inspect CD release pipelines, environment triggers, and artifacts. |
| **Graph** | `vso.graph` | Read | Read user graph profiles, groups, and membership relationships. |
| **Member Entitlements** | `vso.entitlements` | Read | Read user licenses and group assignment rules. |
| **Service Connections** | `vso.serviceendpoint` | Read | Read service connection endpoints configured for cloud deployments. |
| **Security** | `vso.security` | Read | Inspect security namespace permissions, roles, and ACLs. |
> **TIP**
>
> **Alternative (Quick Setup):** Selecting **Full access** will automatically cover all required read operations across every current and future Azure DevOps service.
### Step 3.5: Save and Copy Your Token
* Click **Create** at the bottom of the drawer.
* **Copy the generated PAT string immediately.**
> **WARNING**
>
> Azure DevOps will never display this token value again after you close this drawer. Store it securely in your password manager or configure it directly in Zero-X.
# How to generate keys follow below steps
# ZERO-X SECURITY · AZURE DEVOPS EXTENSION
Run Zero-X Security scans in your Azure DevOps pipelines.
A step-by-step guide for adding the `ZeroXSecurity@1` task to a pipeline in your own Azure DevOps organization and project — from installing the extension to gating pull requests on findings.
## Extension
**Zero-X.zero-x-security**
## Task
**ZeroXSecurity\@1**
## Version
**1.0.1**
## Minimum Agent
**3.232.1**
## Setup Time
**\~20 minutes**
## In this guide
* How it works
* Before you start
* Setup steps 1–8
* Configuration reference and failure threshold
* More examples
* Output variables
* Troubleshooting
* Security practices and getting help
# How it works
The **Zero-X Security Scan** task runs as a normal step in your pipeline. It asks Zero-X to scan the repository and branch being built, waits for the results, reports them in the pipeline, and fails the build if findings reach the severity you choose.
1. **Pipeline runs**
2. **Task calls Zero-X**
3. **Scans complete**
4. **Results reported**
A push or pull request triggers your Azure pipeline.
Using your API key, over HTTPS, the task starts a scan for this repository and branch.
Vulnerability, IaC, SAST, malware, SBOM and secrets are scanned depending on which scanners are enabled.
Results include counts in the log, a summary tab, a SARIF artifact, and a pass/fail gate.
It works with repositories hosted in **Azure Repos** or **GitHub**, as long as the repository is connected to Zero-X Cloud.
# Before you start
Make sure you have the following:
* An Azure DevOps organization and project containing or connected to the repository you want to scan.
* Permission to install extensions in that organization.
* Permission to create pipelines and variable groups in the project.
* A Zero-X Cloud account with access to your tenant, permission to connect datasources, and permission to create Platform API keys.
* A build agent.
Microsoft-hosted agents such as `ubuntu-latest` work out of the box.
Self-hosted agents need:
* Agent version `3.232.1` or newer
* Node 20 or 24 task support
* Outbound HTTPS access to your Zero-X URL
Default Zero-X URL:
```text theme={null}
https://in.zero-x.cloud
```
# Office365 account
Source: https://docs.zero-x.cloud/zerox/connectors/datasource/1.1.5-Office365
# Connect Office365 Account
Follow these simple steps to complete the setup modal and securely integrate your AWS environment for AI-driven analysis.
## 1. Basic Configuration Follow below steps
1. Once you logged in you will navigate to **Dashboard**.
2. Go to the integration and click on **Connect** button to add AWS Datasource.
3. Enter **Account Name** (e.g., Production-AWS, Staging-Environment).
4. **Environment**: Click the dropdown menu and select the environment type (e.g., Production, Staging, Development).
5. Enter **Access Key** and **Secret Key** (Click on view guide to generate Access key and secret keys)
# Microsoft Entra ID Integration Setup
Follow the steps below to collect the required Microsoft Entra ID credentials for configuring the O365 integration in Zero-X.
## Step 1: Sign in to Microsoft Entra
1. Open the **Microsoft Entra admin center**.
2. Sign in using your organization's Azure/Microsoft 365 account.
3. Open **Microsoft Entra ID** from the portal.
For additional information, refer to the Microsoft documentation:
* [Create a new Microsoft Entra tenant](https://learn.microsoft.com/en-us/entra/identity-platform/quickstart-create-new-tenant)
* [Register an application with Microsoft Entra ID](https://learn.microsoft.com/en-us/entra/identity-platform/quickstart-register-app)
## Step 2: Get the Tenant ID
1. In **Microsoft Entra ID**, go to **Overview**.
2. Locate **Directory (tenant) ID**.
3. Copy the Tenant ID.
### Example
```text theme={null}
Directory (tenant) ID:
98f07078-1234-4567-890a-abcdef123456
```
Use this value as the **Tenant ID** when configuring the O365 integration.
## Step 3: Create or Open App Registration
1. In **Microsoft Entra ID**, go to **App registrations**.
2. If your organization already created an application for the integration, open that application.
3. If no application exists, click **New registration**.
4. Complete the application registration.
5. After registration, open the application's **Overview** page.
> **Note:** If you use an existing application, make sure it is intended for the O365 integration and that you have permission to manage it.
## Step 4: Get the Client ID
On the application's **Overview** page:
1. Locate **Application (client) ID**.
2. Copy the value.
### Example
```text theme={null}
Application (client) ID:
4c8f1234-abcd-4567-9876-123456abcdef
```
This value is your **Client ID**.
## Step 5: Create the Client Secret
1. From the same **App Registration**, go to **Certificates & secrets**.
2. Under **Client secrets**, click **New client secret**.
3. Enter the following:
* **Description:** `O365 Integration`
* **Expires:** Select an appropriate expiry period according to your organization's policy.
4. Click **Add**.
Microsoft Entra will generate a new client secret.
### Important: Copy the Secret Value
After creating the client secret, Microsoft Entra displays the secret information.
> **Important:** Copy the **Value**, not the **Secret ID**.
The secret **Value is displayed only once**. Copy and store it securely immediately after creation.
If you leave the page without copying the value, you will need to create a new client secret.
## Required Information
Before configuring the O365 integration in Zero-X, make sure you have the following:
| Required Field | Where to Find It |
| - | - |
| **Tenant ID** | Microsoft Entra ID → Overview → Directory (tenant) ID |
| **Client ID** | App Registration → Overview → Application (client) ID |
| **Client Secret** | App Registration → Certificates & secrets → Client secrets → Value |
## Security Recommendations
* Treat the **Client Secret** as sensitive information.
* Do not share the secret through email, chat, screenshots, or source code.
* Store credentials securely according to your organization's security policy.
* Monitor the client secret's expiration date.
* Create a replacement before the existing secret expires.
* Use only the permissions required for the O365 integration.
Once the **Tenant ID**, **Client ID**, and **Client Secret** are available, you can enter them in the Zero-X O365 integration configuration.
6. Click **Verify** to validate the provided AWS details.
7. After successful verification, click **Connect**.
# Atera
Source: https://docs.zero-x.cloud/zerox/connectors/datasource/1.1.6-Atera
To enable the Atera integration, complete the configuration modal with your required details and API key.
***
## 1. Basic Configuration Follow below steps
1. Once you logged in you will navigate to **Dashboard**.
2. Go to the integration and click on **Connect** button to add ATERA Datasource.
3. Enter **Account Name** (e.g., Production-ATERA).
4. **Environment**: Click the dropdown menu and select the environment type (e.g., Production, Staging, Development).
5. Select Authentication type API Key or API Token.
6. Enter **API Key** (Click on view guide to generate API key).
# Create Your API Key or API Token
Follow the steps below to create or configure an API key or API token for the Zero-X integration.
1. Go to **Admin > Data management > API** (or the relevant section for API Tokens).
2. Click **Generate API key** or generate a new API token (or edit an existing one).
3. Set **IP restriction** to **Allow all IPs** (scripts run from each device IP).
4. Ensure **Permissions** are set to **Full access** or **Custom Values Write**.
> **Note**
>
> Use the same API key or API token in IT Automation scripts and in the **Zero-X Integration** dialog.
7. Click on Verify Integration button.
# Github
Source: https://docs.zero-x.cloud/zerox/connectors/datasource/1.1.7-Github
# Connect GitHub Repositories
Follow these simple steps to install the GitHub App for your organization and select the repositories you want to monitor.
**Zero-X for Client**
### 1. Open GitHub Repository Integration
Navigate to **Connect GitHub Repositories**. The system displays the repositories that are accessible through the configured GitHub App.
### 2. Configure GitHub App (If Required)
If the GitHub App is not installed, the following message is displayed:
> **GitHub App is not installed for your organization.**
Click **Configure GitHub App**. This redirects you to GitHub to:
1. Install the **Zero-X GitHub App**.
2. Select your GitHub organization or personal account.
3. Choose the repositories to grant access.
4. Complete the installation.
### 3. Search Repositories
Use the **search box** to quickly locate repositories by name.
### 4. Select Repositories
Choose one or more repositories that you want Zero-X to monitor.
**Note:** Only repositories authorized through the GitHub App are displayed.
### 5. Connect
Click **Connect**. Zero-X validates:
* GitHub App installation
* Repository access
* Repository permissions
After successful validation, the selected repositories are connected and ready for **security scanning**.
***
## 1. Configure the GitHub App
If the GitHub App is not yet installed for your organization:
1. Click on the **Configure GitHub App** link inside the repository selection box.
2. You will be redirected to GitHub to authorize and install the integration app for your target organization or account.
3. Grant permissions for all repositories or select specific repositories during the GitHub authorization flow.
***
## 2. Select Repositories
Once the GitHub App is configured:
1. Return to the **Connect GitHub Repositories** modal.
2. Use the **Search repositories...** bar to quickly filter your available repositories.
3. Check the boxes next to the repositories you wish to enable for monitoring.
***
## 3. Complete Integration
* Click the **Connect** button at the bottom right to complete the setup and start monitoring your repositories.
# Bitbucket
Source: https://docs.zero-x.cloud/zerox/connectors/datasource/1.1.8-Bitbucket
# Connect Bitbucket Account
Follow these simple steps to enter your Bitbucket credentials and securely connect your workspace for analysis.
***
## 1. Bitbucket Integration
Provide your workspace details and authentication credentials:
1. Once you logged in you will navigate to **Dashboard**.
2. Go to the integration and click on **Connect** button to Bitbucket Datasource.
3. Enter **Bitbucket Workspace URL** (e.g., Production-AWS, Staging-Environment).
4. Enter Bitbucket username.
5. Enter API Access Token (Follow View guide).
# How to generate API Access Token follow below steps
Bitbucket API Access Token Setup
Follow the steps below to create and configure a Bitbucket API access token.
1. Go to Bitbucket → Personal settings → App passwords.
2. Click Create app password.
3. Enter a name for the app password and select the required permissions, for example:( Repositories: Read )Click Create and copy the generated token.
4. Return to the application modal.Paste the copied token into the API Access Token field.
6. Click the **Verify Integration** button at the bottom right to validate your credentials and complete the setup.
# Gitlab
Source: https://docs.zero-x.cloud/zerox/connectors/datasource/1.1.9-Gitlab
# Connect AWS Account
Follow these simple steps to complete the setup modal and securely integrate your AWS environment for AI-driven analysis.
## 1. Basic Configuration Follow below steps
1. Once you logged in you will navigate to **Dashboard**.
2. Go to the integration and click on **Connect** button to add GITLAB Datasource.
3. Enter **Account Name** (e.g., Production-GITLAB, Staging-Environment).
4. **Environment**: Click the dropdown menu and select the environment type (e.g., Production, Staging, Development).
5. Enter Gitlab Instance URL.
6. Enter Personal Access Token. (Click on view guide to generate PAT ).
7. Click on Connect Button .
8. Select Repository .
9. Click on Verify Integration Button.
# Sonarqube Integration
Source: https://docs.zero-x.cloud/zerox/connectors/datasource/1.2.13-Sonarqube-Integration
# Connecting the SonarQube Integration
This guide walks you through setting up and verifying your **SonarQube Integration** to enable code quality analysis, security vulnerability tracking, and test coverage metrics.
***
## Prerequisites
Before setting up the integration, ensure you have:
* Access to a running **SonarQube** or **SonarCloud** instance.
* A generated **User Token** with appropriate permissions from your SonarQube profile.
* *(For SonarCloud users)* Your **Organization Key**.
***
## Step-by-Step Setup Guide
### Step 1: General Configuration
In the **General Configuration** section, enter the baseline information for this connection.
| Field Name | Required | Description | Example / Note |
| :- | :-: | :- | :- |
| **Integration Name** | **Yes** | A unique, recognizable name for this setup. | `SonarQube - Production` |
| **Environment** | **Yes** | Target environment selected from the dropdown menu. | `Production` or `Development` |
***
### Step 2: SonarQube Credentials
In the **SonarQube Credentials** section, enter your authentication details and instance endpoint:
1. **Base URL** *(Required)*:
* Enter your host server's full URL (e.g., `https://sonarqube.yourdomain.com` or `https://sonarcloud.io`).
2. **Organization** *(Optional)*:
* Enter your organization key.
* **Note:** This field is only applicable if you are using **SonarCloud**.
3. **Token** *(Required)*:
* Paste your SonarQube user token into the **Enter User Token** field.
* Click the **eye icon** (`👁`) inside the field to toggle visibility and confirm the token was entered accurately.
***
### Step 3: Verify and Save
1. Double-check all entered configuration fields for accuracy.
2. Click the **Verify Integration** button in the bottom-right corner.
***
# Slack account
Source: https://docs.zero-x.cloud/zerox/connectors/datasource/1.2.14-Slack_integration
# Connect Slack Account
Follow these simple steps to complete the setup modal and securely integrate your Slack environment for AI-driven analysis.
## 1. Basic Configuration Follow below steps
1. Once you logged in you will navigate to **Dashboard**.
2. Go to the integration and click on **Connect** button to add Slack Integration.
3. Enter **Integration Name** (e.g., Production-Slack, Staging-Environment).
4. Enter **Bot User OAuth Token** (Click on view guide to generate Bot User OAuth Token).
# Slack App Credentials – Setup Steps
Follow these steps to create a Slack App, configure the required permissions, install it in your workspace, and securely obtain the Bot User OAuth Token.
## Step 1: Open Slack App Management
Open the official Slack Apps page:
[Slack API – Your Apps](https://api.slack.com/apps)
1. Sign in to your Slack account.
2. Select the correct Slack workspace.
## Step 2: Create a Slack App
1. Click **Create New App**.
2. Select **From scratch**.
3. Enter the **App Name**.
4. Select the required **Slack Workspace**.
5. Click **Create App**.
### Example App Name
`ZeroX Integration`
## Step 3: Open OAuth & Permissions
1. Open the newly created Slack App.
2. From the left menu, select **OAuth & Permissions**.
3. Scroll to the **Scopes** section.
4. Find **Bot Token Scopes**.
[Slack OAuth & Permissions](https://docs.slack.dev/authentication/installing-with-oauth/)
## Step 4: Add Required Bot Permissions
1. Under **Bot Token Scopes**, click **Add an OAuth Scope**.
2. Add the permissions required by the integration.
For sending Slack messages, add:
```text theme={null}
chat:write
```
[Slack `chat:write` Scope](https://docs.slack.dev/reference/scopes/chat.write/)
> **Security recommendation:** Add only the permissions required by the application.
## Step 5: Install the App
1. Go to **OAuth & Permissions**.
2. Find **OAuth Tokens for Your Workspace**.
3. Click **Install to Workspace**.
4. Review the requested permissions.
5. Click **Allow**.
If you see **Request to Install**, contact your Slack Workspace Administrator for approval.
## Step 6: Get the Bot User OAuth Token
After installation:
1. Go to **OAuth & Permissions**.
2. Scroll to **OAuth Tokens for Your Workspace**.
3. Find **Bot User OAuth Token**.
4. Copy the token.
The token normally starts with:
```text theme={null}
xoxb-
```
### Example Token Format
```text theme={null}
xoxb-XXXXXXXXXXXXXXXXXXXXXXXX
```
> **Important:** Do not use the example token. Copy the actual token generated for your Slack workspace.
## Step 7: Add the Bot to the Required Channel
1. Open the Slack channel where the integration will be used.
2. Add or invite the Slack App/Bot to the channel.
3. For a private channel, make sure the bot is explicitly added to the channel.
## Step 8: Provide the Credential Securely
If the integration requires only the **Bot User OAuth Token**, provide:
```text theme={null}
Slack Workspace:
Bot User OAuth Token: xoxb-...
```
> **Security Warning:** Never share the actual token in public Slack channels, GitHub repositories, Jira comments, documentation, screenshots, or other publicly accessible locations.
5. Click on Verify Integration .
# Onboarding
Source: https://docs.zero-x.cloud/zerox/modules/Onboarding
# Zero-X Cloud Security Platform - Onboarding Documentation
## Overview
The Zero-X Cloud Security Platform onboarding flow is designed to guide new users through the initial setup process, ensuring they have a smooth introduction to the platform's capabilities. The onboarding process consists of three main **Steps: Profile Setup, Data Source Connection, and Security Scan execution**.
The onboarding flow serves as a structured, guided introduction to the Zero-X Cloud Security Platform, addressing the complexities of cloud security setup for new users. It ensures that users are not overwhelmed by the platform's extensive features and instead experience a progressive, step-by-step setup that builds their Security Findings incrementally.
#### 1. Login with Email
Enter basic details (Enter email and forgot password)
1. Forgot Password
Users enter their email and receive a reset link or temporary password to regain access instantly.
Verify email with a one-time password
The process is fast, simple, and designed for secure onboarding.
#### 2.SSO Login Options
1. Social / Third-Party SSO
At the top under "CHOOSE A SIGN IN METHOD", click on one of the available identity provider buttons:
Google: Click the Google button to sign in using your Google account.
GitHub: Click the GitHub button to sign in using your GitHub credentials.
2. Enterprise / Corporate SSO
If your company uses enterprise Single Sign-On linked to your work domain:
Type your work email address into the Email field (placeholder reads Enter corporate email).
Depending on your organization's configuration, entering your corporate email address may automatically redirect you to your company's SSO / Identity Provider page (e.g., Okta, Azure AD, OneLogin).
### 2. Onboarding Flow
The main onboarding flow is a guided, step-by-step process that helps users set up their security monitoring environment.
* #### Step 1: Connect Data Sources
Users choose what they want to secure:
Cloud Accounts: **AWS, GCP, Azure**
Code Repositories: **GitHub**
After connection, Zero-X automatically syncs assets and prepares the environment for scanning.
* #### Step 3: Initial Security Scan (Optional)
Users can run their first scan immediately:
Select scan type
View live progress and results
See findings populate in real time
This step gives users an instant look at their Findings.
# Overview
Source: https://docs.zero-x.cloud/zerox/modules/Overview
The Zero-X Cloud Security Platform represents a paradigm shift in enterprise security management, delivering a unified solution designed to address the complex security challenges of modern cloud and code-driven environments. As organizations increasingly adopt multi-cloud strategies and hybrid infrastructures, Zero-X Cloud provides comprehensive security monitoring, compliance management, and automated remediation across leading cloud providers including AWS, Google Cloud Platform (GCP), Microsoft Azure, hybrid environments, and source code ecosystems such as GitHub and GitLab.. Built from the ground up with enterprise-grade security principles, Zero-X Cloud integrates cloud security, application security, container protection, and IaC analysis into a single, cohesive platform. This holistic approach eliminates the fragmentation typically associated with point solutions, providing security teams with unprecedented visibility and control over their cloud and application Security Findings.
### Application Security
1. Catch issues early so your team fixes problems before they reach production.
2. Spot risky code and weak spots across your apps and services in one place.
3. Protect your secrets by instantly finding exposed passwords, keys, or tokens.
4. Keep your app setup safe by checking configurations before anything goes live.
### Cloud Security
1. Detects cloud misconfigurations across AWS and GCP, including open security groups, public storage, weak encryption, and unsafe defaults.
2. Identify and reduce excessive IAM permissions by analyzing roles, policies, and service usage to generate least-privilege access.
3. Find publicly exposed resources such as internet-facing VMs, buckets, and workloads, with visibility into reachable attack paths.
4. Correlate risks with real exploitability by combining CVEs, network exposure, and misconfigurations for accurate prioritization.
5. Remediate issues instantly with guided fixes, one-click quarantine actions, and automated policy enforcement via cloud APIs.
### Container & Kubernetes Security
1. Scan container images for CVEs, malware, and misconfigurations across all registries.
2. Correlate vulnerabilities to running workloads to expose real impact across clusters and namespaces.
3. Detect risky Kubernetes settings including weak RBAC, unsafe privileges, and insecure defaults.
### Cost Management & FinOps
1. Multi-Cloud Cost Analysis\*\*: Unified cost monitoring across cloud providers
2. Optimization Recommendations\*\*: AI-powered cost optimization insights
3. Budget Management\*\*: Automated alerts for cost thresholds
4. Usage Analytics\*\*: Resource utilization patterns and forecasting
### Automated Remediation
1. Define security guardrails that auto-detect violations across cloud and container environments.
2. Trigger automatic fixes for misconfigurations, exposed secrets, and risky permissions.
3. Apply one-click remediation for patching, key rotation, policy updates, and quarantine actions.
4. Maintain full audit trails with timestamps, policy actions, and compliance evidence logged automatically.
### Cloud Compliance
1. Map cloud resources to standards like CIS, ISO 27001and SOC 2 automatically.
2. Continuously monitor compliance posture with real-time across accounts and regions.
3. Automate evidence collection including logs, configurations, and reports for audit readiness.
# Profile
Source: https://docs.zero-x.cloud/zerox/settings/10.1-Profile
6. Profile:
**Step 1 :-** Go to Profile Overview
**Step 2 :-** You get these options
| |
| - |
| 6.1. Overview |
| 6.2. Security |
| 6.3. Billing |
| 6.4. Team |
| 6.5. Audit Logs |
6.1.Profile
**Step 1 :-** Select Profile
**Step 2 :-** Click Edit Profile
**Step 3 :-** Edit the fields you want to update
**Step 4 :-** click the Save changes button
You can see your personal information here.
# Security Settings
Source: https://docs.zero-x.cloud/zerox/settings/10.2-Security-Settings
**Step 1 :-** Go To Right side menu on same Profile dashboard
**Step 2 :-** You can see security setting option their
**Step 3 :-** Select security
**Step 4 :-** If you have not enabled MFA or any other authentication method you can see here.
**Step 5 :-** Password Policy (last used and last Changed)
# Billing And Subscription
Source: https://docs.zero-x.cloud/zerox/settings/10.3-Billing-And-Subscription
Manage your subscription, billing, and usage
**Step 1 :-** Once you clicked on Billing which present on same dashboard
**Step 2 :-** You can see your Current Plan
**Step 3 :-** Your Billing Profile details
**Step 4 .-** Billing history
**Step 5 .-** Upgrade plan you want to update
**Step 6 :-** If your profile is incomplete, you can complete it by clicking the Complete Profile button .
# Team Management
Source: https://docs.zero-x.cloud/zerox/settings/10.4-Team-Management
**Step 1 :-** Right side menu on profile dashboard
**Step 2 :-** Select Team
**Step 3 :-** You can see your team members with (Role, Status, Last active)
# Audit Log
Source: https://docs.zero-x.cloud/zerox/settings/10.5-Audit-Log
**Step 1 :-** Last option on Profile dashboard is Audit
**Step 2 :-** Select audit
**Step 3 :-** You can see the list of team members of your audit logs which actions are taken by whom
It helps to find user and action with timestamp