See 10ETLabs on a read-only connection to your own estate. Request a demo →
Code Security

From pull request to live resource.

Agentless code-to-cloud scanning of source, dependencies, secrets and infrastructure as code on every pull request, with zero file contents uploaded from CI.

Step 1RepositorySource, IaC and lockfiles
Step 2Pull requestChecked on every PR
Step 310et CLIOffline check in CI
Step 4Live resourceLinked in the asset graph
Capabilities

What Code Security does.

SAST with taint trackingFollows untrusted input to the query or command it reaches, so each finding shows the path.
Vulnerable dependenciesOpen-source packages matched against the OSV database across npm, PyPI, Go, Maven and more.
Secrets detectionLeaked keys and tokens in repositories, flagged before they reach a build or a production host.
Infrastructure as codeTerraform, CloudFormation, ARM and Kubernetes YAML, including rules for public training data and exposed AI endpoints.
Code to cloud
1Repository
Source, IaC and lockfiles
2Pull request
Checked on every PR
310et CLI
Offline check in CI
4Live resource
Linked in the asset graph
0file contents uploaded from CI
Connects to

Where it works.

GitHubGitLabBitbucketAzure DevOps

In the pull request

Run the 10et CLI in GitHub Actions, GitLab CI, Azure Pipelines or Bitbucket Pipelines. A failing check stops the merge.

In the console

Paste Terraform, CloudFormation, ARM or Kubernetes YAML and see the same rules applied.

After you connect

The same risk classes are checked on live inventory, so code and cloud findings line up.

Licensing: Quoted on your environment. Each product is licensed separately.

The rest of the platform

Works with the other products.

AI Shield

AI-SPM and LLM red-teaming across your model estate.

Learn more →

Cloud Posture

CSPM and CIEM, with workloads, containers and vulnerabilities, ranked.

Learn more →

Compliance & Privacy

Continuous GRC, signed evidence packs, and DPDP Act and GDPR consent management.

Learn more →
Why it matters

More code is being written than ever. More secrets are leaking with it.

AI-assisted coding has raised the volume of commits, and credentials are ending up in repositories faster than teams can revoke them. The cheapest place to stop a misconfiguration or a leaked key is the pull request.

28.65M

new hardcoded secrets were pushed to public GitHub in 2025, a 34% rise and the largest yearly jump on record.

GitGuardian, The State of Secrets Sprawl 2026
64%

of the valid secrets leaked in 2022 had still not been revoked four years later. Finding a leaked key is not the same as closing it.

GitGuardian, The State of Secrets Sprawl 2026
48%

of breaches involve a third party, after a 60% rise in a single year. Suppliers, shared components and vendor accounts are now part of your own attack surface.

Verizon, 2026 Data Breach Investigations Report
Key terms

The vocabulary, in plain language.

SAST

Static application security testing. Analysing source code for flaws such as injection without running it.

Taint tracking

Following untrusted input from where it enters the code to where it is used, so a finding shows the whole path and not just one line.

Dependency scanning

Matching the open-source packages you use against known vulnerabilities. 10ETLabs matches against the OSV database.

Secrets detection

Finding keys, tokens and passwords committed to a repository before they reach a build or a production host.

Infrastructure as code

Templates such as Terraform, CloudFormation, ARM and Kubernetes YAML that define cloud resources. A mistake here becomes a live misconfiguration on deploy.

Code to cloud

Linking a finding in a template to the live resource it created, so the cause is fixed once and confirmed in the account.

Questions

What buyers ask about this.

Does our source code leave the pipeline?

No file contents are uploaded from CI. The 10et CLI runs offline in your pipeline. Uploading findings metadata is optional and uses write-only CI tokens.

Which pipelines does the pull-request check run in?

GitHub Actions, GitLab CI, Azure Pipelines and Bitbucket Pipelines, with baselines and severity gates so existing issues do not block every merge.

Is the infrastructure-as-code check a full policy engine?

No. It is a set of built-in, line-level pattern rules for public, open, wildcard, unencrypted, privileged and AI-infrastructure settings. The same risk classes are then checked on live inventory.

Can it open a fix for us?

Yes, if you opt in. A generated Terraform patch can arrive as a pull request on a new branch for review. Write scope on a source-control connection is off by default.

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.