Epsis takes security seriously and is considered in the development and deployment process. Enify is built and deployed on Microsoft Azure. Therefore we are taking advantage of "best-in-class" security and infrastructure.
We want to be transparent in every way when it comes to security and data protection.
Below we have compiled some general information to help. If you wish more detail please contact our security team directly with your queries.
- We use Microsoft Azure Cloud services
- Enify is taking advantage of Microsoft Azure cloud services when it comes to authentication of users.
- Enify is using HTTPS and SSL for data traffic between your computer (the client) and the Enify Service (on a Microsoft Azure tenant in the cloud).
- Access Roles in Enify
- In Enify, roles are used to give users access to program functionality. Roles are set up and applied by an Admin user within the Enify software suite. These roles can be quite granular granting access to individual parts of Enify functionality as individual users or groups.
- The Admin role is given based on the subscription you have.
- In Enify, roles are used to give users access to program functionality. Roles are set up and applied by an Admin user within the Enify software suite. These roles can be quite granular granting access to individual parts of Enify functionality as individual users or groups.
- Security of resources opened using Enify
- Enify opens applications but does not override any existing security.
- When using Enify elements and boards to open applications, data or documents any existing security will remain in place. Enify has no means to bypass any existing security.
- I.e. you can not open information from an application in Enify if you don’t have access outside of Enify.
- I.e. you can not open information from an application in Enify if you don’t have access outside of Enify.
- Security implications of sharing resources within Enify
-
- Boards and Elements shared with other users will not grant them access to those resources (Data, applications and documents). Those users will need to have access to the resources with their own credentials to be able to utilise them.
- Elements or boards can be shared with read-only permission (meaning they cannot edit the element or board) or with edit permissions if you wish. This can be done on a case-by-case basis.