Source-linked configuration dossier
ES&S EVS 6.4.0.0 / DS200
A source-linked pilot dossier for the DS200 within the EAC-certified EVS 6.4.0.0 configuration, with historical change records, separately scoped optional modem models and vulnerability reviews, and a labeled Washington deployment observation.
Federal certificate ESSEVS6400VVSG 1.0VSTL: Pro V&V, Inc.Editorial: published r8
Network configuration evidence
Documented paths, controls, and unknowns
Expected, documented, and observed configurations remain separate. Physical port capability is not treated as an active connection.
Safe public evidence boundaryReviewed 2026-07-21
For EVS 6.4.0.0, the EAC scope defines Regional Results as a separate application at a regional sending site, and Pro V&V tested transmission of DS200 result files through Regional Results over a VPN. The reviewed exact-version text does not establish that the DS200 itself was the VPN endpoint. Older federal and state records separately document a Unity 3.4.0.0 wireline SFTP reference design, a Michigan EVS 5.3.2.0 wireless-carrier and SFTP path, and optional DS200 cellular hardware families without proving EVS 6.4 certification, firmware, activation, or field use.
The module publishes roles, high-level paths, connection media when established, and evidence boundaries. It excludes IP addresses, credentials, VPN parameters, keys, APNs, SIM identifiers, carrier accounts, device identifiers, and jurisdiction routing details.4 sourced configuration views7 source imagesNo field-observed topology collected
expected layervstl test configurationdocumented partial
EVS 6.4.0.0 Regional Results test path
Pro V&V tested DS200 results transmitted by the separate Regional Results application through a VPN to the EMS. The source establishes the end-to-end result workflow but not a direct DS200 network session or the local handoff medium from the tabulator to the Regional Results client.
Topologyresults transmission service
Select a nodeHighlights its documented paths
DS200Regional Results client
Result-data handoff; local medium not established in the reviewed passage
Make DS200 result data available to Regional Results - not publicly establishedRegional Results clientCustomer-dedicated VPN path
Virtual private network over a customer-dedicated network
Transmit encrypted unofficial results collection files - confirmedCustomer-dedicated VPN pathElectionware EMS
Virtual private network
Deliver transmitted result files to the central EMS - confirmeddocumentedEncrypted unofficial result files
The EAC scope states that Regional Results securely transmits encrypted unofficial results collection files.
documentedCustomer-dedicated network
The certified Regional Results description specifies a customer-dedicated network.
not publicly establishedDirect DS200 network session
The reviewed exact-version passages do not make the DS200 itself the VPN endpoint or identify a direct scanner-to-network connection.
Operational details withheld
No addresses, credentials, VPN settings, keys, APNs, SIM data, carrier accounts, or site-specific routing information are collected or shown.
A successful VSTL system test is not evidence that a jurisdiction enabled Regional Results, used the same network design, or transmitted results in a particular election.
Source diagrams and pagesExpand any image; scope and caveats stay attached.
source topology diagramEVS 6.4.0.0 certified-system overview diagram
The system-level figure contains many EVS components and paths. It does not prove that every component or connection is present in a DS200 deployment.
EAC scope PDF page 4, document page 3source document pagePro V&V EVS 6.4.0.0 result-transmission accuracy-test statement
This is evidence of a laboratory test configuration and successful result transfer, not a field deployment or direct DS200 network-session record.
Pro V&V test-report PDF page 30, report page 25source topology diagramMichigan contract exhibit: historical DS200 wireless results network
The diagram belongs to a historical Michigan procurement response and does not establish EVS 6.4.0.0 certification, a current county topology, an installed modem, or election use.
Michigan contract PDF page 101, contract page 62, Wireless Results Networkmanufacturer reference pinoutMultiTech Universal Socket reference pinout
This is a generic product-family interface reference. The guide says not all modems include every pin; it is not a DS200 carrier-board pin map or proof that any interface is wired or enabled in a DS200.
Universal SocketModem Developer Guide PDF page 12manufacturer reference board drawingMultiTech generic SocketModem developer-board layout
The source labels third-party components as examples and describes a developer board for SocketModems generally. It is not a DS200 carrier-board drawing, teardown, port inventory, or placement record.
Universal SocketModem Developer Guide PDF page 20manufacturer reference block diagramMultiTech generic SocketModem developer-board block diagram
This developer-board diagram shows possible reference connections across the broader SocketModem platform. It does not establish which ports exist, are connected, or are enabled on a DS200 modem carrier board.
Universal SocketModem Developer Guide PDF page 22manufacturer reference installation pageMultiTech generic modem, antenna-lead, and SIM installation guidance
This generic procedure establishes product-family installation concepts only. It is not evidence that a DS200 contains a SIM holder, antenna lead, active SIM, or any particular SocketModem model.
Universal SocketModem Developer Guide PDF page 31Evidence gapsUnknowns stay explicit and source-bounded.
DS200-to-Regional Results handoff
The reviewed exact-version passages do not identify whether the local result handoff used removable media or another mechanism, and they do not establish the DS200 as the VPN endpoint.
The module leaves the local medium unresolved instead of drawing a direct network link.Field configuration and modem state
No dated jurisdiction network diagram, interface inspection, modem inventory, firmware reading, carrier activation record, or transmission log was collected for a particular DS200.
Optional and historical records must not be presented as field evidence.U.S. Election Assistance Commission: EVS 6.4.0.0 Certificate and Scope of ConformanceFlorida Department of State, Division of Elections: ES&S EVS Release 4.5.0.0 Version 4 Test Report Addendum (Revision 1)Pro V&V, Inc.; Minnesota Judicial Branch record mirrored by Democracy Docket: EVS 5.3.4.1 Test Report hardware-components table, court-filed Exhibit A