Skip to content

SWEAR System Architecture

Purpose

This page explains how SWEAR integrates with Milestone XProtect to create and validate video authenticity evidence.

Scope

  • Includes: Core components, high-level certification, and validation behavior.
  • Does not include: Installation steps, troubleshooting workflows, or licensing procedures.
  • Applies to: Milestone XProtect VMS environments using SWEAR certification and validation components.

Quick definitions

Term Meaning
SWEAR Certification System Server-side SWEAR component that creates cryptographic hashes during recording and writes authenticity evidence to a blockchain-backed ledger.
SWEAR Validation System Client-side SWEAR component that recalculates hashes and compares them to original ledger-backed records.
Hash A deterministic cryptographic fingerprint of content used to detect changes.
Validation result Outcome of comparing recalculated hashes to recorded authenticity evidence.

How it works

Components

  • Milestone Recording Server: Captures and stores video streams.
  • SWEAR Certification System (server): Generates hashes as assets are written and anchors authenticity evidence in a blockchain-backed ledger.
  • SWEAR Validation System (client): Recomputes hashes for selected video and checks them against recorded evidence.
  • Milestone XProtect Client tools: Provide operator workflows to review and validate protected footage.

Data flow

  1. Video is recorded by Milestone XProtect.
  2. SWEAR Certification System computes cryptographic hashes as content is saved.
  3. Hash evidence is preserved in a blockchain-backed ledger for tamper-evident reference.
  4. During review, SWEAR Validation System recomputes hashes for the selected asset.
  5. Validation compares current hashes with original evidence and returns a match/non-match outcome.

States / lifecycle

  • Recording Devices: Video is captured.
  • Recording Servers: Video is stored.
  • Certification: Hash evidence is generated and preserved.
  • Validation: Evidence is checked against current content.
  • Result: Authenticity status is presented to the user.

Permissions / roles

  • Users need the required XProtect permissions to view content and access SWEAR validation features.
  • Administrative setup permissions are required for initial SWEAR configuration.

Key behaviors and rules

  • SWEAR adds authenticity verification signals without replacing Milestone recording, playback, or storage workflows.
  • Validation depends on comparing current content fingerprints to original certification evidence.
  • Any mismatch indicates the content no longer matches the originally certified state.

Configuration and defaults (if applicable)

Setting Default Notes

Limits and constraints (if applicable)

  • Rate limits: Not documented in this reference.
  • Size limits: Not documented in this reference.
  • Timeouts/TTLs: Not documented in this reference.
  • Compatibility: This document describes Milestone XProtect integrations.

Overview

Figure 1: System Architecture Overview

Common questions

  • Q: Does SWEAR replace Milestone video storage or playback?
    A: No. Milestone continues to manage recording and playback. SWEAR adds authenticity certification and validation.
  • Q: What does validation compare?
    A: Validation compares newly computed hashes for the selected asset to the original certification evidence.

Change log

  • 2026-02-17 — Completed front matter and replaced template placeholders with production-ready architecture reference content.