A full audit of a multi-tenant voice and chat AI platform
Security and compliance auditA production platform where businesses run AI phone and chat agents for their own customers, with telephony, payments and thirteen CRM integrations.
Read moreVoice agent security test - We call your agent and test what a caller can make it do.
We phone your AI agent, try to break it, and check the parts a simulated caller cannot see: recordings, tool authorization, telephony and consent.
- From $8,500
- 7 to 8 tester days
- Retest and attestation letter
- Fixes as pull requests
What we test
- Recordings, transcripts and how long they are kept
- Caller identity checks before account actions
- Tool authorization for bookings, refunds, transfers and outbound calls
- Manipulation of the agent through spoken instructions
- Telephony abuse, toll fraud exposure and cost limits
- AI disclosure and recording consent
Scope and price - What one test covers
One voice agent on one phone number, with up to five tools and one language.
What raises the price
- More numbers, languages or call flows
- Outbound calling in addition to inbound
- Payments taken by phone (PCI scope)
- Health data in the call (BAA and PHI handling)
Typical engagement
- Starting price
- From $8,500
- Testing time
- 7 to 8 tester days
- Start
- Usually within two weeks of the signed scope
- Report
- Within three business days of the last testing day
A good fit
- AI receptionists, intake, scheduling, collections and support agents
- Agents built on Vapi, Retell, ElevenLabs, LiveKit, Pipecat or Twilio
- Contact center, healthcare or lending customers asking how the agent was tested
Not a fit
- IVR menus without an AI agent
- Testing a phone number you do not own or control
- Legal opinions on TCPA, CIPA or HIPAA
Example finding - What a finding looks like
Based on a real finding from our team's previous work, written in the format of our reports.
HIGHWK-012OWASP LLM06 Excessive agency
A caller can make the voice agent place calls to any number
- Reproduced
- 4 of 20 calls
- Root cause
- The callback tool accepted a number chosen by the model instead of the caller's verified line.
- Fix
- Callbacks limited to the caller's own number, set on the server. Pull request with regression test.
- Retest
- 0 of 20 calls. Closed.
Mapped to the standards your buyers check
| Area | Standards |
|---|---|
| Recordings and transcripts | SOC 2 C1.1, ISO 27001 A.8.10, HIPAA 164.312 |
| Caller identity | NIST SP 800-63B, SOC 2 CC6.1 |
| Tool authorization | OWASP LLM06, OWASP Agentic Top 10 |
| Spoken manipulation | OWASP LLM01, MITRE ATLAS AML.T0051 |
| Telephony and cost | OWASP LLM10, SOC 2 A1.1 |
| Disclosure and consent | FCC 24-17 (TCPA), state recording laws |
Rules of engagement - How we call your agent
Every call is agreed in writing first. Each scenario a tester finds is repeated, so a finding is reported as a rate, not a lucky call.
- Written authorization. The numbers we call, the dates and a minute budget are agreed in writing before the first call.
- Agreed caller numbers. Every number we call from is listed in the authorization. We never call your customers or spoof their numbers.
- Synthetic identities. We never use real customer data or real health information.
- Graded on your transcript. Results are judged on what your agent actually heard and said, not on our own speech recognition.
- Evidence handling. Call recordings are stored encrypted, shared only with the people you name and deleted 30 days after the retest.
- Repeated, not lucky. A tester finds the scenario, then it is repeated many times to measure how often it works.
What you get - Evidence, fixes and a letter you can send.
- A report your auditor can sample. Scope, method, dates, every finding with severity, proof and the exact fix. Written so an auditor can trace a finding from discovery to closure.
- Fix pull requests. Confirmed findings ship with a pull request and a regression test. We open them from a fork or a branch you protect, your engineers review and merge, and we never hold merge or deploy rights.
- Free retest within 90 days. A tester who did not write the fix confirms it holds, and the report is updated with before and after evidence.
- Signed attestation letter. A one page letter for your customers and investors, signed by the lead tester, with an ID your customer can check with us.
- Questionnaire answers. We answer the pentest and AI lines of the questionnaire your customer sent, each one pointing to the part of the report that proves it.
Related evidence
Our team's previous work. Client names stay private, the numbers come from the engagement record.
Combine - Often bought together
FAQ - Questions buyers ask
Is this a legal opinion on TCPA, CIPA or HIPAA?
No. We test the controls and report what we find. Legal conclusions are for your counsel.
How many minutes will you use?
We agree a minute budget up front and stay inside it.
Will my SOC 2 auditor accept your report?
Auditors look for scope tied to your systems, a named method, dated testing, findings with severity and evidence that fixes were retested. Our reports are written to that list.
Who writes the fixes, and how do you stay independent?
We open pull requests from a fork or a protected branch, your engineers review and merge them, and a tester who did not write the fix retests. The attestation letter says who wrote each fix.
Do you test production?
We start with staging or dedicated test tenants. Production is tested only with your written risk acceptance.
Where are you based?
Wardkey is a brand of Meridal Group LLC, a United States company. Testing is performed from the EU. We do not take work that requires US-person testers, such as FedRAMP, CJIS or ITAR scope.
How long does it take?
Most tests start within two weeks of the signed scope and take four to eight tester days. The report follows within three business days.
What if you find nothing?
Then the report says exactly what was tested and how, which is what your customer's reviewer needs to see.
Send us the questionnaire your customer sent.
We will tell you which lines a test answers, in writing, within one business day.
Who we are
- CompanyMeridal Group LLCWyoming, United States
- TestingPerformed from the EUFor clients in the US and Europe