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.
Source-bounded topology
Documented topology, controls, and unknowns
Expected, documented, and observed configurations remain separate. Physical port capability is not treated as an active connection, and public-Internet reachability is shown only when a reviewed source says so.
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 or that the VPN used the public Internet. Older federal and state records separately document a Unity 3.4.0.0 wireline SFTP reference design, optional cellular hardware families, and a Michigan EVS 5.3.2.0 diagram that explicitly shows DS200 units and Regional Results connected through a wireless carrier and the Internet without proving current certification, activation, field use, or an election transmission.
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.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.
The exact EVS 6.4 test record documents Regional Results sending result files through a customer-dedicated VPN to Electionware EMS. The reviewed passage does not make the DS200 the VPN endpoint or say that the VPN traverses the public Internet.
Evidence classification only. It does not establish a live connection, current deployment, attack path, or security finding.
This is an exact-version VSTL test path. The DS200-to-Regional Results handoff medium, public-network transit, jurisdiction deployment, and election use are not established.
eac-evs-6400-scope@2026-07-19provv-evs-6400-test-report@2026-07-19Accessible topology indexSelect a node or connection without using the canvas.
The EAC scope states that Regional Results securely transmits encrypted unofficial results collection files.
The certified Regional Results description specifies a customer-dedicated network.
The reviewed exact-version passages do not make the DS200 itself the VPN endpoint or identify a direct scanner-to-network connection.
No addresses, credentials, VPN settings, keys, APNs, SIM data, carrier accounts, or site-specific routing information are collected or shown.
eac-evs-6400-scope@2026-07-19provv-evs-6400-test-report@2026-07-19The 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 3eac-evs-6400-scope@2026-07-19This 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 25provv-evs-6400-test-report@2026-07-19The diagram explicitly shows an Internet segment, but it belongs to a historical Michigan procurement response and does not establish EVS 6.4.0.0 certification, a current county topology, an installed modem, an active connection, or election use.
Michigan contract PDF page 101, contract page 62, Wireless Results NetworkThis 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 12multitech-universal-socket-guide@2026-07-20The 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 20multitech-universal-socket-guide@2026-07-20This 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 22multitech-universal-socket-guide@2026-07-20This 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 31multitech-universal-socket-guide@2026-07-20DS200-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.eac-evs-6400-scope@2026-07-19provv-evs-6400-test-report@2026-07-19Field 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.eac-evs-6400-scope@2026-07-19fl-evs-4500-v4-modem-report@2026-07-20provv-evs-5341-modem-hardware-table@2026-07-20