Questions we answer on a first call.
Straight answers on access, data, scope and buying. If yours is not here, we will answer it in the walkthrough.
Access and agents
Is 10ETLabs agentless?
Yes, for cloud connections. You grant a reader role, Kubernetes get and list, or a VPS token you already control. Nothing installs in the guest OS unless you choose the optional host sensor, and nothing runs in your clusters unless you install the optional Kubernetes runtime sensor or admission webhook. Opt-in DeepScan is agentless too.
Do you write back to our clouds?
Not by default. Every connection is read-only. Fixes are code you review: Terraform, CloudFormation, Azure CLI or Bicep, gcloud or a Kubernetes patch, or a pull request if you opt in. One-click changes need a separate remediator role that you deploy, and an Owner or Admin approves each one.
What do you read from Azure Entra ID?
With read-only Microsoft Graph permissions: users and guests, groups, service principals, managed identities, app registrations and their credential expiry dates (never secret values), directory roles, Conditional Access and last sign-in dates. If a permission is missing, that area shows as a coverage gap, never as a pass.
Do you inventory CVEs inside every VM?
If you opt in to DeepScan. It snapshots VM disks, scans them with a short-lived scanner in your own account, then deletes the snapshots. Only findings metadata comes back, never values.
Data and privacy
What data do you keep after a scan?
Asset metadata, findings, membership, encrypted connection secrets and Ask 10ET chat history. Not disks, object bodies or packet captures. The Trust center has the full inventory.
Who can open a customer tenant from 10ETLabs?
A platform operator, after MFA when enabled, as a read-only viewer. The session is audited, and no UI or API path returns plaintext credentials to anyone, including our operators.
Does the Ask 10ET assistant send our data to a third party?
Only when the assistant is enabled for your tenant. Then your question and relevant tenant context go to OpenAI. Secrets are never sent, and chat history is stored in your tenant.
Where does SSO fit?
Optional OIDC for the tenant. Membership still requires an invite, and ID tokens are verified against the issuer.
Product scope
What does "from code to cloud" mean here?
Paste Terraform, CloudFormation, ARM or Kubernetes YAML in the console, or run the 10et CLI on every pull request. Built-in pattern rules flag public, open, wildcard, unencrypted, privileged and AI-infrastructure settings. After you connect, the same risk classes are checked on live inventory.
What exactly do you check on AI services?
Configuration on AWS SageMaker and Bedrock, Azure OpenAI, AI Foundry and Azure ML, and Google Vertex AI, linked to the buckets, roles and service accounts behind them. We read configuration only, never prompts, responses or model weights.
Buying and hosting
Can we self-host?
Yes, with a Helm chart or a single VM, on your own Postgres and Redis. Ask 10ET stays off unless you add your own OpenAI key.
How do we buy?
There is no self-serve checkout. Billing is sales-led and invoiced: one master agreement, then one order form per product.
Security questionnaires and DPAs go to our security team: security@10etlabs.com
See it on your own estate before you sign.
A walkthrough in the live console, on a read-only connection to your environment. No agents, no write credentials.
