Encrypted data connection
Supported Internet data connections use TLS. Device identification, key management and access method are adapted to the specific installation environment.
Safety and operation, with specific liability limits.
Encrypted data path, controlled access, backup and availability — documented for the given project.
Security already during the design of the architecture
OrigSmart connects physical assets, measurement data and business processes. Security requirements are therefore not treated as an afterthought, but as part of the assessment and system planning.
Roles and logging
Access is planned according to roles, and important system and business events can be traced back.
Separate data path
Field protocols, integration and business authorizations are linked with clear boundaries of responsibility.
Operating model
The hosting location, backup schedule, availability goal, update responsibility and incident management are recorded per project, in the offer and in the technical specification. Cloud, client-side and hybrid design can be designed; only the accepted service agreement means a specific SLA.
What do we clarify at the first technical meeting?
- Where is the data generated and stored?
- Which connections can be opened externally and which remain on the local network?
- Who can access measurement, device and business data?
- What backup, restore and retention requirements do you have?
- For which events do you need an alarm, a log and a person in charge?
- Which suppliers or data processors are involved in the service?
A verifiable commitment is more important than a general promise
The detailed security and operational parameters are provided for the given system, so they can be technically checked and accounted for in the contract.
Negotiate security requirements