IaaS, PaaS, SaaS: cloud service models for public agencies
What each cloud service model means, who is responsible for what, and how agencies typically use them.
Articles
Every reference article on hqt.org in Technology, written for agency procurement, technology, and program staff.
What each cloud service model means, who is responsible for what, and how agencies typically use them.
What the two cloud security authorization programs are, how they differ, and what an authorization actually tells an agency.
The principles behind Zero Trust, the maturity model, and a realistic sequence for a small security team.
How the framework is structured, why agencies adopt it, and how to use it without drowning in paperwork.
What the policy covers, who it binds, and the areas that most often cause compliance findings.
The stages of a secure delivery pipeline and the evidence it produces for auditors.
The main approaches to modernizing an old application, and how to choose among them.
Principles for designing interfaces between agency systems that will be maintained for years.
Where low-code tools help agencies, where they cause trouble, and the governance that keeps them useful.
The main data platform architectures, what each is good for, and a sensible default for a public agency.
The role of geographic information systems across agency functions and the components of a modern GIS.
What NG911 changes about how emergency calls are routed and handled, and what agencies must prepare.
The technical standard behind accessibility requirements, what it covers, and how agencies achieve and maintain conformance.
How control systems differ from IT, the risks they face, and the practical controls that protect them.
Directory services, single sign-on, multi-factor authentication, and lifecycle management as the foundation of agency security.
What a backup strategy must include to survive ransomware, and how to know it works before it is needed.
How agencies know their online services are working, and what to measure.
The risks in the components software is built from, and the practices that manage them.
What containers are, when orchestration is worth it, and a right-sized approach for public agencies.
Why flat networks are dangerous, how to divide them, and how to do it without breaking operations.
Why one-time codes are no longer enough, what passkeys and security keys change, and how to roll them out.
Quantum computers will eventually break today's public-key encryption. The preparation is inventory and agility, not panic.
How agencies collect and act on data from sensors, meters, vehicles, and signals as it happens.
How agencies can run online services that scale for deadlines and cost little when idle, without managing servers.
What a digital twin is in practical terms, and where the concept delivers value for water, power, and facilities.
How a shared, paved road for development teams speeds delivery and keeps security consistent across applications.
Using imagery from vehicles, drones, and fixed cameras to find pavement defects, sign damage, and asset conditions at scale.
The components that have replaced nightly exports and spreadsheets, and how they fit together for a public agency.
What SPF, DKIM, and DMARC records do, how alignment works, and how to reach enforcement without blocking legitimate agency mail.
What EDR adds beyond antivirus, and how agencies decide whether to watch the alerts in house or buy managed detection.
A practical order for onboarding log sources into a SIEM, how to set retention periods, and why ingestion volume drives cost
How encryption in transit, at rest, and at the field level differ, who holds the keys, and what to require of vendors.
How CIS Benchmarks and DISA STIGs give an agency a defensible hardening standard, and how to handle levels, exceptions, and drift
How agencies control and log access to equipment spaces, manage power and water risk, and document media disposal for assessors.
How agencies keep an accurate software entitlement record, reconcile it against deployment, and prepare for a vendor license audit.
What it takes to give residents one account across permitting, utility billing, and court systems, and the tradeoffs of each approach.
How agencies take card and ACH payments online: merchant accounts, gateways, PCI scope and SAQ choice, fee models, and reconciliation.
How agency communications and IT staff compare hosted government platforms, commercial products, and open source CMS options during a redesign.
A practical guide for agency IT leaders on naming technical debt, ranking it by risk, and funding remediation in the budget
What changes when a field application must work without a signal: local storage, selective sync, conflict handling, and device security.
How agencies build one authoritative record for a resident, parcel, business, or asset across systems that disagree
How local governments decide who assigns addresses, keep points, parcels, and centerlines aligned, and publish one list other systems can trust
How agency GIS teams document coordinate systems, schemas, and metadata so shared layers can actually be trusted
How agencies separate a technical data catalog from a statutory data inventory, what a minimum entry in each contains, and who keeps them current.
A practical way to define, profile, and automatically test data quality so the numbers on an agency dashboard can be trusted.
Compares the realistic routes for getting agency data out of a hosted vendor system, and the access terms to settle before go-live.
How agency IT teams set up a service catalog, intake and triage, support tiers, priority rules, and the metrics worth reporting.
How to size an IT change process for a public agency: change types, approvers, review boards, maintenance windows, and freeze periods.
How agencies set refresh intervals by device role, fund replacement predictably, and retire equipment on schedule.
How to inventory network gear, rank switch and wireless replacements by risk, and plan for PoE, cabling, and closet limits.
How to restructure fund, department, program, project, and object segments before an ERP conversion and document a crosswalk that survives audit.
How budget preparation software handles position budgeting, scenarios, decision packages, and the adopted budget book.
How agencies run one receipting system across counters, balance drawers, tie deposits to the bank, and post revenue to the ledger.
How multi-year CIP budgets, multiple funding sources, change orders, retention, and construction in progress fit together in one system.
What an applicant tracking system must do under merit system rules, from requisition approval through eligible lists, certification, and audit trails.
How agencies run civil service exams at scale: item bank security, proctoring options, accommodations, scoring, and eligible lists.
What to look for in a learning management system that has to prove training compliance to auditors, not just deliver courses.
How agencies keep an authoritative record of staff licenses and certifications, verify them with issuers, and alert before they expire.
How shift scheduling systems for police, fire, and dispatch handle minimum staffing, overtime callback lists, and audit trails.
How position control links adopted budget authority to filled and vacant seats, and how to reconcile HR and finance headcount monthly.
How agencies extend HR self-service to field and shift staff: kiosk and mobile access, phishing-resistant login, and delegated approvals.
How building automation systems land on agency networks, and how facilities and IT should divide patching, backups, accounts, and alarm routing.
How an energy management information system combines utility bills, interval meter data, and weather to manage agency building energy costs.
How to scope a building access control replacement: credentials, readers, panels, data migration, and a phased cutover.
What an IWMS or CAFM must hold to be trusted for floor plans, occupancy, and lease records, and what GASB 87 reporting demands.
How to build a 311 request type catalog: sizing the list, routing each type to an owner and queue, and setting response targets crews can meet.
How Open311 GeoReport v2 works, what its endpoints do, and how to require it in a service request system solicitation.
How to connect a 311 request system to public works work orders: system of record, asset matching, status mapping, and closure notifications.
How a constituent relationship system differs from a 311 service request tool, and how to scope one without starting an enterprise data program.
How to design a resident notification preference center: topics, channels, consent records, quiet hours, and cross-system opt-out sync.
What an agency call center needs beyond a phone system: routing, callback, IVR design, language access, recording, and peak sizing.
How to configure appointment scheduling for permit counters, clerk windows, clinics and inspections without simply hiding the wait.
How HL7 v2, C-CDA, and FHIR fit together, and what to name in a solicitation so interface quotes are comparable.
How local agencies connect case management tools to state eligibility systems: access agreements, matching rules, and audit limits.
How to build a public zoning lookup map that gives residents a clear, trustworthy answer about what they can build on a parcel.
How agencies run low-cost air sensor networks: siting, calibration and drift, data gaps, and publishing readings residents can act on.
Moving water quality results from field sampling and contract lab EDDs into a validated database, dashboard, and state report.
How agencies specify stream and rain gauge telemetry that survives the storm: sensors, backhaul, power, alarms, and upkeep.
How agencies can forecast storage, compute, and license growth on a budget cycle and size systems for predictable seasonal peaks.
A practical guide to assigning recovery time and recovery point objectives to agency systems and using them to drive backup, replication, and contract terms.
How agencies weigh separation distance, hosting options, and network paths when choosing a disaster recovery site.
The routine database maintenance a two-person agency IT shop still owes a vendor system, and how to staff it.
How agencies can use deployment rings, realistic maintenance windows, and documented exceptions to patch 24/7 systems.
How to scope, populate, and maintain a configuration management database that a small government IT team can keep accurate.
How agencies build and maintain an application dependency map to speed outage triage and avoid cutover surprises.
How agency IT teams can cut monitoring noise, tune alert rules, and make sure real outages still get noticed.
A practical monitoring baseline for small government networks: which signals to watch, what each one tells you, and how to size a tool.
How small government IT teams can build an on-call rotation that works: schedules, escalation tiers, hand-off notes, standby pay, and budget.
How agencies can inventory every TLS certificate and domain they depend on, with owners, expiry dates, funding, and automation.
How agencies move from bench imaging to zero-touch enrollment for laptops, patrol tablets, and rugged field devices.
How agency IT teams can inventory service accounts, assign named owners, and rotate credentials without breaking scheduled jobs.
What privileged access management tools do, which pieces a small agency needs first, and how to write PAM requirements.
A practical plan for taking local administrator rights off agency workstations without stranding staff who legitimately need to install things.
How the Active Directory tier model works, and a practical sequence a small agency can follow to protect domain admin credentials.
How agencies can inventory certificates, assign owners, and automate renewal so expirations stop taking public systems offline.
How state and local agencies evaluate WAF and DDoS protection for public websites, from monitor mode to contract terms.
How protective DNS blocks malicious domain lookups, where enforcement gaps appear, and what to ask before an agency buys it.
How state and local agencies can find internet-facing systems nobody remembers owning, and keep that inventory current each quarter.
How to security test an agency API before it goes public, from authorization flaws to contract terms and go-live evidence.
How to document the path from a source system field to a published figure, and what lineage details to record by hand.
How agencies can find every report, extract, dashboard, and submission that depends on a field before changing it.
How agencies define, own, version, and distribute code lists so department, fund, case, and status values stay consistent across systems.
How to measure geocoding quality using match rates, match types, and tie handling, and what to do with records that fail to match.
How agencies set retention windows, downsample sensor and meter readings into rollups, and choose a time series store.
How agencies separate certified dashboards staff may cite from exploratory ones using owners, definitions, reviews, and retirement.
How agencies can automate row count, null, duplicate, referential, range, and freshness checks before a dashboard refresh publishes.
A repeatable method for reconciling counts that disagree between a source system, a data warehouse, and a published report.
Why copying production records into test environments creates risk, and how to build synthetic and masked datasets that still catch real defects.
How agencies assign page ownership, set content and accessibility standards, and run recurring reviews that retire stale pages.
Get in touch
Talk with an HQT engineer. We respond to agency, corporate, and partner inquiries promptly.