Buy Template

Wardlow

New

Wardlow raises a $32M Series A to put agents to work in operations

Our Series A

Our Series A

Read the announcement

Read

What our SOC 2 Type II audit tested, in plain English

A SOC 2 badge tells a security team that an auditor looked. It doesn’t say at what. Here’s what our Type II audit tested, and what it didn’t, written for the people who review vendors like us.

In this article

01

Type I is one day; Type II is twelve months of evidence

02

Tested: access, changes, encryption, incidents, backups, vendors

03

Agent-specific: guardrails, least privilege, an uneditable Run Log

Portrait of Hana Sato

Hana Sato

3 min read

SOC 2 Type II

Sampled all year, not one day

One email a month

What we shipped, and what we learned running agents in production.

We completed our second SOC 2 Type II audit this spring, with no exceptions. That sentence goes on our security page. This post is for the people who want to know what it actually means.

Type I and Type II

A Type I report says our controls were designed properly on a single day. A Type II report says they worked, continuously, over a period, in our case twelve months. The auditor doesn’t take our word for it. They sample real evidence across the year: access reviews, change approvals, incident tickets, backup tests.

What was tested

SOC 2 is organized around trust principles. Ours covered security, availability and confidentiality. In practice, the auditor tested things like:

  • Access. Whether staff access to production is approved, reviewed every quarter and removed promptly when someone leaves. They sampled leavers and checked the timestamps.

  • Change management. Whether every change to production is reviewed by a second engineer and tested before release, including changes to models and agent instructions.

  • Encryption. Whether customer data is encrypted at rest and in transit, everywhere it’s stored.

  • Monitoring and incidents. Whether alerts are raised, investigated and closed, and whether incidents follow our written response plan.

  • Backups. Whether backups run daily and restores are actually tested. Ours are tested every quarter.

  • Vendors. Whether we review the security of our own sub-processors.

What’s specific to agents

Agents raise questions a standard SOC 2 scope doesn’t fully answer, so we asked our auditor to include three areas: that guardrails are enforced outside the model, that agent permissions in customer systems follow least privilege, and that the Run Log can’t be edited after the fact. All three are in the report.

What SOC 2 doesn’t tell you

A clean report doesn’t mean a vendor can’t be breached, and it doesn’t cover how your own team configures the product. It also doesn’t say anything about model quality. We cover those separately: an annual penetration test by an independent firm, our ISO 27001 certification, and the adversarial testing we run before every model or instruction change.

How to get the report

Our full SOC 2 Type II report, ISO 27001 certificate and penetration test summary are in our security pack, which we send under NDA within one business day. If your team has a questionnaire, send it with your request. Most of the answers are already in the pack, and I’m happy to take the rest on a call.

Security reviews are slow when vendors make reviewers dig. We would rather show our work.

Portrait of Hana Sato

Written by

Hana Sato

Head of Security & Trust

Wardlow

Agents that do the work. People stay in charge.

Floor 4, 612 Bryant Street, San Francisco, CA 94107

SOC 2 Type II · ISO 27001 · GDPR · HIPAA

© 2026 Wardlow, Inc.

Jeeth, template designer

Crafted

by Jeeth

Create a free website with Framer, the website builder loved by startups, designers and agencies.