. Using the mentioned form you can:
Subtitle |
---|
Prefix | figure |
---|
SubtitleText | Data Masking options |
---|
AnchorName | data_masking |
---|
|
|
Three options are available for logs about Calls and Secure Messages:
- Do not archive: won't keep trace of any record at all. Exception is for enqueued Secure Messages to be delivered: they are shown in web console as masked events and they are deleted as soon as delivered to recipient.
- Masked out: mask all sensitive data replacing them with "XXX". You just get time and duration of calls and trace of message delivery but you cannot tell who's who for both sender and receiver or caller a callee.
- Disabled: no masking is applied and events are kept in their original form.
Whichever Data Masking policy is configured, Data Retention policy applies: it is possible to have secure messages masked and configure one week data retention policy, to automatically delete them, as soon as they are not useful anymore for support needs to end-users.
Data Masking changes type of data that are going to be stored (if you chose to store them at all).
As said in the previous paragraph (4.0.3.2), there are two left menu entries to manage the Data Retention feature (see
Xref |
---|
AnchorName | data_retention_menus |
---|
|
). If you want to access to the stored archives just press the "
Archived Data" link.
Subtitle |
---|
Prefix | figure |
---|
SubtitleText | Data Archive List |
---|
AnchorName | data_archive_list |
---|
|
|
The "Data Archive List" is shown in the page body (see
Xref |
---|
AnchorName | data_archive_list |
---|
|
). Each archive row shows its
Name, its
Creation Timestamp and its
Size (all the columns are pretty self explaining).
The last two columns shows two icons: the first one is for downloading the archive, the second one is for deleting it.
Tip |
---|
It's possible to download the archive also by clicking on its name |
Data Archives and Secure Messaging
You can just download a CSV view of Secure Message transport data, such as sender, recipient, acceptance date, delivery status.
Warning |
---|
Secure Messages payload is never saved. As soon as Message has been delivered, its payload (aka Message content) is deleted from 's data storage |
Delete Data Archives
If you choose to delete the archive, press the last column icon.
Subtitle |
---|
Prefix | figure |
---|
SubtitleText | The confirmation pop-up window |
---|
AnchorName | popup_are_you_sure |
---|
|
|
A confirmation is requested (see
Xref |
---|
AnchorName | popup_are_you_sure |
---|
|
). If you approve the action then the archive is removed from both the list and the hard disk of the appliance.
Warning |
---|
title | Point of no return action! |
---|
|
Please be aware that this action isn't undoable! Once confirmed the deletion, the archive is lost forever! |
System's logs
In addition to historical data collected in internal database, the two main
's components can log debug information in log files.
They main components are:
- Secure Voip Engine
- Web Console
Both of them use default system locations (specifically directory /var/log) to store their logs. saves only the last week of these files and rotates them on a daily base. Rotate operation implies both deletion for files oder than one week and archiving in .zip format for the most recent ones. All the log files are labelled by timestamp of the rotation.