New Q1 2027 certification windows are open — lock in your audit before your next release. Schedule a meeting

Cloud platforms

Secure AI deployment on every major cloud

Your AI is only as safe as the cloud configuration underneath it. We publish the configuration we expect on each platform — and certify that yours matches it.

Shared responsibility

The cloud secures the model. You secure the deployment.

Managed AI services like Azure OpenAI, Amazon Bedrock and Vertex AI are secure by design — but almost every setting that decides whether your deployment is safe is yours to configure.

Cloud provider

  • Physical & host security
  • Model hosting and isolation
  • Service availability
  • Not training on your prompts (per provider terms)

You — and what we certify

  • Who and what can call your models
  • Public vs. private endpoints
  • Encryption keys and data retention
  • Guardrails, quotas and gateways
  • Data your AI can retrieve
  • Agent and tool permissions
  • Logging, alerting and response

Cross-cloud comparison

The same controls, in each cloud's language

Every platform can meet the CertiSafe AI baseline. Here's what each control looks like on Azure, AWS and Google Cloud.

ControlMicrosoft AzureAWSGoogle Cloud
Managed model serviceAzure OpenAI in Azure AI FoundryAmazon BedrockVertex AI
Keyless identityMicrosoft Entra ID + managed identities; local (key) auth disabledIAM roles with temporary credentials; no long-term Bedrock API keysService accounts + Workload Identity Federation; service account keys blocked
Least-privilege accessScoped Azure RBAC roles (e.g. Cognitive Services OpenAI User)IAM policies scoped to approved model ARNs; SCPs deny the restNarrow Vertex AI roles; Organization Policy restricts allowed models
Private networkingPrivate endpoints; public network access disabledVPC interface endpoints (AWS PrivateLink) with endpoint policiesVPC Service Controls perimeter; Private Service Connect
Customer-managed keysAzure Key Vault (CMK)AWS KMS customer managed keysCloud KMS (CMEK)
GuardrailsAzure AI Content Safety filters + Prompt ShieldsAmazon Bedrock Guardrails, enforced via IAMModel Armor + Gemini safety settings
AI gateway & quotasAzure API Management AI gateway (token limits)API gateway / proxy tier + service quotasApigee or API gateway + quotas
Sensitive data protectionMicrosoft Purview (DSPM for AI)Guardrails sensitive-info filters; Amazon Macie for S3Sensitive Data Protection (DLP)
Audit loggingDiagnostic settings → Log Analytics; Activity LogBedrock model invocation logging + CloudTrailCloud Audit Logs (incl. Data Access logs)
Threat detectionMicrosoft Defender for Cloud — AI threat protectionAmazon GuardDuty + AWS Security HubSecurity Command Center
Policy as codeAzure PolicyService control policies + AWS Config rulesOrganization Policy Service
RAG / retrieval storeAzure AI Search with security filtersBedrock Knowledge Bases with metadata filteringVertex AI Search / RAG Engine with access controls

Cloud services evolve quickly. Our audit baselines are reviewed every quarter against each provider's current security guidance.

How we certify a cloud deployment

Configuration review and attack testing, together

A configuration scan alone misses how your AI actually behaves. Attack testing alone misses the misconfigurations waiting to be found. We do both.

STEP 1

Read-only access

You grant a time-boxed, read-only identity to the in-scope accounts, subscriptions or projects. No write access, no customer data.

STEP 2

Configuration review

Automated and manual review of every AI resource against the platform baseline: identity, network, keys, guardrails, logging.

STEP 3

Attack testing

Adversarial testing of the AI applications running on that infrastructure — injection, data leakage, agent abuse.

STEP 4

Evidence & certificate

Findings, remediation re-checks, then a certificate and evidence pack you can hand to auditors and customers.

Frequently asked questions

Which cloud platforms does CertiSafe AI certify?

We certify AI deployments on Microsoft Azure (Azure OpenAI in Azure AI Foundry, Azure AI Search, Azure Machine Learning), Amazon Web Services (Amazon Bedrock, SageMaker), and Google Cloud (Vertex AI), as well as Oracle Cloud Infrastructure, Databricks, Snowflake, direct model APIs such as OpenAI and Anthropic, self-hosted open-weight models, and Microsoft 365 Copilot. Multi-cloud environments are certified as a single scope.

Who is responsible for AI security in the cloud — us or the cloud provider?

Both, under the shared responsibility model. The provider secures the underlying infrastructure and the managed model service. You are responsible for how you configure it: who can call the models, whether endpoints are public, which data the AI can reach, which guardrails are enforced, and whether activity is logged. Almost every real-world AI cloud incident is a customer-side configuration issue.

Do you need write access to our cloud accounts?

No. We use a time-boxed, read-only identity scoped to the accounts, subscriptions or projects in scope. We review configuration and metadata, not the content of your prompts or customer data, and access is removed when the audit ends.

Can a multi-cloud AI deployment be certified?

Yes. Many organizations use Azure OpenAI for one workload and Amazon Bedrock or Vertex AI for another. We audit each platform against its own baseline and issue one certification covering the whole in-scope AI footprint.

Running AI on more than one cloud?

We'll scope your whole AI footprint — every cloud, every model, every app — into one certification.