Categories
Mining Business

SOC 2 is an attestation, not a certificate. What Type I and Type II actually claim, where the report says what it does not cover, and how to read one in twenty minutes.

Ask a hosting provider whether they are “SOC 2 compliant” and most will say yes. The word does a lot of work in that sentence, and very little of it is the work you need done. SOC 2 is not a certification, there is no pass mark, and two providers holding reports with identical cover pages can be running operations that are nothing alike.

The report itself tells you the difference. Almost nobody reads it.

What the report actually is

SOC 2 is an attestation produced under AICPA standards. An independent accounting firm examines a service organisation’s controls and writes an opinion on them. It is closer to an audit opinion on a set of financial statements than to a certificate on a wall: the auditor is attesting to something specific, in specific words, about a specific period, and the value is entirely in those specifics.

There are two types, and the distinction matters more than anything else on the cover.

Type I says the controls were suitably designed as at a single date. It is a photograph. It tells you the provider had a documented process on the day the auditor looked, and nothing whatever about whether that process was followed the week after.

Type II says the controls operated effectively across a period, usually somewhere between three and twelve months. It is a recording rather than a photograph. A Type II over twelve months is a materially stronger statement than a Type II over three, and a three-month Type II issued shortly after a Type I usually means the provider is at the beginning of its compliance programme rather than the middle of it.

If a provider says “we have SOC 2” and the report is a Type I from eighteen months ago, you have learned something, and it is not the thing they intended you to learn.

The five criteria, and the four you probably do not need

SOC 2 reports are written against the Trust Services Criteria. There are five: Security, Availability, Processing Integrity, Confidentiality and Privacy. Only Security is mandatory. The provider chooses which of the others to include.

For hosted mining, Security and Availability are the two that earn their place. Security covers access control, change management, incident response and the rest of the controls that determine whether somebody can walk into a building or into a network and interfere with your machines. Availability covers the controls behind uptime commitments, which is the criterion that connects most directly to what you are actually paying for. The economics of that connection are set out in our piece on what an uptime guarantee is worth once you read the penalty structure.

Processing Integrity, Confidentiality and Privacy are usually scoped for software businesses handling customer data. A mining host that includes all five is not necessarily stronger than one that includes two; it may simply have a different customer base driving the scope. Read why each one is there before you read it as a virtue.

Where the report tells you what it does not cover

The section buyers skip is the system description, and it is the section that decides whether the rest of the report is relevant to you at all.

The system description defines the boundary of the examination. A report can legitimately cover a provider’s corporate network and SaaS platform while excluding the mining halls entirely. It can cover one facility and not the facility your machines are going into. It can cover the colocation infrastructure while scoping out the operational practices that determine whether a failed hashboard is noticed in an hour or a fortnight.

None of that is deceptive. It is the report doing its job. But a provider is under no obligation to volunteer that their SOC 2 covers a building three states away from yours, and most will not.

Read the description, find the facility list, and check your site is on it.

Exceptions are the point, not the problem

Buyers tend to treat a noted exception as a red flag. It is usually the opposite.

An exception is an instance where the auditor tested a control and found it had not operated as described. A Type II report with zero exceptions across twelve months is either a very tightly run operation or a very narrowly scoped examination, and the second is more common than the first. A report with a handful of exceptions, each with a management response explaining what changed, tells you the auditor was actually testing and the provider was actually fixing.

What you are reading for is pattern. One access-review exception in month three with a documented remediation is ordinary. The same exception recurring in months three, seven and eleven means the remediation did not take, and that is worth a conversation before signing. The same instinct applies to the operational questions in our due diligence checklist for choosing a hosting provider, where repetition is nearly always more informative than any single answer.

Complementary user entity controls

Near the back of most SOC 2 reports is a list of complementary user entity controls, usually abbreviated to CUECs. These are the things the auditor assumes you are doing, and the provider’s controls are only effective if you are.

Typical examples: that you remove departed staff from the provider’s portal promptly, that you keep your own credentials secure, that you review the access lists the provider sends you. If you are not doing them, the control environment described in the report does not exist in your case, whatever the opinion says.

It is a short list and it takes four minutes to read. It is also the only part of a SOC 2 report that assigns you homework, which is presumably why it is the least-read section of a document nobody reads.

Subservice organisations: carve-out or inclusive

Few hosts own every layer. Power comes from a utility, connectivity from a carrier, sometimes the building itself from a landlord. The report handles these through one of two methods.

The inclusive method brings the subservice organisation’s controls into the examination. The carve-out method excludes them and simply states that they exist. Carve-out is far more common and is not a weakness in itself, but it means the report is silent on a layer that may matter enormously to you.

If the facility is leased and the landlord is carved out, the report says nothing about physical security of the building perimeter. That may be fine. It is not fine to assume otherwise because the cover page says SOC 2.

SOC 1 is a different document

Occasionally a provider offers a SOC 1 instead. SOC 1 covers controls relevant to a customer’s financial reporting. It exists for service organisations whose processing flows into their customers’ financial statements, such as payroll processors.

For a mining host it is almost never the document you want. If you asked about operational and security controls and received a SOC 1, either the provider misunderstood the question or is answering a different one.

What to do when there is no report at all

Most hosted mining capacity in North America sits with providers who have never commissioned a SOC 2. That is a fact about the industry, not a verdict on any individual operator. Audits are expensive, and a well-run operator may reasonably have spent the money on transformers instead.

The absence is only a problem if you let it become an absence of evidence generally. Without a report, you are looking for the underlying artefacts directly: documented change management, access logs you can actually be shown, an incident history the provider will discuss specifically rather than in general terms, named responsibility for after-hours response. A provider who can produce those has substance without the attestation. A provider who can produce neither has given you your answer.

The same applies when a broker sits between you and the facility, where the report you are shown may belong to a company that does not operate anything. That problem has its own shape, set out in what to check when you buy hosting through a broker.

Reading one in twenty minutes

If you have a report in front of you and limited time, the order that extracts the most is:

Open at the independent service auditor’s report and read the opinion paragraph — that is where a qualified opinion would appear, and a qualified opinion changes everything that follows. Check the type and the period covered. Go to the system description and confirm your facility and the relevant services are in scope. Scan the testing tables for exceptions and read the management responses. Read the CUECs. Check how subservice organisations are handled.

That is twenty minutes and it tells you more than any sales conversation will.

What this is and is not

A SOC 2 report is evidence that somebody independent examined a defined set of controls over a defined period and wrote down what they found. That is genuinely useful, and it is also all it is. It is not a guarantee of uptime, not a statement about financial health, and not a substitute for reading the hosting agreement, which remains the only document that determines what you are owed when something goes wrong.

Used properly, it narrows the field. Used as a badge, it tells you nothing at all.

If you would rather discuss how a specific facility runs than read about it, you are welcome to speak to our team about capacity, controls and what we can show you directly.

Explore Rax Mining

Categories