Measurement-data security
Protection applies to the payload itself, helping preserve confidentiality and integrity beyond the classic stable HTTPS scenario.
EnviroSense
EnviroSense Technology
EnviroSense technology is built around measurement-data security, predictable server operation and resilience in non-ideal transmission conditions. The system does not depend on a single communication channel or a single infrastructure model.
payload securityAES-256-CBCHMAC-SHA256GSM/LTELoRa
Architecture principles
Infrastructure independence
The system can run locally, on a VPS, in a private cloud or on-premise according to the customer’s policy.
Flexible transmission channels
The architecture supports WiFi, GSM/LTE, SMS, LoRa and installations where connectivity may be limited or unstable.
Backend scalability
The server layer can range from lightweight PHP to native C++ applications with relational, cache or time-series databases.
Security mechanisms
AES-256-CBC
Payload encryption protects the content of measurement data from unauthorised reading.
HMAC-SHA256
Integrity signing helps detect data manipulation and reject unauthentic payloads.
Device validation
The server can validate device identifiers, allowed transmission sources and required fields.
Event logging
Ingestion events, transmission errors and alarm situations can be stored in system logs.
Data control
The self-hosted model keeps measurement data in infrastructure indicated by the customer.
Access layers
The architecture can separate ingestion, public previews, operator views and administrative back office.
Transmission resilient to real conditions
Environmental installations often operate in imperfect networks. EnviroSense separates data protection from the transport channel, making field scenarios easier to handle.
EnviroSense model
Payload protection and device control
Data protected before sendingThe payload can be secured on the device before it enters the selected communication channel.
Different transmission mediaThe same data model can be used across WiFi, GSM/LTE, SMS or LoRa deployments.
Unstable-link toleranceThe system can accept delayed data and organise records by measurement time and device identifier.
Stronger backend controlThe administrator controls retention, backup, logs, alerts and integrations with other systems.
Transport-only model
Limitations in some field deployments
High dependency on stable IPSystems relying only on the transport layer require predictable connectivity and stable sessions.
Lower channel flexibilityNon-IP channels or emergency transmission scenarios are harder to support without payload protection.
More reliance on intermediate infrastructureSecurity may depend on operators, gateways, proxies or access-point configuration.
Harder integrity controlIf protection does not include the payload itself, authenticity is harder to assess unambiguously.