On-site edge box
- Camera connection
- Local processing and buffering
- Measurement of the chosen condition
- Secure evidence transfer
Security, Privacy & Trust
Know what runs where before a camera is connected.
Edgentik combines an on-site edge box with a secure application for evidence review, device health and reports. The table below separates what the product does today from the security and data decisions agreed with each customer before connection.
Data path
See the agreed data path before connection.
The pilot begins with one existing camera, secure on-site processing, reviewable findings and a connected operating record.
Pilot facts
Current product behavior and customer-specific decisions.
This is the buyer checklist used to turn a general security conversation into an approved security and data plan.
| Topic | Current product behavior | Confirmed before connection |
|---|---|---|
| Camera connection | Suitable existing RTSP camera views connect to the on-site edge box. | Selected feeds, credential handling, network route and approved operating schedule. |
| On-site processing | Local processing, buffering and measurement of the chosen condition run on the edge box. | Device location, allowed outbound endpoints, health access and recovery responsibilities. |
| Cloud application | Event evidence, case details and device health support review and reporting. | Exact evidence payload, expected volume, hosting region and customer retention requirement. |
| User access | Organization- and site-scoped roles limit who can review, administer and export. | Named users, permission profile, MFA requirement and customer approval path. |
| Evidence | Evidence stays attached to the case; review and export activity is auditable. | Preview and full-frame handling, export rights, retention, deletion and end-of-pilot handling. |
| Worker identity | No facial recognition, individual identification, per-worker history or worker scoring. | The chosen safety condition, area and reason for review are documented in the pilot scope. |
| Integrations | Approved customer systems can receive agreed notifications or data through integrations and APIs. | Every integration, recipient, acknowledgement and handoff included in the engagement. |
Responsibility split
Processing, review and safety authority stay distinct.
Edgentik review application
- Alert and reviewed-episode evidence
- Device health and setup status
- Ownership, comments and audit history
- Completed Scan reports
Customer authority
- Hazard assessment
- Control selection and approval
- Retention and access requirements
- Maintain, refine, escalate or close
Inspectable controls
Controls a buyer can verify in the product.
Scoped RBAC
Organization- and site-scoped roles constrain administrative, review and export actions.
TOTP MFA option
Cloud sign-in supports TOTP MFA, password hardening, lockouts and hardened sessions.
Audit-backed evidence
Evidence views, exports and operating actions remain tied to named accounts and site context.
Gated health access
Health and metrics remain behind the same access boundary unless broader access is explicitly enabled.
Visible setup and device health
Camera setup, device health and recovery status remain visible instead of being handled as undocumented field changes.
Security review package
Customer review can include the agreed data flow, access, runbook, recovery and evidence-handling record.
Decision boundary
Safety decision support—not automated judgment about people.
Edgentik measures
The chosen visible condition, camera accuracy, individual events, recurring patterns and results after the site acts.
The employer decides
Whether controls are adequate, what corrective action is appropriate and when follow-up is complete and what should happen next.
Edgentik does not determine
Regulatory compliance, root cause, fault, worker conduct or corrective-action effectiveness.
Qualified security review
Confirm the data and security requirements for the first camera.
The pilot scope can document camera access, evidence payload, users, hosting region, retention, exports and end-of-pilot data handling before connection.