Before using DeepTraQ, ensure that you have completed the basic account setup and have the required assets or integrations available depending on the type of security scan you want to run.
Account Setup
| Requirement | Description |
|---|---|
| DeepTraQ account | Sign up using a business email or authenticate using supported identity providers. |
| Supported sign-in methods | Email and password, Google account, or Microsoft account or Github. |
| Region selection | Select your data residency region during account setup. Currently, only India is supported. |
Note: For potential customers requiring a different data residency, DeepTraq can host the platform in the US region upon request. Please contact sales@deeptraq.ai for region-specific access and onboarding.
Assets Required for Scanning
Different DeepTraQ modules require different types of assets or integrations. Ensure the relevant assets are available before creating scans.
| Module | Required Assets | Description |
|---|---|---|
| Code Security | Git repository access | A repository hosted on GitHub, GitLab, or Bitbucket containing the application source code. Read-only access via Personal Access Token (PAT) is required for private repositories. Public/open-source repositories do not require a PAT. |
| Web Application Security | Target website URL | Public or internal web application URL to scan. Authentication credentials may be required for protected applications. |
| Network Perimeter Security | Public IP addresses | Public-facing IP addresses or hostnames that should be scanned for exposed services and vulnerabilities. |
| Cloud Workload Security | Server or workload access | Workloads such as virtual machines or servers where the DeepTraQ agent can collect vulnerability data. |
| CSPM | Cloud account integration | Cloud account access for AWS, Azure, GCP, or Oracle Cloud to evaluate configuration security posture. Read-only audit access must be provided to ensure secure and non-intrusive assessments. |
Optional Requirements
Some scans may require additional configuration depending on the environment.
| Requirement | Description |
|---|---|
| Authentication credentials | Required for scanning authenticated areas of web applications. |
| Cloud access permissions | Read-only access is required to pull workload details and evaluate cloud configurations for CSPM scans. |
| Repository permissions | Required for code scanning integrations to analyze source code and dependencies |
Ensuring these prerequisites are ready will allow scans to be configured and executed without errors.