Depot and cash centre
Scanners, label printers, a routing PC, note counters or sorters, a vault system and a CCTV recorder, with a small office at the side.
How the register reads it
| Also called | cash centre, parcel hub, archive store |
|---|---|
| Family | Depot, warehouse and yard |
| Exposure by default | Attended: staffed in shifts, with a guarded cash floor where there is one; the yard gate is the perimeter. A line that says attended, unattended, public or hostile (outdoors, in transit, at sea) overrides it. |
| Link by default | Always: a fixed line, with the scanners falling back to their local buffer. A line that names the link (fibre, 4G, satellite, radio, offline) overrides it. |
| Regulated data by default | None; a line that names customer, staff, patient, card or controlled data adds it. |
| Runs plant | Not by default; a line that names PLCs, SCADA, RTUs or HMIs adds it. |
| What a loss costs | A depot offline scans to a buffer and catches up; a depot broken into loses the goods, the counters and whatever records were on the routing PC. |
| Contract focus | Device buffer and sync behaviour, repair and swap times, out-of-hours alarm response, secure disposal of scanners and recorders. |
What each regime attaches
10 clauses across 6 regimes, on the class defaultsShown on a register for the regimes you tick, by the exposure, link, data and plant the line states; with none ticked, the ISO 27001 rows are the default. Requirement text is our own statement of each clause, from the standards published at compliance.theartofservice.com, the same publisher as this register, read against the published text of each standard: our statement of each clause, not the instrument verbatim.
ISO/IEC 27001:2022, with the 27002:2022 guidance beside it
Attaches to every site: the off-premises, equipment, media, endpoint, backup, redundancy, network and continuity controls of Annex A, by the site's exposure, link, data and plant. With nothing ticked these rows render as the default.
ISO 27001 7.9 Security of assets off-premisesProtect assets used or held off-site.
ISO 27002 7.9 guidance: Requires assets located away from the organisation's premises to be protected.
Common gap: Missing offsite asset register
Source framework: ISO/IEC 27001:2022
ISO 27001 7.13 Equipment maintenanceMaintain equipment correctly to preserve availability, integrity and confidentiality.
ISO 27002 7.13 guidance: Requires equipment to be maintained correctly, so that information stays available, intact and confidential.
Common gap: no documented maintenance schedule
Source framework: ISO/IEC 27001:2022
ISO 27001 8.9 Configuration managementEstablish, document, implement, monitor and review secure configurations for hardware, software, services and networks.
ISO 27002 8.9 guidance: Requires configurations of hardware, software, services and networks, including their security configurations, to be established, documented, implemented, monitored and reviewed. Supporting material frames this as a standing process that keeps systems configured securely and consistently.
Common gap: outdated baselines
Source framework: ISO/IEC 27001:2022
NIST SP 800-53 Rev 5
Attaches to every site: the PE family for the premises and the alternate work site, MP for the media, AC-17, AC-19 and AC-20 for remote access, mobile devices and external systems, the CP family for the sites that lose their link, SC-7 for the boundary and SI-7 and CM-8 for what runs there.
SP 800-53 CM-8 System component inventoryRequires an accurate inventory of system components that covers every component, avoids duplicate or cross system accounting, is held at the granularity needed for tracking and reporting, carries the information the organization has defined for accountability, and is reviewed and updated on a defined frequency.
Common gap: Cloud and container assets absent because inventory is built from a fixed asset register
Source framework: NIST SP 800-53 Rev 5
SP 800-53 PE-3 Physical access controlRequires physical access authorizations to be enforced at defined entry and exit points by verifying authorization before entry and controlling ingress and egress with defined mechanisms or guards, physical access audit logs to be kept, publicly accessible areas to be controlled, visitors to be escorted and their activity controlled in defined circumstances,...
Common gap: Tailgating unaddressed, so an authorization check happens for only the first person through
Source framework: NIST SP 800-53 Rev 5
SP 800-53 SI-7 Software, firmware, and information integrityRequires integrity verification tools to be employed to detect unauthorized changes to organization-defined software, firmware and information, and requires organization-defined actions to be taken when such unauthorized changes are detected.
Common gap: Integrity monitoring produces constant noise from routine change and is therefore ignored
Source framework: NIST SP 800-53 Rev 5
CIS Controls v8
Attaches to every site: the asset inventory on all of them, anti-malware on the unattended and public ones and on plant, automated and isolated backups where the link is intermittent or absent, remote wipe and the VPN on portable and remote devices.
CIS v8 CIS-1.1 Establish and Maintain Detailed Enterprise Asset InventoryEstablish and maintain an accurate, detailed, and up-to-date inventory of all enterprise assets with the potential to store or process data, to include: end-user devices (including portable and mobile), network devices, non-computing/IoT devices, and servers. Ensure the inventory records the network address (if static), hardware address, machine name, enterp...
Common gap: Safeguard implemented for some assets but not all in scope
Source framework: CIS Controls v8
ISO 22301:2019
Attaches the business continuity plans and procedures to every site, and the plan content and recovery clauses to the sites whose link is intermittent or absent.
ISO 22301 8.4.1 GeneralPut in place and keep up a response structure that allows relevant interested parties to be warned and informed in good time. It needs plans and procedures for steering the organization through a disruption and for triggering the continuity solutions, identified and documented from the strategies and solutions that were selected, and procedures that are spec...
Common gap: Procedures written for one rehearsed scenario, brittle against anything else
Source framework: ISO 22301:2019
DORA, the Digital Operational Resilience Act
Attaches Article 11 (response and recovery) to every site of a financial entity and Article 12 (backup, restoration and recovery) to the sites whose link is intermittent or absent; a site with no recovery objective is a finding. An entity listed in Article 16(1) follows the simplified framework of Article 16 instead of Articles 11 and 12.
DORA Art. 11 Response and recoveryFinancial entities adopt an ICT business continuity policy within their overall continuity policy and implement it through documented arrangements that keep critical or important functions running, contain and resolve incidents, estimate preliminary impacts, and drive crisis communication and reporting under Articles 14 and 19; they run a business impact ana...
Common gap: Plans tested only for critical systems, not for systems supporting all functions
Source framework: DORA (Regulation (EU) 2022/2554)
NIST SP 800-207, zero trust architecture
Attaches the satellite-facility deployment scenario to every site and the two design tenets (every communication secured, every asset's posture monitored) to the sites where remote access is named. No regime page: it renders on the remote-access rows and the finding.
SP 800-207 SC-SATELLITE Deployment Scenario: Enterprise with Satellite FacilitiesApplies ZTA to an organization with a headquarters plus geographically dispersed locations and remote workers that have no full enterprise-owned network.
Common gap: VPN-only model treated as zero trust
Source framework: NIST SP 800-207
Questions for the hardware vendor
six, and one for the classFor the scanners, the routing PC, the counters or sorters and the recorder, over the fixed link:
- Can you show measured boot or firmware attestation on the equipment, and how a failed check reports back over the fixed link?
- How does the equipment take an update unattended over the fixed link, and how does it roll back on its own when the update fails part way?
- Can a lost or stolen unit be wiped remotely, and what happens to the wipe command while the unit is offline?
- Is local storage on the equipment encrypted at rest with the key held off the device, and can that be verified from the fleet console?
- Can the equipment be recovered to a known state by a non-technical person on site, without a technician's visit?
- What spares, lead times and end-of-support dates apply to the equipment, and who holds the spares nearest the site?
For this class: How long do the scanners buffer offline, and what happens to the buffered records if a scanner is lost before it syncs?
Findings this class can raise
- Concentration in one class or one link type
One site class holding a third or more of the sites (three or more of them), or a single link type across every site: the register names the share so the dependence is a recorded one. A failure mode shared by every site (one carrier, one device model, one class) is what the continuity and redundancy duties ask to be planned for, not avoided. - Financial entity site with no recovery objective
DORA is ticked and the line carries no recovery time objective. Articles 11 and 12 ask a financial entity (other than one on the simplified framework of Article 16) to hold response and recovery plans and backup and restoration procedures, with recovery time and recovery point objectives set for each function, wherever its ICT systems run; a branch, an ATM estate or an outsourcing site without one is a gap in the plan, not in the site. - Hardware questions unanswered
On the first paste no line answers the six questions the register puts to the vendor of the hardware at each site: attestation of firmware and boot, unattended update and rollback, remote wipe, local storage encryption, recovery without a technician, spares; each class adds one question of its own. The finding is the RFI page: the questions per site, grouped by class, ready to paste into the next rollout's request.
Do this for every site on your list
Paste the list and get this reading for every site at once, with the link, the exposure, the data held, the findings and the duty rows per regime. Eight sites free, no account.
Build my edge register