Privacy & security
Everything we’ve written.
Newest first. Most pieces take 4 to 6 minutes.
Where did this record go? Tracing a record across systems
When an auditor, a resident or a records request asks what happened to one record, integrations are often a blind spot. How to trace a record by ID across every flow, without keeping its contents.
Read article →Court and citation data in integrations: handle with care
Citations, court dates and case records are useful to share, and easy to share wrongly. Cautions for integrations that touch them: sealed records, juveniles, identifiers, open data and what to log.
Read article →Running integrations on an air-gapped network
Some agencies keep key systems on networks with no internet access. Integration still has to happen there. What to look for in a platform that runs fully inside a closed network.
Read article →Using AI to draft integration flows, without giving it your records
AI can draft and explain integration flows from settings and field names alone. Where the line sits between helpful and risky, the guardrails to require, and the questions your security team will ask.
Read article →Why your integrations shouldn't keep a copy of resident data
Most integration tools quietly keep a copy of every record they move. For a city, that copy is a liability. Here is what pass-through integration means and why it matters.
Read article →Reaching on-premises systems: an outbound relay or a VPN?
Cloud integrations often need to reach a finance database or file server inside the city network. Comparing a site-to-site VPN, opened firewall ports and an outbound-only relay, with the questions to ask.
Read article →CJIS basics for integrations: what city IT should know
When an integration touches criminal justice information, the CJIS Security Policy applies. A plain-language overview of what it asks of integrations, and the questions to put to any vendor.
Read article →SSO, SCIM and two-step sign-in for city staff: a practical guide
Single sign-on, automatic account removal and two-step sign-in, explained for city IT. What each one does, how they fit together, and what to require from any system that touches resident data.
Read article →Public records requests and integration logs: what should be in them
Integration logs can quietly become records you have to search, review and produce. What tends to end up in them, how to keep them lean, and how to respond when a request names them.
Read article →