Prynt Gate docs

Example: GPS trackers and an alarm receiver

Two public raw-TCP services where a device is trusted only by the ID it sends: a tracking platform on Traccar and an alarm receiving center on SIA DC-09.

The problem

  • A tracker identifies itself with its IMEI only. Whoever knows an IMEI can connect as that vehicle and send positions or alarms.
  • Many receivers answer differently to a known and an unknown ID, so IDs can be enumerated.
  • An alarm panel reports with an account number; a spoofed heartbeat can keep a cut-off panel looking alive.

1. GPS: Traccar

Install the agent on the Traccar host with the traccar parser. A line such as

2026-11-15 18:02:11  WARN: Unknown device - 356307042441013 (203.0.113.7)

becomes

{"port": 5027, "protocol": "teltonika", "srcIp": "203.0.113.7",
 "claimedIdentity": {"type": "imei", "value": "356307042441013"},
 "outcome": "unknown_id", "metadata": {"parser": "traccar"}}
  • Six unknown IMEIs from one source within 10 minutes → enumeration → the source is blocked for an hour.
  • A known IMEI connecting from a second network while the device is still online → concurrentSources → flag and alert: one of them is a clone.
  • An IMEI that always came through one mobile carrier appears from a hosting provider → torOrHosting and newAsn.

2. Alarms: SIA DC-09

Have the receiver log one line per frame (account, token, result) and enable the dc09 parser, or send events directly:

{"port": 6543, "protocol": "dc09", "transport": "tcp", "srcIp": "198.51.100.40",
 "claimedIdentity": {"type": "panel_account", "value": "L0001#1234"},
 "outcome": "auth_ok", "metadata": {"token": "SIA-DCS", "seq": "0042"}}
  • Gate learns each account's usual network. A report from a new country or a datacenter is flagged.
  • Frames for accounts that do not exist (unknown_id) count toward enumeration, like unknown IMEIs.
  • Mark a critical panel as watch in Gate → Identities to get an alert on every change of network.

3. Rules for this setup

{"name": "Connection from a datacenter", "field": "asnType", "op": "eq", "value": "hosting", "action": "block", "priority": 10}
{"name": "Stricter enumeration", "field": "unknownIdsFromSource", "op": "gte", "value": "3", "action": "block", "priority": 20}
{"name": "Alarm panel abroad", "field": "newCountry", "op": "eq", "value": "true", "action": "flag", "priority": 30}

Gate detects and blocks at the network; it does not replace device authentication. Where the protocol allows it (encrypted DC-09, per-device keys), turn it on as well.

Updated 2026-11-15 · API reference