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

See every model, and every path to it.

AI-SPM and LLM red-teaming for the Head of AI and the CISO. Findings are read from configuration, with zero calls to your models.

Step 1Training dataBuckets and datasets
Step 2ModelWeights and artifacts
Step 3EndpointThe serving image
Step 4IdentityThe role it runs as
Capabilities

What AI Shield does.

AI inventoryNotebooks, endpoints, custom models, agents, knowledge bases and vector search, alongside the rest of your estate.
AI attack pathsBuilt only from collected evidence. If a hop cannot be read, no path is shown.
Supply chain linkageEach model joined to its training data, artifacts, serving image and the identity it runs as.
Prompt testsThe open-source 10et-ai-test CLI tests for injection, leakage and tool abuse with your own credentials, aligned to the OWASP LLM Top 10.
Model supply chain
1Training data
Buckets and datasets
2Model
Weights and artifacts
3Endpoint
The serving image
4Identity
The role it runs as
0calls to your models
Covers

Where it works.

Amazon SageMakerAmazon BedrockAzure AI FoundryVertex AI

AWS

SageMaker notebooks, endpoints and models; Bedrock custom models, agents, knowledge bases, guardrails and invocation logging.

Azure

Azure OpenAI and AI Services deployments, AI Foundry hubs and projects, Azure ML endpoints, compute instances and AI Search.

Google Cloud

Vertex AI endpoints, models, datasets, training and tuning jobs, Vector Search, RAG corpora, Agent Engine and Workbench.

Licensing: Quoted per cloud account with AI workloads, or per model endpoint. Each product is licensed separately.

The rest of the platform

Works with the other products.

Code Security

SAST, dependencies, secrets and IaC on every pull request.

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

AI projects move fast. The roles and buckets behind them rarely get reviewed.

Most AI risk is ordinary cloud risk in a new place: a public bucket holding training data, a notebook running as admin, an endpoint with no guardrail. The model is only as protected as the configuration around it.

43%

of breached organisations had an incident involving AI tools their security team never approved, more than double the previous year.

IBM and Ponemon Institute, Cost of a Data Breach Report 2026 (as reported by Help Net Security)
81%

more leaked secrets were tied to AI services than the year before, as teams wired models into their code.

GitGuardian, The State of Secrets Sprawl 2026
10

risk categories make up the OWASP Top 10 for LLM Applications, from prompt injection and sensitive information disclosure to excessive agency and unbounded consumption.

OWASP GenAI Security Project, Top 10 for LLM Applications (2025 edition)
Reference

The OWASP Top 10 for LLM Applications, 2025 edition

  1. Prompt injection
  2. Sensitive information disclosure
  3. Supply chain
  4. Data and model poisoning
  5. Improper output handling
  6. Excessive agency
  7. System prompt leakage
  8. Vector and embedding weaknesses
  9. Misinformation
  10. Unbounded consumption

Source: OWASP GenAI Security Project, Top 10 for LLM Applications (2025 edition).

Key terms

The vocabulary, in plain language.

AI-SPM

AI security posture management. An inventory of models, endpoints, notebooks, agents and the data and identities they depend on, with checks on how each is configured.

Model supply chain

Everything a model is built from and runs on: training data, artifacts, the serving image and the role it runs as. A weakness in any link reaches the model.

Prompt injection

Input crafted to make a model ignore its instructions, reveal data or misuse a tool. It is the first entry in the OWASP Top 10 for LLM Applications.

Excessive agency

A model or agent that has been given more permissions or tools than its task needs, so a single bad instruction can do real damage.

LLM red-teaming

Deliberately attacking your own model with injection, leakage and tool-abuse tests before someone else does.

Shadow AI

AI tools and services adopted by staff without the security team knowing, so they sit outside any inventory or policy.

Questions

What buyers ask about this.

Does 10ETLabs call our models or read our prompts?

No. The platform reads configuration only. It never invokes your models and never collects prompts, responses or model weights.

How are prompt tests run, then?

You run them. The open-source 10et-ai-test CLI tests injection, leakage and tool abuse with your own credentials, in your own pipeline. You can upload only the verdicts if you choose.

Which AI services are covered?

Amazon SageMaker and Bedrock, Azure OpenAI, AI Foundry and Azure ML, and Google Vertex AI, each linked to the buckets, roles and service accounts behind it.

What happens when part of a path cannot be read?

No path is shown. Attack paths are built only from evidence that was collected, so a missing hop is never guessed.

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.