SOC 2 Type II
A SOC 2 Type II report is an independent auditor's opinion on how a provider's controls worked over a period of time.
What SOC 2 Type II is
A SOC 2 Type II report is an independent auditor's opinion on whether a service provider's controls for security, and optionally related areas, operated as described over a stated period.
What it means for you
Type I looks at how controls are designed at one date. Type II also tests that they worked throughout the period, so it is the report most vendor reviews ask for. You get the controls, the tests the auditor ran and any exceptions the auditor noted.
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 2 Type II.
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
What it does not do
Does not make your workload compliant
The report covers the VPSie service. Your own systems, users and data fall outside it.
Covers one period
Each report covers the period it states. It is a record of that period, not a promise about the next one.
Shared responsibility
The report lists controls you are expected to run on your side. The shared responsibility table shows the split.
Using it in your review
Three steps that keep a supplier review short.
Request the document
Ask for the report or entry for SOC 2 Type II 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.
| Standard | In plain words |
|---|---|
| ISO 27001 | The international standard for running information security as a managed, audited system. |
| SOC 3 | A short report on the same kind of controls as SOC 2, written to be shared widely. |
| CSA STAR | The Cloud Security Alliance registry where cloud providers document their security controls. |
| PCI DSS | The security standard for systems that store, process or send payment card data. |
| SSAE 18 | The 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 2 Type II
What is the difference between SOC 2 Type I and Type II?
Type I describes the design of controls at a single date. Type II also tests whether the controls operated effectively across a period of time.
Which criteria does the report cover?
SOC 2 reports use the Trust Services Criteria: security is always included, and availability, processing integrity, confidentiality and privacy are optional. The scope section of the report lists what is included.
How current is the report?
Every report states the period it covers. When you request it, check those dates against your review policy.
Questions from your auditors?
Talk to an expert. We will point you to the right documents and answer your control questions.