For the reviewer, not the buyer
Everything IT asks, answered before the meeting.
A plant champion should not have to assemble this. It is the same seven questions every time — what does it talk to, with what credentials, what can it reach, and what happens when the network drops. Written to be attached to a ticket.
Network boundary
In local deployments, inference runs on the device. Configured cloud or hybrid routes can send inputs to the selected provider. Review the execution route, export policy and any preprocessing or anonymization settings as part of the network boundary.
The control plane handles fleet management, model distribution, dataset storage and long-term evidence retention. Field telemetry crosses a bounded companion MCU; control authority does not move.
Egress
- Direction
- Outbound only. The device initiates; nothing inbound is required to reach it.
- Destinations
- Confirm the endpoint and port allowlist for the selected control plane, model route and integrations before deployment.
- Protocol
- HTTPS for hosted API connections. Verify TLS requirements and certificate handling for the selected runtime during the security review.
- Proxy support
- Confirm support and configuration for your selected runtime before relying on an outbound proxy.
- What is sent
- Verdicts, structured events and heartbeat. Frames only where the operator has configured it.
Credentials
- Operators
- Cognito OAuth 2.0 with PKCE. Invitation only; tenant-scoped.
- Devices
- Device identity and device secret, issued at enrolment.
- Agent tokens
- Expiring, tenant-scoped, read-only against the MCP service.
- Rotation
- Agree credential expiry, rotation and revocation procedures for operators, devices and integrations during onboarding.
- Storage on device
- Review credential storage on the selected host. Hardware-backed storage is not assumed for every supported device.
Updates and rollback
- Pull-based. The device asks; nothing is pushed to it
- Artifacts are private and checksum-verified before activation
- Activation is atomic into a versioned slot
- A failed health check restores the previous slot automatically
- Every candidate passes admission before it can install
Application rollback does not replace a PLC safety function, an OS image rollback or machine validation.
What agents cannot do
- Reach anything beyond the grant recorded for that device
- Obtain a shell, or run an arbitrary process
- Reach a network endpoint that was not declared
- Install without a passing verdict against the named device
- Act as a safety function — rated control stays authoritative
Current agent surfaces do not directly write PLC values. Any downstream control integration requires separate review, explicit scope and an audit trail.
Retention
- Verdicts and events
- Agree the retention period, export and deletion requirements for the deployment before production.
- Frames
- The hosted demo does not store uploaded frames. Production frame capture and retention depend on the configured workflow and policy.
- Region
- Stated per deployment. The default hosted demo route uses AWS us-east-1; the active provider and region are disclosed in each result.
- Tenant isolation
- Records are tenant-scoped; no cross-tenant read path exists.
On network loss
- Local inference can continue without a cloud link; cloud-dependent workflows require connectivity
- Event buffering depends on the selected runtime and configured queue
- Queued events can sync when the link returns, subject to queue limits
- Confirm queue capacity and overflow handling for the selected runtime before commissioning
- No agent gains reach it did not already hold while offline
Frameworks this produces evidence for
NIST SP 800-82 and CSF 2.0, IEC 62443, the EU Cyber Resilience Act, FDA 21 CFR Part 11, OSHA 29 CFR 1910 documentation, and SOC 2 change-management controls.
Support is not certification. Indagate holds no certification against any of these frameworks and none is implied. These are the obligations the system is designed to produce evidence for; conformity remains the operator’s assessment, made with your own auditors against your own deployment.
Send this to your reviewer.
If a question is missing, tell us which one and we will add it. This page exists so the security meeting happens once.