VPSie home

SOC 3

A SOC 3 report is a short summary of an independent audit, written to be shared widely.

SOC 3Details on requestSOC 3Details on request

What SOC 3 is

A SOC 3 report is a general-use summary of an independent audit of the same kind of controls a SOC 2 report covers, without the detailed test results.

What it means for you

It gives procurement and security teams a quick answer they can read in minutes. When your reviewers need control-level detail, ask for the SOC 2 Type II report instead.

What it applies to

The scope stated in the report or entry is what counts, so check that the services you use are listed.

  • VPSie Cloud, the public cloud
  • VPSie Private Cloud, the platform you run on your own site
  • Bare metal servers
  • The data centers that host them

Where it comes up

The situations in which customers usually ask for SOC 3.

Vendor reviews

Procurement and security teams ask each supplier for the same evidence before a contract is signed.

Security questionnaires

Answers on the questionnaire can point to the document instead of repeating long explanations.

Regulated workloads

Teams that handle sensitive data need to show their own auditors what each provider supports.

Renewals and audits

The same evidence is asked for again at renewal and when your own audit cycle comes round.

How to get the report

Reports are provided on request. Tell us which document you need and which services you use.

  • Your company name and the VPSie services you use
  • The standard or report you need
  • Who will read it, and by when
  • Any questions your auditors want answered with it

Request the reportBack to Trust

What it does not do

Has no test detail

A SOC 3 report states the auditor's conclusion. It does not list individual controls or tests.

Does not make your workload compliant

It describes the VPSie service only. Your own systems and data are outside it.

Shared responsibility

The shared responsibility table shows what VPSie runs and what you run.

Using it in your review

Three steps that keep a supplier review short.

Request the document

Ask for the report or entry for SOC 3 and say which VPSie services you plan to use.

Read the scope first

Check that the services and sites you rely on are inside the scope. Anything outside it is not covered by the document.

Map it to your own duties

List what you must still do on your side, such as access rules, patching and backups, and keep that list with the report.

How it fits with the other standards

Each document answers a different question, so reviewers often ask for more than one.

StandardIn plain words
ISO 27001The international standard for running information security as a managed, audited system.
SOC 2 Type IIAn independent auditor reports on how security controls operated over a period of time.
CSA STARThe Cloud Security Alliance registry where cloud providers document their security controls.
PCI DSSThe security standard for systems that store, process or send payment card data.
SSAE 18The attestation standard under which SOC 1 and SOC 2 reports are issued.

GDPR is an alignment of how VPSie handles data, not a certificate. HIPAA has no certificate, see the HIPAA page.

Questions about SOC 3

How is SOC 3 different from SOC 2?

SOC 3 is a short, general-use summary of the audit conclusion. SOC 2 is the full report with the controls, the tests and the results.

Does a SOC 3 report show test results?

No. It gives the conclusion and the scope, not the detailed tests. Request the SOC 2 Type II report if you need those.

Which report should I ask for?

Start with SOC 3 for a summary, because it is short and quick to read. Ask for SOC 2 Type II when your reviewers need control detail and the results of the tests.

Questions from your auditors?

Talk to an expert. We will point you to the right documents and answer your control questions.