Edge Register
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 parts of the estate can run on their own, 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
SiteLinkExposureData
01Leeds Headrow branchalwaysattendedpersonalpayment
07Scarborough branch no backup statedintermittentattendedpersonalpayment
11Cape Town outsourcing site cross-borderalwaysattendedpersonal
15ATM estate off-branch regulated data, nobody therealwayspublicpayment
16Home workers encryption not statedalwaysattendedpersonal
19Print and mail line 1 remote access to plantalwaysattendedpersonalplant
21Survey vessel Northmoor Tern no backup statedintermittenthostilepersonal
30Wakefield deeds vault unrecognisedalwaysattendednone read
30 sites, 399 units20 always, 10 intermittent12 with nobody there23 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.

Alert internal and external users when incidents occur

When a site has an incident, log it once and alert the people on that site's call tree: internal contacts (the site owner, the IT or infrastructure lead, the continuity lead, management) and external contacts (a provider, landlord, carrier or key customer), each by email from Edge Register with your address as Reply-To. Each recipient acknowledges with one link, so the record shows who knows and who has not answered; a contact without email stays on the call list with their phone numbers, and a regulator gets a draft for you to review, never an email. On Solo and Team; the specimen incident is open to read.

One site per line: Site | what runs there | link | data | country | units | backup | segregation | remote access | RTO | encryption. Or just Leeds branch, till system and back-office PC, always on, customer records. Tabs, commas or pipes; a header row is optional and its column names are recognised in any order. A first line jurisdiction: UK | dora: yes | as at: 2026-09-21 sets the home area, ticks the regime and pins the date.
Classification and every reading run in your browser against a published dictionary. Nothing is sent anywhere until you choose to save.
01

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.

02

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.

03

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.

04

Alert internal and external users when incidents occur

Keep contacts and a call tree per site, log an incident at one or more sites with what is affected from the register, and alert internal and external contacts with the template that fits them; each recipient acknowledges by link. The NIS2, DORA and GDPR reporting lines that attach are shown with a time only where the published text fixes one; regulator texts are drafts, never sent. How incident alerts work.

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 our statement of each clause of the standards themselves, published at compliance.theartofservice.com, the same publisher as this register, read against the published text of each standard, and ships with this page as a static file. The register reads your own lines and states the duty in our words; it never grades a site or a vendor's hardware.

Edge Register: the questions buyers ask

What is Edge Register?

Edge Register takes the places your systems run outside the data centre and says what each one carries. For every site it returns what it is, what a loss there costs, the duties that attach and the clause behind each.

What do I paste into Edge Register?

One site per line, with what runs there, how it is connected, what data it holds and where it is. Tabs, commas or pipes work, a header row is optional, and a plain line such as `Leeds branch, till system and back-office PC, always on, customer records` works too.

How many sites can I run for free?

Eight sites are free and no account is needed. The dictionary and the clause text load with the page, and every reading is a comparison of the words on your own lines against them, in your browser.

What is the physical exposure, and where does it come from?

The exposure is attended, unattended, public or hostile, read from your line or taken from the site class. The link is always, intermittent or none.

What does an intermittent link change?

It changes what the continuity and transfer obligations are for that site, and it is one of the readings the register makes per site. Each site also carries one sentence on what a lost, stolen or offline site costs.

Which regimes does it read against?

ISO/IEC 27001:2022 with the 27002:2022 guidance beside it, NIST SP 800-53 Rev 5, NIST SP 800-171 Rev 3 for sites handling CUI, CIS Controls v8, ISO 22301:2019, the GDPR, DORA, the OT overlay of NIST SP 800-82 Rev 3 and NIST SP 800-207 for remote access design. A first line such as `jurisdiction: UK | dora: yes | as at: 2026-09-21` sets the home area and pins the date.

What happens where a site runs plant?

The site carries the NIST SP 800-82 Rev 3 OT overlay on top of the other duties. That is one of the facts that decide which clauses attach to the site.

What happens with a site it does not recognise?

A site that matches nothing against the published dictionary of 38 site classes in nine families is marked unrecognised and never guessed. Its data is left as not read.

What questions do I get for the hardware vendor?

Every site carries six questions to put to the vendor of its hardware, plus one for its class. The RFI page groups them by class, ready to paste.

Can it alert people when a site has an incident?

Yes, on Solo and Team. You log an incident at one or more sites and alert the people on that site's call tree by email, internal and external contacts, each acknowledging with one link so the record shows who knows and who has not answered.

Does it email a regulator for me?

No. A regulator gets a draft for you to review, never an email. The NIS2, DORA and GDPR reporting lines that attach are shown with a time only where the published text fixes one.

Does it grade a site or a vendor's hardware?

No. The register is a reading of your own lines and a statement of the duty in our words, cited to its clause; it does not grade a site or a vendor's hardware.

How Edge Register compares with a spreadsheet, a site survey or a general assistant

A spreadsheet holds the site list, and it is free, but it does not read the site class, the physical exposure, the link or the regulated data into the continuity and transfer duties that attach. A site survey firm visits each place and sees conditions this register can only read from your own words, and a security consultant or a lawyer can advise on DORA, the GDPR or NIS2 for a specific estate; the register never grades a site or a vendor's hardware. A general AI assistant will explain ISO 22301 in plain language, but it will not attach the clauses of ISO/IEC 27001, NIST SP 800-53, NIST SP 800-171, CIS Controls, ISO 22301, the GDPR, DORA, NIST SP 800-82 or NIST SP 800-207 to each of your own lines. Edge Register classifies each pasted site by what runs there, what a loss costs and the duties that attach with the clause behind each, gives six questions for the hardware vendor, and on Solo and Team logs an incident and alerts the site's call tree, each recipient acknowledging by link; a regulator gets a draft for you to review, never an email.

Primary source: ISO/IEC 27001:2022