Skip to content
Defence

Infrastructure your security team can actually review.

For defence organizations and their suppliers: dedicated, single-tenant infrastructure in Canadian data centres, run by a Canadian company, with every layer documented before anything goes live.
Request a meeting

What a defence program has to know before it deploys

Where the boundary is

Where data is stored and processed, which networks reach it and which parties operate each layer, written down for your deployment rather than described in general terms.

Who is in the supply chain

The facility, carrier, hardware and software providers behind the service, identified so your security team can assess each one.

Who can reach it

Administrative access limited to named people, with the approval route agreed with you up front.

Whose law applies

A provider owned outside Canada can be subject to another country's laws. Robson is a Canadian, Indigenous owned company, operating Canadian data centres.

Working with the defence sector is not the same as holding a clearance or approval. Protected B describes the architecture, not a certification. Where Robson holds a credential, Trust and Procurement lists it with its issuer and scope.

What Robson brings.

  • Architecture designed for Protected B workloads
  • Dedicated, single-tenant deployments with no shared tenancy
  • Data centres in Vancouver, Toronto and Montreal
  • Dedicated fibre and wavelengths between sites
  • 99.999% uptime
  • 25 years building secure infrastructure for government and enterprise

Want to talk it through?

A short, open conversation is the quickest way to see whether Robson fits.

Request a meeting 1-833-MY-EMILY

Robson compared with a typical foreign-owned cloud

Large public clouds offer many services. For a defence program, these are the differences that matter.

  • Who owns the operator

    Robson: A Canadian, Indigenous owned company

    Typical foreign-owned cloud: Often a US company, subject to laws such as the US CLOUD Act

  • Tenancy

    Robson: Dedicated, single-tenant servers

    Typical foreign-owned cloud: Shared infrastructure unless you pay for isolation

  • Supply chain

    Robson: Facility, carrier, hardware and software providers named for your deployment

    Typical foreign-owned cloud: A general list of sub-processors

  • Where data lives

    Robson: Our Canadian data centres in Vancouver, Toronto and Montreal

    Typical foreign-owned cloud: The regions you configure

  • Who you deal with

    Robson: Named people who know your deployment

    Typical foreign-owned cloud: Support plans and ticket queues

Deployment boundary

Everything inside your boundary, documented.

Before go-live, your security team receives a written account of each layer of the deployment: what it is, where it is and who operates it.

Your deployment boundary
  1. Facility: The Canadian data centre (Vancouver, Toronto or Montreal) and who operates it
  2. Network: Dedicated fibre and wavelengths, and the carriers behind them
  3. Platform: Single-tenant servers, with no shared tenancy
  4. Access: The named administrators, and how their access is approved
  5. Data: Where data is stored and processed

Every layer is documented for your deployment, so your security team can review it before anything goes live.

Relevant services

Dedicated and custom hosting

Single-tenant servers or a custom design, with boundaries documented for your deployment.

Data protection and recovery

Backup scope, retention and restore testing agreed for each system you must recover.

How an engagement can look

Illustrative examples show how an engagement can be shaped. They do not describe specific clients.

Illustrative exampleDefence supplier

An isolated environment for program data

The situation
A defence supplier needs a separate environment for a program, and its security team must be able to assess every part of it.
What Robson does
Robson provides single-tenant servers in a Canadian data centre, on an architecture designed for Protected B workloads, with administrative access limited to named people and logged.
What changes
Deployment boundaries and every party involved are documented, so the supplier can complete its review before anything goes live.

Common questions

Is Robson certified for Protected B?

Our architecture is designed for Protected B workloads. That is a design statement, not a certification. Any formal assessment we hold is listed in Trust and Procurement with its issuer, scope and date.

Can the environment be isolated from other customers?

Yes. Dedicated deployments use single-tenant servers, with no shared tenancy, and private network connectivity.

How do we share sensitive requirements?

Not through this website. The first meeting covers only what can be discussed openly. We then agree a channel your organization approves for anything sensitive.

Can you support a supplier, not just a department?

Yes. We work with defence organizations and the suppliers that support their programs.

The first meeting

The first meeting is a non-sensitive conversation about your organization, the kind of environment you need and your timeline. Anything sensitive comes later, through a channel your organization approves.

It helps to bring

  • Your organization and a contact for the program
  • The type of environment you are considering: dedicated, hybrid or on-premise
  • Your timeline and contracting route
  • Constraints you can describe without sensitive detail

Please do not send classified, protected or otherwise sensitive information through this website. We will agree a suitable channel for any detail that needs one.

Supplier information you can review now is in Trust and Procurement.

Start with an open conversation.

Tell us who you are and how to reach you. We will arrange a meeting with the right people on our side.

Request a meeting Call 1-833-MY-EMILY

Or email sales@robsoninc.com