eBiss 3

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Protecting sensitive data ======


From this version onwards, messages containing sensitive data can be can be given special protection. To this end, two approaches have been implemented in eBiss:
  * “audit-proof” can be excluded from global access and
  * Messages can be encrypted.


==== Audit-proof nodes ====

If a node is defined as “audit-proof”, only users from that specific node have access to it. Even administrators from other nodes have no access, neither to the node itself nor, for example via the global search, to elements within the node.
The “audit-proof” property is set in the node type. This is only possible 
  * for a user with admin rights from that specific node and
  * if there are no sub-nodes.
 !!! This setting cannot be undone.


==== Encrypting messages ====

From this version of eBiss onwards, messages can be encrypted. To do this, 
  * the eBiss system must have been enabled for encryption using the eBiss configurator, and 
  * a key file must be stored on the server. 
The administrator can then set a message basket to “Encrypted”. This setting cannot be undone!


All messages created in this message basket will then be encrypted and remain so, even if they are moved to another message box.

The ‘Message store’ access right, and specifically ‘View encrypted’, can be used to control which users can read encrypted messages. A user without this permission cannot open or save an encrypted message. Nor can they open it in a mapping or start a job.
eBiss 3

User Tools

Site Tools

Page Tools
