Summary

  • CoreWeave’s trust centre prints ten compliance labels — three SOC 2 Type II reports, five ISO/IEC certificates and two HIPAA compliance reports — and not one of the six pages read for this briefing prints the criteria assessed, the reporting period, the audit firm or a certificate number beside any of them.
  • Four CoreWeave surfaces describe one posture with four different words, and the strongest of them — “current SOC 2 Type II certification” — sits in a blog post naming two services while the trust centre scopes its labels across three.

A compliance badge is not a statement about a company. It is a pointer to a report. The badge says a report exists; the three SOC 2 Type II report bodies themselves, the five ISO/IEC certificates, the auditor’s opinion, and the scope boundary of each document are all somewhere else.

Start with what the property prints. The trust centre for CoreWeave, Inc lists ten artifacts under a Certifications heading on trust.coreweave.com: “SOC 2 Type II Report (CKS and Inference)”, “SOC 2 Type II Report (WandB)”, “SOC 2 Type II Report (BMaaS)”, “ISO/IEC 22301 Certificate”, “ISO/IEC 27017 Certificate (WandB)”, “ISO/IEC 27001 Certificate (WandB)”, “ISO/IEC 27018 Certificate (WandB)”, “ISO/IEC 27001 and 27701 Certificate”, “HIPAA Compliance Report (CKS and Inference)” and “HIPAA Compliance Report (BMaaS)”. Every one of the ten is followed by the same call to action, “Request access”. My count of that list: three SOC 2 Type II report labels, five ISO/IEC certificate labels, two HIPAA compliance report labels.

The same property repeats the list twice more. Its certification-status page prints the phrase “No controls available”, the same ten labels with the same access request, and “No updates available” where a reader would look for a date. Its documentation page prints “No controls available” as well, then the same ten labels, then a subprocessor inventory. Neither page prints a trust-services criteria list, a report period, an issuing audit firm, a certificate number, an expiry date or the name of the legal entity whose controls were examined.

That absence is the finding, and it is worth stating as a count rather than an impression. Of the ten printed labels, none prints the criteria in scope. None prints the period the report covers. None prints the firm that issued the opinion. None prints a certificate number or an expiry. None names a legal person. I am counting fields printed on the page a stranger reaches without credentials; the documents behind “Request access” were not obtained, and nothing here says what they contain.

One CoreWeave page does carry a calendar date, and it is the wrong kind of date. The docs compliance page prints “Last modified on June 10, 2026” — documentation metadata for the page, not the period a report covers and not a certificate’s validity window. The same page describes CoreWeave’s alignment “with SOC 2, ISO 27001, ISO 27017, and ISO 27018 compliance standards” and points to a Compliance Documentation Portal where a reader can request evidence of third-party assessments, with the qualification “where available”. A reader who needed to know whether the June 2026 modification followed a control change, a re-audit or a typo fix has one date and no way to attach it to anything.

Then there is the language. Four CoreWeave surfaces describe one posture, and no two use the same verb. The product security page says the company “aligns its security and compliance programs to industry-standard SOC2 and ISO 27001 frameworks” and requires its data centre colocation providers to adhere to those frameworks through the contract lifecycle; that sentence does not print the phrase “SOC 2 Type II” at all. The docs page says “alignment with”. The trust centre prints “Report”, then gates it. The October 2026 blog post prints the strongest of the four: “We hold ourselves to current SOC 2 Type II certification for Bare Metal and CoreWeave Kubernetes Service”, with the ISO standards as “alignment” and the SOC 2 Type II report “on request”.

Four verbs for one posture is a small thing to notice and a large thing to inherit. A procurement team that reads the blog records a certification. A team that reads the security page records an alignment. A team that reads the trust centre records a report it has asked for and not yet received. The three teams are writing the same vendor into three different risk registers, and the vendor’s own surfaces are what taught each of them a different word.

The scopes do not line up either, and this is recorded as two printed statements rather than one proven contradiction. The trust centre splits its SOC 2 Type II labels three ways — “CKS and Inference”, “WandB”, “BMaaS”. The blog names two services, Bare Metal and CoreWeave Kubernetes Service, and never mentions WandB. Whether one sentence is looser than the other, or whether two of the three scoped reports sit outside the sentence the blog wrote, cannot be settled from the pages read here. What a reader can settle is that the count of scoped labels and the count of named services differ.

The subprocessor inventory is more interesting than its heading suggests. Both trust-centre pages print the sentence “See all 11 subprocessors” under an inventory of organisations CoreWeave says it has engaged under its Data Processing Agreement. The retrieved list names twelve: Backblaze, Inc.; Microsoft Corporation; Anthropic; AWS; Clickhouse; Azure; Coreweave (Affiliate); Datadog; GCP; Hex; Modal Labs, Inc.; OpenAI. The gap between the printed count and my count is one, and the obvious candidate is the affiliate entry, which a vendor might not count as a subprocessor.

That is a guess, not a finding: the list carries no version number, no date and no sentence joining it to any report period, so a reader has no way to know whether the eleven and the twelve are the same set counted two ways or two different sets. A subprocessor list without a date is a photograph of a moving object with no timestamp.

The gating itself deserves plain words, because it is too often read as evasion. Confidentiality is the ordinary condition of an attestation report: the document contains control descriptions and test results that read like an inventory of how to get in, and vendors gate them as a matter of course. The trust centre is hosted on a third-party platform — the page carries “Powered by Wolfia” — and every artifact on it is request-gated rather than downloadable. Before the request step, a buyer holds the label and nothing else. After it, the buyer may hold the report. The two states are different, and the procurement record should not blur them.

Now the stop, named as a stop. The three SOC 2 Type II reports were not obtained; they sit behind “Request access”. The five ISO/IEC certificates were not obtained, and no certificate number, issuing certification body, scope statement or expiry date was printed on any page read for this briefing. No bridge or gap letter covering a period after a report closed was printed anywhere. The trust centre advertises a separate subprocessors address, but its full text was not retrieved, so no count or field claim is drawn from it.

And no CoreWeave page inspected names the legal entity that is the subject of any attestation — the entity that holds the controls may be the entity that signs the customer’s order form, but nothing here demonstrates it.

One reading limit belongs beside those claims rather than at the end. All six pages were read as page text returned by a retrieval adapter, not as rendered HTML inside a logged-in session. Modules collapse in such extraction, and “No controls available” came from an anonymous view; a signed-in customer may see a control list and a period where a stranger sees a sentence. That limit qualifies the absence claims above; it does not dissolve them, because the absence is printed on the surfaces a stranger is given.

So what does a buyer do with a page like this? Two things the page permits and one it does not. It permits asking for the report by the exact label — “SOC 2 Type II Report (BMaaS)”, not “your SOC 2” — because the labels are separable and the wrong one produces the wrong document. It permits putting four questions in the same email as the access request: which trust-services criteria are in scope, what period the report covers, which firm issued it, and which legal entity is the subject.

And it does not permit the assumption that the entity holding the certificate is the entity a customer contracts with, because no page read here says so and the difference is exactly the kind of thing that is discovered after an incident rather than before a signature.

Ten badges, ten access requests, no parameters. The phrase “SOC 2 Type II” did not become worthless by being printed without them — it became a question, and the useful thing about a question is that a buyer can put it to somebody who must answer in writing.