Cloud Sentry
For auditors and advisory firms

You found the gaps. We close them.

Independence keeps your opinion clean, and it leaves the client asking somebody else how to fix what you found. That is the work we do, and attestation stays yours.

The question that comes after the findings

Independence is the point of your work and the source of its value. It also means the report ends at the diagnosis, and everyone in the room knows it.

The readiness assessment lands badly

You run it properly and hand back the findings. Then comes the question independence reserves for somebody else: so how do we fix this? The client has just paid for the diagnosis, learns the cure belongs to another firm, and leaves the call still looking for its name.

So they go shopping on their own

Remediation turns out to be sold in project statements of work by firms hearing the context for the first time. A managed security provider quotes them as though they were a company several times their size. The compliance platform they get pointed at reports the problem and leaves the repair to them. The bill to pass the audit outgrows the contract that triggered it.

A company that was trying to do the right thing decides the whole exercise is a racket. That is the client we exist for, and now the one you have a name for.

Two ways this works

One sends us a client who needs the work done. The other is what your fieldwork looks like once it has been.

Referral

For the client who just went pale.

You tell them we exist. That is the whole of it, and it can happen off the engagement, by email or on LinkedIn, at whatever remove your obligations call for. We give them 30 minutes, free, and a straight answer on whether we can help. Where the fit is wrong they hear it on that call.

  • An introduction is all it asks of you
  • Your name reaches the client only on your say-so
  • A reciprocal option, where that keeps the introduction clean
How an engagement is scoped

Already underneath

When we are operating a client you audit.

The reciprocal half, and the one that changes your week as much as theirs. Where we run the environment, the controls are operated on a calendar and the evidence accumulates as a byproduct of the work. The record is already written when you arrive, because it was written as the work happened.

  • Scoped, time-bounded evidence links, one per artifact
  • Live asset, risk, vendor, and lifecycle registers with owners
  • A named operator who answers you directly
What an auditor actually sees

Where the line sits

The line is the whole arrangement.

We implement and operate. You test and attest. The independence rules you work under keep those two jobs in separate firms, which is exactly why this works.

What stays yours

Everything that makes your opinion worth having, held entirely on your side of the line.

  • The testing, the judgement, and the opinion
  • The report, and every conclusion in it
  • Scope, materiality, and what constitutes sufficient evidence
  • The client relationship for audit purposes

What we run

The work that needs an operator: turning controls on, keeping them on, and leaving a record that they were.

  • Remediation of the gaps, carried out and closed
  • Control operation and the monthly framework work between audits
  • Managed detection across endpoint, identity, cloud, and email
  • Evidence collection, with scoped access when you ask for it

Attestation stays with your firm, on every engagement, permanently. That boundary is what makes a referral safe for you to make.

What we commit to

Telling a client about us puts your judgement behind the introduction. These are the terms that make that a reasonable thing to do.

Attestation stays yours

You know this better than we do: under AICPA guidance on independence in SOC engagements, implementation and attestation belong to separate firms, and a breach can void the report your client paid for. We set out how we keep the specialists separate, with that guidance cited, on the partner model.

Your name is yours to give

We tell a client you sent them, or list you as a partner, only on your written say-so. An introduction stays an introduction, and we present it as exactly that.

Scope is written before work starts

Scope covers the work we take on and the work we decline. Our refusals are published on the operated partnership page, and the same list applies to anyone you send us.

We are straight about fit

Significant on-premises infrastructure, hardware, and telephony sit outside what we run, and a referred client hears that on the first call. You hear it from us at the same time.

The client owns their environment

Credentials, configuration, and documentation live in accounts the client owns. That keeps the evidence theirs, and it keeps an exit simple.

Offboarding is included

Ours as well as theirs. What a clean exit looks like, in both directions, is written up on the switching page.

Referral terms are agreed per partner, and one of the options is purely reciprocal. This page describes how we work, ahead of the terms of any particular arrangement.

Our own position, before you ask

  • External penetration test. Planned. Open until a third party has run it.
  • External audit. Planned. Our own SOC 2 report is still ahead of us.

Our own external certification is still ahead of us. We run our own program on the same platform our clients use, with our Microsoft 365, Google Workspace, AWS, Cloudflare, and 1Password tenants connected to it, and we can evidence every control except the two marked open here.

You are going to ask, so it is here in writing first. An operator who volunteers the gaps in their own program is the one worth handing a client to.

How it starts

01

You tell them we exist

One sentence, and it can happen off the engagement if independence requires it. An introduction is all it is, and all it needs to be.

02

We tell them the truth in 30 minutes

Free, and straight. Where the fit is wrong we say so on that call and, where we can, point them at someone better suited.

03

You see what we scoped

What we took on and what we declined, so the engagement reads the same to you as it does to us when you arrive to test it.

Send us the one that went pale.

Start with the client whose assessment ended in a list and an open question.

One call about one client, and a straight answer on whether we are the right operator for them.

The same argument, written for your client. Ready to forward as it stands.