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.

Source version: Version 1.0 · November 1, 2026
Publisher: The Museum Protocol · EAM LLC

Download Markdown Guide

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

ConceptResearch meaningImportant limit
ProvenanceDocumented history of an object's origin, attribution, ownership, and contextA recent handoff cannot fill gaps in historical ownership
CustodyResponsibility for possession, handling, or safeguarding over a defined periodCustody does not establish lawful ownership
Digital integrityEvidence that bytes match an identified baselineMatching hashes do not prove the original information was true
AuthorizationRecorded permission for an action within a defined scopePermission does not prove the action occurred
Air gapSeparation between specified systems with no physical connection and no automated logical transfer across that interfaceA label, screen image, or disconnected cable is insufficient evidence
Zero Trust ArchitectureAn access-oriented architecture requiring explicit decisions rather than presumed trustDistinct 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

RoleResponsibility
Museum sponsorApproves scope, priorities, resources, and residual risk
Registrar or collections leadDefines identifiers, movement authority, custody, and reconciliation
ConservatorDefines condition checks and safe handling restrictions
System ownerMaintains inventory, configurations, accounts, and restoration arrangements
Authorized testerExecutes the approved protocol and preserves observations
Evidence custodianControls originals, manifests, access, and transfer receipts
Independent reviewerChecks findings against evidence and challenges unsupported conclusions
MBISO coordinatorConnects 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

  1. Identify the object using its museum identifier and an appropriate description.
  2. Record its current location and custodian. Keep exact storage locations out of public reports.
  3. Obtain movement approval and define purpose, destination, timeframe, and handling requirements.
  4. Check condition and prepare packing with responsible collections professionals.
  5. Record release, carrier or handler, and each intermediate handoff.
  6. Confirm arrival, condition, receipt, and discrepancies.
  7. Update the authoritative location record promptly and reconcile temporary paperwork.
  8. Retain corrections with author, time, reason, and prior value.

Proposed custody event template

FieldEntry guidance
Event ID and object IDStable unique identifiers; never recycle an event ID
Event type and purposeRelease, transport, receipt, inspection, return, or exception
From and to locationsControlled location identifiers
AuthorizationApprover, approval reference, scope, and approval time
Released by and received byIdentified actors and acknowledgment method
Event time and entry timeInclude timezone; distinguish observed time from later entry
Condition and packingReferences to reports, images, and seals where applicable
Related digital packagePackage ID and manifest reference
Exception or uncertaintyWhat is unknown, who was informed, and current status
ReviewReviewer, 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.

TestMethodEvidence and decision criterion
Boundary inventoryInspect configuration, ports, adapters, radios, docks, and management interfacesInventory and diagram complete; unexplained paths mean not verified
Physical inspectionInspect actual equipment and cable endpointsRecord connections and photos when permitted
Interface inspectionReview OS and firmware settings and device listingsReconcile all discovered interfaces with inventory
Communication observationObserve authorized local interfaces and controlled test networkUnexpected traffic investigated; silence alone cannot prove every path absent
Reboot persistenceRestart and repeat relevant checksNo unapproved interface or service re-enabled
Controlled file transferExecute media protocol with harmless sample dataSource and destination hashes agree; receipts retained
RestorationRestore approved data to separate test equipmentFiles, 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

  1. Approve the transfer request and classify information.
  2. Prepare minimum required files and create a manifest.
  3. Inspect media and files using approved tools.
  4. Record media ID, operator, source, destination, inspection result, and release approval.
  5. Transfer through the documented manual process.
  6. Verify destination hashes and record acceptance or rejection.
  7. 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.

  1. Collections Trust. Location and movement control; Spectrum standard and suggested procedure. Spectrum and suggested procedure.
  2. NIST CSRC glossary. Air gap; definition attributed to CNSSI 4009-2022.
  3. NIST SP 800-86. Guide to Integrating Forensic Techniques into Incident Response. August 2006.
  4. NIST SP 800-88 Revision 2. Guidelines for Media Sanitization. September 2025.