Differences

This shows you the differences between two versions of the page.

--- governance [2018_06_15 23:47] – steven
+++ governance [2024_04_24 22:01] (current) – [Archiving and Erasing Audit Logs] smeadmin
@@ Line 1: / Line 1: @@
 ====== Governance Settings ======
+== last updated on April 27, 2020 ==
 ===== 1 User Management =====
-{{:/governance:steps:sme_1_user_management.png}}
+{{ ::screenshot_2020-10-30_at_15.23.05.png?600 |}}
 Users and user roles can be controlled directly by the Cloud Administrator when setting up the Cloud File Server.
@@ Line 9: / Line 10: @@
 ===== 2 Permissions and access control =====
-{{:/governance:steps:sme_2_permissions_and_acce.png}}
+{{ ::screenshot_2020-10-30_at_15.25.15.png?600 |}}
 Once shared folders for the Cloud File Server have been added, the Cloud File Server Admin can control access to folders and sub folders using an access control list. If a user has no permission to a folder the folder is not displayed at all in their file tree.
-FAQ: We often get asked if we support Active Directory integration. We support Active Directory integration, and this enables single sign on and group permissions federation. You can find more about Active Directory integration on our Wiki [[organisationcloud/activedirectory|here]].
+FAQ: We often get asked if we support Active Directory integration. We support Active Directory integration, and this enables single sign on and group permissions federation.
@@ Line 19: / Line 20: @@
-{{:/governance:steps:sme_3_notifications.png}}
+{{ ::screenshot_2020-10-30_at_15.27.16.png?600 |}}
-The Cloud File Server Admin can setup notifications. Notifications are based upon rules that are invoked on file events. If a file of a certain description, file name or extension is uploaded, updated, viewed etc, then the nominated users can receive notification alerts.
+The Access Anywhere Admin can setup Audit Watch notifications. Notifications are based upon rules that are invoked on file events. If a file of a certain description, file name or extension is uploaded, updated, viewed etc, then the nominated users can receive notification alerts.
-===== 4 Event Auditing and other Governance options =====
+===== 4 Event Auditing and Other Governance Options =====
+Event logging is built into Access Anywhere and it works above any storage provider that is mapped to Access Anywhere. Which types of events are logged can be controlled by the org. admin from the Security tab of the Policies page:
+{{ :server:server:syslog:events_to_log.png?direct&600 |}}
-{{:/governance:steps:sme_4_event_audtiing_and_o.png}}
+===== 5 Displaying and Filtering Event Logs =====
-Auditing is built into the Cloud File Server and it works above any information Cloud that is mapped to the fileserver. The granularity of the events that are logged s controlled by the Cloud File Server Admin.
+The org. admin can view the events belonging to the org. on the Audit Events Log page which is accessed from the admin's Organization pull-down menu:
+{{ :server:audit_events_log.png?direct&600 |}}
-===== 5 Event Logs =====
+There are five filters:
+**Search logs**
-{{:/governance:steps:sme_5_event_logs.png}}
+The contents of the Log field will be filtered by the value you provide here without regard to case.
-Event logs are generated if auditing is turned on and these can be displayed, filtered, exported or archived.
+{{ :server:better_logs.png?direct&400 |}}
+**Type**
-===== 6 Recording GEO locations =====
+Events are classified by type.  You can filter by any single type or allow all types:
+{{ :server:type.png?direct&200 |}}\\ \\
+**User, Date and Tool**
+You can also filter by the user whose action caused the events, the date or range of dates during which the events occurred, and the tool that was used.
+{{ :server:user_date_range_and_tool.png?direct&200 |}}
-{{:/governance:steps:sme_6_recording_geo_locati.png}}
+The date range is inclusive.  To select events for a specific date set that date as both the From date and the To date.
-GEO locations are recorded with regards to where a file was uploaded from and also where a file was uploaded to. This can ensure companies comply with electronic data laws and international compliance regimes
+You can set values in any or all of the five filters and then search.  The filters are logically combined so that only events that qualify for all of the filter values that have been set are displayed.
-===== 7 Disable File Sharing =====
+Use the Search button at the bottom left of the page to re-filter the results after you change a filter value. You can reset all of the filters to their default (no value) state by clicking in the link under the Search button.
+{{ :server:search_and_reset.png?direct&200 |}}
+=== Exporting Audit Logs ===
+Your filtered set of audit log entries can be downloaded in four forms:
+  * Excel workbook
+  * .csv file
+  * .zip archive.
+  * PDF file as a formatted report
+Access these three options from the Export pulldown near the top of the Audit Event Logs page:
+{{ :server:ael_-_export.png?direct&200 |}}
+=== Archiving and Erasing Audit Logs ===
+Because audit log entries accumulate quickly you will probably want to archive the entries from time to time and then erase them.  You can access archiving and deletion features from the Options pulldown near the top of the Audit Event Logs page:
+{{ :server:ael_-_archive_and_erase.png?direct&200 |}}
+To archive the audit log entries, select Archive from the pulldown menu and a confirmation box will be displayed:
+{{::screenshot_2024-04-24_at_22.58.41.png?200 |}}
-{{:/governance:steps:sme_7_disable_file_sharing.png}}
+Select a folder to archive the logs to.
-The Cloud FIle Server Admin can disable any sharing or collaboration features of the Cloud File Server entirely by disabling the ability for any user to do any form of file sharing or collaboration.
+Click on Archive to proceed or Cancel to cancel.
+If you proceed a background task will be created which will create a zip file containing the audit log entries.  If you care to inspect the background task, find its entry on the Tasks tab of the File Manager page:
-===== 8 Controlling other Data Clouds =====
+{{ :server:archive_cloud_task.png?direct&600 |}}
+Audit logs archives will be placed by the background task into the directory chosen when archiving was started.
+Select Erase Logs from the pulldown menu to erase old audit log entries.
+<WRAP center round important 60%>
+When you erase audit log entries they will no longer be available from Access Anywhere.  If you need a historical record, archive these entries before you delete them and be sure that the archive job has completed successfully prior to proceeding.
+</WRAP>
+When you erase audit log entries, only entries from before a date that you select will be erased:
-{{:/governance:steps:sme_8_controlling_other_da.png}}
+{{ :server:erase_logs_date.png?direct&200 |}}
-As the Organization, or individual users, may user other information clouds, it is preferable for these to be controlled as part of the Cloud File Server rollout in a company. This will enable that any auditing, event logging etc can be setup for such clouds. The Cloud File Server admin can decide which Clouds a user can add.
+After you have selected the date click on Erase to proceed or click on Cancel if you have changed your mind.
-For example if each user has a corporate Google Apps Docs account, then the Admin can enable users to add this directly, and any use of it can also be monitored and audited.
+=== Tracing Downloads by Watermark ===
+The Access Anywhere provides a [[watermarking|]] feature that affixes a random watermark code to downloaded PDF files. You may sometimes want to learn the details of when a watermarked file was downloaded.  To do this, click on the Watermarking Logs link near the top of the Audit Event Logs page:
+{{ :server:ael_watermarking_logs.png?direct&400 |}}
+This will take you to the Watermarking Logs page:
+{{ :server:watermarking_logs.png?direct&400 |}}
+When this page loads it displays a list of all watermarked file downloads in reverse chronological order.  To search for downloads for files with a specific watermark code, enter some or all of the code in the Watermark Code text box and click on Filter.  The text you entered will be used without regard for case to filter the watermark downloads by the code in the first column.  You can clear the filter with the "Clear filter" button.
+### Also See
+[[server/syslog|Integrating Audit logs with Syslog]]
+===== 6 Recording GEO locations =====
+{{ :screenshot_2020-10-30_at_16.07.24.png?600 |}}
+GEO locations are recorded with regards to where a file was uploaded from and also where a file was uploaded to. This can ensure companies comply with electronic data laws and international compliance regimes
+===== 7 Disable File Sharing =====
+{{ ::screenshot_2020-10-30_at_16.10.52.png?600 |}}
+The Access Anywhere Admin can disable any sharing or collaboration features of Access Anywhere entirely by disabling the ability for any user to do any form of file sharing or collaboration from Access Anywhere policies page.
+===== 8 Controlling User Access to Storage =====
+{{ ::screenshot_2020-10-30_at_16.14.21.png?600 |}}
+As the Organization, or individual users, may (if configured) user other storage , it is preferable for these to be controlled as part of Access Anywhere rollout in a company. If available this will also enable that auditing, event logging etc for such storage. The Access Anywhere admin can decide which storage a user can add.
+For example if each user has a corporate Google Apps account, then the Admin can enable users to add this directly (with any use also being monitored and audited.
 ===== 9 Encryption options =====
 {{:/governance:steps:sme_9_encryption_options.png}}
-Cloud Admins can choose for all files to be encrypted when stored on Cloud. This encryption is AES 256 bit military grade encryption.
+Cloud Admins can choose for all files to be encrypted when stored on private / cloud storage. This encryption is AES 256 bit military grade encryption.
+See the [[cloudencryption|encryption section]] for further information.
 ===== 10 File versioning Options =====
 {{:/governance:steps:sme_10_file_versioning_opti.png}}
 To ensure the lifecycle of a file is tracked then file versioning can be turned "on" which results in all changed versions of a file being kept rather than overwritten.
+For further information see the [[versions|versioning section]].
+### Also See
+* [[features/md5hash|File Verification]]
+* [[geoip|IP white listing / black listing]]
+* [[antivirus|Virus Scanning Protection]]
+* [[watermarking|Watermarking Documents]]