For the infrastructure lead whose estate runs outside the data centre

Paste the sites outside the data centre. Get what each one carries.

Paste the places your systems run outside the data centre. Get, per site, what it is and what a loss there costs, the duties that attach to equipment and people off-premises with the clause behind each, what an intermittent link does to your continuity and transfer obligations, the overlay where the site runs plant, and the questions to put to the vendor of the hardware before the next rollout. Eight sites free, no account.

Build your own registerThe dictionary and the clause text load with the page. Every reading is a comparison of the words on your own lines against them, in your browser; nothing leaves it until you choose to save.

A depot worker crouched by stock with a handheld scanner and a tablet — Which of the estate can run away from the data centre, on low-power hardware, over a link that drops: answered per site, with the duty and the clause behind each answer, from the list you already hold. The ten standards it reads against are the ones ticked below.

Specimen: an invented UK building society, 30 siteseight of 30 sites

Site	Link	Exposure	Data
01Leeds Headrow branch	always	attended	personalpayment
07Scarborough branch no backup stated	intermittent	attended	personalpayment
11Cape Town outsourcing site cross-border	always	attended	personal
15ATM estate off-branch regulated data, nobody there	always	public	payment
16Home workers encryption not stated	always	attended	personal
19Print and mail line 1 remote access to plant	always	attended	personalplant
21Survey vessel Northmoor Tern no backup stated	intermittent	hostile	personal
30Wakefield deeds vault unrecognised	always	attended	none read
30 sites, 399 units	20 always, 10 intermittent	12 with nobody there	23 regulated

Link, exposure and the data held, as the register reads them from the pasted line or takes them from the site class. The full register adds the country, the duty rows under ISO 27001, ISO 22301, DORA and the GDPR, nine findings, and the six hardware questions per site.

ISO/IEC 27001:2022 NIST SP 800-53 Rev 5 NIST SP 800-171 Rev 3 (sites handling CUI) CIS Controls v8 ISO 22301:2019 GDPR (EU or UK personal data) DORA financial entity OT overlay (NIST SP 800-82 Rev 3) NIST SP 800-207 (remote access design) Classification and every reading run in your browser against a published dictionary. Nothing is sent anywhere until you choose to save.

Paste the sites you already have

The asset register's site column, the WAN circuit list, the facilities spreadsheet or a line per place from memory: one site per line, with what runs there, how it is connected, what data it holds and where it is, in any order the header names. Every site is matched against a published dictionary of 38 site classes in nine families; a site that matches nothing is marked unrecognised and never guessed.

Read what each site is, and what it carries

Per site: the class and what typically runs there, the physical exposure (attended, unattended, public, hostile), the link (always, intermittent, none), the regulated data it holds, whether it runs plant, and one sentence on what a lost, stolen or offline site costs. Per register: sites by family, by link and by exposure, the regulated-data sites, the plant sites, the cross-border sites. Each reading says whether it came from your line or from the class.

Take the duties and the questions to the rollout

Tick the regimes that reach you and each site carries the clauses that attach by its exposure, link, data and plant: ISO 27001 7.9 and 8.13 with the 27002 guidance beside them, the 800-53 PE, MP and CP families, ISO 22301 8.4, GDPR Chapter V on a site outside the home area, DORA Articles 11 and 12, the 800-82 overlay on plant. Every site carries the six questions to put to the vendor of its hardware, and one for its class; the RFI page groups them by class, ready to paste.

Why a register and not a site survey

The survey firm arrives in a quarter and prices per site. The infrastructure lead is being asked this week which of the estate's systems could run on low-power hardware over an intermittent link, and what that carries. Before anyone visits anything, somebody has to say what each site is, who is there when it runs, how it is connected, what data sits on it and which duty attaches. That is the register this builds, in your browser, from the list you already hold.

The dictionary and the duty table are ours and published in full: every site class it recognises, in nine families, and what each regime attaches to a site by its exposure, link, data and plant. The requirement text behind every duty is drawn from the compliance.theartofservice.com corpus, read against the held text of each standard, and ships with this page as a static file. The register reads your own lines and quotes the duty; it never grades a site or a vendor's hardware.