The Museum Protocol · EAM LLC
Museum Chain-of-Custody and Air-Gap Security Research Guide
An original research framework for museum custody records, digital integrity, air-gap verification, controlled media transfers, and recovery exercises.
Purpose and audience
This guide helps collections staff, conservators, museum leadership, IT teams, and security researchers investigate how physical custody and digital security can support each other. It provides an original research protocol, proposed record templates, and practical acceptance criteria. It does not certify a system, determine title to an object, or establish compliance with a court order.
The central question is: can an independent reviewer reconstruct who was authorized to act, what happened, where the object or data went, and which evidence supports that account?
1. Key distinctions
| Concept | Research meaning | Important limit |
|---|---|---|
| Provenance | Documented history of an object's origin, attribution, ownership, and context | A recent handoff cannot fill gaps in historical ownership |
| Custody | Responsibility for possession, handling, or safeguarding over a defined period | Custody does not establish lawful ownership |
| Digital integrity | Evidence that bytes match an identified baseline | Matching hashes do not prove the original information was true |
| Authorization | Recorded permission for an action within a defined scope | Permission does not prove the action occurred |
| Air gap | Separation between specified systems with no physical connection and no automated logical transfer across that interface | A label, screen image, or disconnected cable is insufficient evidence |
| Zero Trust Architecture | An access-oriented architecture requiring explicit decisions rather than presumed trust | Distinct from an air gap; cannot substitute for a missing custody record |
Collections Trust treats location and movement control as maintaining current object locations and movement history. Its suggested procedure includes authorization, condition checks, handling requirements, and receipt of custody [1]. Use that source with the applicable Spectrum licence; the templates below are original research proposals.
2. Define the research boundary
Before testing, document the research sponsor, permissions, locations, dates, systems, and participants. Use fictional collection records in public demonstrations. Specify whether the study concerns a physical object, a digital surrogate, a removable medium, an isolated workstation, or their relationship.
Write a bounded claim such as: “During the recorded test interval, workstation LAB-01 had no identified automated communication path to network NET-01 under the inspected configuration.” Avoid “unhackable,” “permanently isolated,” or “proves provenance.”
Research questions include whether a reviewer can follow an object's approved movement; link a digital record without obscuring changes; identify paths across an isolation boundary; transfer a file through a controlled process; and recover records after disruption.
3. Assign responsibilities
| Role | Responsibility |
|---|---|
| Museum sponsor | Approves scope, priorities, resources, and residual risk |
| Registrar or collections lead | Defines identifiers, movement authority, custody, and reconciliation |
| Conservator | Defines condition checks and safe handling restrictions |
| System owner | Maintains inventory, configurations, accounts, and restoration arrangements |
| Authorized tester | Executes the approved protocol and preserves observations |
| Evidence custodian | Controls originals, manifests, access, and transfer receipts |
| Independent reviewer | Checks findings against evidence and challenges unsupported conclusions |
| MBISO coordinator | Connects responsibilities, actions, reporting, and educational interpretation |
Smaller teams may combine roles. Record that concentration of authority and add a second-person review for consequential movements or transfers where practical. An AI assistant may summarize approved records; it must not silently authorize movement, alter originals, or supply missing facts.
4. Physical custody workflow
- Identify the object using its museum identifier and an appropriate description.
- Record its current location and custodian. Keep exact storage locations out of public reports.
- Obtain movement approval and define purpose, destination, timeframe, and handling requirements.
- Check condition and prepare packing with responsible collections professionals.
- Record release, carrier or handler, and each intermediate handoff.
- Confirm arrival, condition, receipt, and discrepancies.
- Update the authoritative location record promptly and reconcile temporary paperwork.
- Retain corrections with author, time, reason, and prior value.
Proposed custody event template
| Field | Entry guidance |
|---|---|
| Event ID and object ID | Stable unique identifiers; never recycle an event ID |
| Event type and purpose | Release, transport, receipt, inspection, return, or exception |
| From and to locations | Controlled location identifiers |
| Authorization | Approver, approval reference, scope, and approval time |
| Released by and received by | Identified actors and acknowledgment method |
| Event time and entry time | Include timezone; distinguish observed time from later entry |
| Condition and packing | References to reports, images, and seals where applicable |
| Related digital package | Package ID and manifest reference |
| Exception or uncertainty | What is unknown, who was informed, and current status |
| Review | Reviewer, review date, and correction references |
5. Digital evidence and integrity
For each export, photograph set, log collection, or report, assign a package ID. Preserve original collected bytes and analyze working copies. Create a manifest with relative filename, byte size, hash algorithm and value, collection source, collector, method, collection time with timezone, and tool/version. Use a modern algorithm such as SHA-256 under approved policy.
Store the manifest in a controlled repository with access records and version history. A hash saved next to a file on the same writable drive can be changed along with the file. At every transfer, verify against the accepted manifest and record the result. For a mismatch, preserve both versions and investigate. An ordinary application event log should be described as an activity record unless stronger preservation and independent verification support a stronger claim.
6. Air gap threat model
Identify what needs protection, from whom, and against which plausible paths. Consider accidental reconnection, compromised transfer media, maintenance access, malicious peripherals, credential misuse, physical access, and loss of records. Inventory host, operating system, storage, Ethernet, Wi-Fi, Bluetooth, cellular radios, USB adapters, docks, network-capable peripherals, out-of-band management, and power arrangements.
For HPAOC2016 demonstrations, note that the LV290AA is a wireless peripheral system. Examine its receiver and radio behavior. A peripheral radio is not automatically an internet connection, but it is relevant to claims of complete radio isolation. Preserve the unopened LV290AA#ABA box and use separate loose peripherals and test equipment.
7. Verification protocol
Use institution-approved test equipment and methods. Do not probe third-party systems or reconnect production equipment merely to prove a point.
| Test | Method | Evidence and decision criterion |
|---|---|---|
| Boundary inventory | Inspect configuration, ports, adapters, radios, docks, and management interfaces | Inventory and diagram complete; unexplained paths mean not verified |
| Physical inspection | Inspect actual equipment and cable endpoints | Record connections and photos when permitted |
| Interface inspection | Review OS and firmware settings and device listings | Reconcile all discovered interfaces with inventory |
| Communication observation | Observe authorized local interfaces and controlled test network | Unexpected traffic investigated; silence alone cannot prove every path absent |
| Reboot persistence | Restart and repeat relevant checks | No unapproved interface or service re-enabled |
| Controlled file transfer | Execute media protocol with harmless sample data | Source and destination hashes agree; receipts retained |
| Restoration | Restore approved data to separate test equipment | Files, access, dependencies, and custody links reconcile |
Use four outcomes: pass for the stated criterion; fail; inconclusive; not tested. Report individual results and unresolved paths rather than collapsing the study into a misleading overall score.
8. Controlled removable media transfer
- Approve the transfer request and classify information.
- Prepare minimum required files and create a manifest.
- Inspect media and files using approved tools.
- Record media ID, operator, source, destination, inspection result, and release approval.
- Transfer through the documented manual process.
- Verify destination hashes and record acceptance or rejection.
- Retain receipts and handle media under a defined policy.
Do not sanitize media subject to an incident investigation or preservation hold. Deleting a file is not equivalent to verified sanitization.
9. Recovery and discrepancies
Define who can declare an incident, pause a movement, approve restoration, and authorize return to service. If a custody receipt is missing, mark the gap and preserve contemporaneous records. If an unexpected connection appears, preserve relevant configuration and logs using approved response procedures.
Practice restoring a collections-record export on separate equipment. Check integrity, readability, permissions, dependencies, identifiers, location history, and discrepancies. A successful backup job is not a successful restoration test.
10. Research scenarios
Exhibition handoff
A fictional object moves from storage to Gallery A and a receiving acknowledgment is absent. Success means visible uncertainty and an accountable resolution.
Maintenance reconnection
A demonstration workstation is serviced using a network-capable dock. Participants record the changed boundary and repeat checks.
Altered digital package
A harmless test copy differs from its manifest. Participants preserve both copies, record rejection, and trace transfer records.
Lost online service
A fictional ticketing service is unavailable while local collection records remain accessible. Participants prioritize communications and restoration.
11. HPAOC2016 research application
The Museum Protocol may use HPAOC2016 as a conceptual installation for discussing human action and boundaries. Evaluate artwork, software, physical actuator, and governance workflow separately. Do not infer completed actuation, tamper resistance, identity assurance, or isolation from an AOC monitor and HP peripherals. PatentSplit remains a proposed architecture unless separately demonstrated and verified.
Keep HPAOC2016's Air-Gap focus distinct from HPAOC2022's Zero Trust Architecture focus. QuantyGRC remains Governance, Risk, and Compliance.
12. Research report and release checklist
Publish a report with objective, scope, authorization, system diagram, methods, results, exceptions, limitations, corrective actions, reviewer, and retest triggers. Remove precise storage locations, credentials, personal information, and sensitive network detail from public copies.
Before release, confirm every consequential statement is supported, every demonstration is labelled, vendor results are attributed, and fictional examples are unmistakable. Do not imply a federal case requirement, court finding, institutional endorsement, or legal ownership determination without relevant documentation.
References
Sources consulted November 1, 2026. Original procedures and templates in this guide are proposed research methods; they are not official NIST or Collections Trust forms.
- Collections Trust. Location and movement control; Spectrum standard and suggested procedure. Spectrum and suggested procedure.
- NIST CSRC glossary. Air gap; definition attributed to CNSSI 4009-2022.
- NIST SP 800-86. Guide to Integrating Forensic Techniques into Incident Response. August 2006.
- NIST SP 800-88 Revision 2. Guidelines for Media Sanitization. September 2025.