AdaDocsAda AI for Azure DevOpsTry the demo

Security and trust

What a security or procurement review usually asks about Ada, in one place. The details are in SECURITY.md, PERMISSIONS.md and DATA-HANDLING.md.

Who makes Ada

Ada is made by Valor Consulting Emanuel-Eduard Chirileanu, in Poland ("Valor Consulting", "we").

We are a small vendor. That is a fair concern for a product you build on, so here is what we do about it:

How Ada is built

Part Where it runs Who operates it
Ada's extension In each user's browser, inside Azure DevOps Installed by your organization from the Visual Studio Marketplace
Ada's backend In your Azure subscription: App Service, Key Vault and storage. With the managed service, in our Azure, in a resource group of your own You, or us with the managed service
AI provider Your provider account. With the managed service, ours at cost if you prefer You, or us
License service Our Azure Us

When someone uses an AI feature, Ada sends the content to your backend, and your backend sends it to your AI provider. Nothing goes to us. Ada contains no telemetry and no analytics.

What your backend connects to

For firewall and network reviews. Your backend makes no other outside connections, and your administrators can check that: from backend 1.64.0, Organization settings > Ada AI > Monitoring shows every outside address it called in the last 30 days, with counts and never content.

Address When What goes there
Azure DevOps (dev.azure.com, vssps.dev.azure.com) Always Reads, and the changes users confirm, with the user's or the backend's access (see PERMISSIONS.md)
Your AI provider's address Always, for AI features The content of each AI request
Azure Key Vault and Azure Storage Always, in the deployment we provide Secrets (read only), the backend's own records, and the storage containers administrators name for the Mockup Designer (read only)
Microsoft Entra ID (login.microsoftonline.com) With a Microsoft sign-in, or Entra authentication to your AI provider Sign-in
Azure AI Search and an embeddings model With Ask with search Your index's content and the questions
Azure Managed Grafana With logs for Diagnose a Ticket Log and trace queries
Public search engines, through SearXNG beside the backend, or Brave Search With web search on Search terms only
Google Fonts and the npm registry With the Mockup Designer The names of the fonts and packages your applications use, to copy their look
Your test environments, through a Playwright server With the Mockup Designer's browser Visits to the pages it copies
Servers your administrators connect (Connections) When they set them up The tool calls they allow
Our license service Only once subscriptions start (not yet) Your organization's ID and name, never content

What your administrators control

From backend 1.64.0, under Organization settings > Ada AI:

Two features read with the backend's own access rather than each user's: Ask with search and Diagnose a Ticket. PERMISSIONS.md explains why, and how to limit who uses them.

What we receive

With your own backend:

So we don't process your Ada content, and you need no data processing agreement with us for this setup. If your procurement process wants this in writing, ask us and we'll confirm it.

With the managed service:

Check the images we publish

From backend 1.66.0, we sign each of the three images Ada's backend runs on, with their parts lists:

The parts list is a software bill of materials (SBOM): every package in the image, with its version and license, in the SPDX format. Your security team can feed it to the vulnerability scanner it already uses.

Our public key is ada-images.pub:

-----BEGIN PUBLIC KEY-----
MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEdI93/xMW73H4vvrL0Q2g8wsZRut+
uQpoHdFdN6aPl/+5Dxt1Z0DkueZaeNmGs664jR3dNpcnQoBa1R59xp/c+Q==
-----END PUBLIC KEY-----

To check an image, use cosign and the registry user and password Ada gave you in Set up a backend. This works in Bash, including Azure Cloud Shell:

curl -sSfLO https://adadocs.valor-co.com/deploy/ada-images.pub
cosign login adavalorconsulting.azurecr.io -u "<registry user>" -p "<registry password>"
cosign verify --key ada-images.pub --insecure-ignore-tlog=true adavalorconsulting.azurecr.io/ada-backend:1.66.0

To get the image's parts list, checked with the same key:

cosign verify-attestation --key ada-images.pub --insecure-ignore-tlog=true --type spdxjson \
  adavalorconsulting.azurecr.io/ada-backend:1.66.0 | head -n 1 | jq -r .payload | base64 -d | jq .predicate > ada-backend.spdx.json

A few points:

Test Ada's security yourself

Every organization licensed to use Ada may test the security of its own Ada, without asking us first. Today that is every organization that uses Ada. Allowed:

The rules:

Send what you find to contact@valor-co.com. Don't include credentials or content from your organization.

How fast we fix vulnerabilities

We confirm your report within one business day. A fix is published within 1 to 14 days of your e-mail, depending on how severe the vulnerability is:

Severity (CVSS score) Fix published within
Critical (9.0 to 10.0) 3 days
High (7.0 to 8.9) 7 days
Medium and low (below 7.0) 14 days

What "fix published" means:

If Valor Consulting stops Ada

If we ever stop offering Ada, we will publish:

This is part of the license terms.

Support

Write to contact@valor-co.com.

Business days are Monday to Friday, except public holidays in Poland. What to include is on the Support page.

What's changed

Every release, with its date, is on What's new.