The wider regime · 5.5

Where the data physically sits

Where the data physically sits. What it costs, who decides, and what usually goes wrong.

For an independent reference point, see AWS compliance resources.

The question

Where does the file actually live

Every organisation can answer this for the obvious systems and almost none can answer it completely. The complete answer includes places data goes that nobody chose deliberately.

The obvious part

Cloud services handling covered information

Where a cloud service processes or stores covered defence information, the defence clause requires the provider to meet a specified security baseline or its equivalent, and imposes obligations on you about incident reporting and access.

Which means the choice of service is a compliance decision rather than an IT one, and a service that is excellent and does not meet the baseline is not available to you for that data.

Rests on

The safeguarding clause in the defence acquisition regulation supplement, which sets out the requirement applying to cloud services used to process or store covered defence information.

Which services meet it, and what equivalence means in a given case, is established with the provider and your assessor rather than from a summary.

The unobvious part

Six places data goes that nobody mapped

Backups. Frequently in a different region from the system they protect.

Disaster recovery sites. Same question.

Support tooling. Screen sharing, remote assistance and diagnostic uploads all move data, sometimes abroad.

Logging and monitoring platforms. Which by design receive a copy of a great deal.

Email and collaboration. Where the covered file was attached once and remains.

Vendors' own support staff. Who may be anywhere and who may be able to see what they are supporting.

The question to ask a vendor

Where are your support people

Not where the data centre is: where the humans with administrative access sit, and what nationality arrangements apply to them. Reputable vendors answer this readily because they are asked it constantly by this sector.

It matters for the security requirement and, as the entry on export control notes, potentially for a different regime entirely.

Government cloud offerings

What they are and what they are not

Several providers operate environments intended for this sector, with personnel and location constraints that ordinary commercial environments do not carry.

They cost more, they lag on features, and they answer questions the commercial equivalent cannot. Whether you need one depends on what you put in it, which returns to the boundary decision that governs everything else.

Mapping it

A diagram with arrows leaving the page

Draw where covered information is created, where it is stored, and every place a copy goes. Include the six above. The arrows that leave your organisation are the list of relationships that need examining.

Most suppliers doing this for the first time find at least one they had forgotten, and it is usually a support tool.

Changes

Providers move things

A service that processed your data in one region may not next year, and the change arrives as a release note. Where a contract term requires notice of such changes, it is worth having; where it does not, the review has to catch it.

Add it to the annual supplier review from the entry on your own suppliers.

Also

Elsewhere in the wider regime