Morning. Daniel, I look after IT and security for a manufacturer, based in the UK. Our other plant has been on Hermetry for a while. We created our organisation back in January and it has sat mostly empty since, but now it’s our turn: vibration sensors on the main motors first, more later.
I’m not the one writing firmware. I’m the one who answers for accounts, access and the audit trail when someone asks, so expect questions on roles and sign-in more than on sensors.
Welcome Daniel. The checklist for a new organisation on the Security page is a good place to begin: a passkey plus a backup passkey for every owner and admin, Require two-step verification for every member once everyone has a second factor, at least two owners or admins, and field staff on the User role. Device profiles on TLS only (port 8883) and allowed networks for fixed sites are on the same list.
Useful, thanks. The auditors will ask who changed what on devices and users. How much of that is recorded, and can I hand them an export?
Every row holds the time, the actor (a member, an API key, the system or a service), the action, its severity, the resource, and the address and browser. Secrets, passwords, tokens and attribute values are never written. The log is hash-chained and you set its retention to what your compliance rules need. Export CSV downloads the rows for the date range of the filter. What is audited lists the actions by area, and Audit log covers reading, exporting and verifying it.
- Vous devez être connecté pour répondre à ce sujet.
Rejoignez la discussion
Connectez-vous pour poser et répondre à des questions, aimer les messages utiles et marquer la réponse qui a résolu votre problème. Chaque contribution rapporte des points et des niveaux.