Hi Tharindu,
I believe we can stick to the same format of
| | | |
Because in that format we can include the same required results that Megala
wants.
thanks,
Dimuthu
On Wed, Mar 14, 2018 at 5:47 PM, Megala Uthayakumar wrote:
> Hi Sanjeewa/Tharindu and all,
>
> I have done some reading on
Hi Sanjeewa/Tharindu and all,
I have done some reading on this area and has come-up with the doc based on
guidelines.
Following is the summary based on my reading,
GDPR does not directly mention the recommendations related with logging and
monitoring. However based on various points given under t
There are some recommendations related to GDPR and it would be great if we
can search little bit. Then we can figure out what we need to do
additionally support GDPR requirements. Log access to personal data is
something everyone discuss these days. As recommended every read operation
on a personal
Hi Tharindu,
Thanks for the response. I think we could define a new format, given that
it improves the search based on logs. I will go through provided docs.
Thanks.
Regards,
Megala
On Tue, Mar 13, 2018 at 5:19 PM, Tharindu Edirisinghe
wrote:
> Hi Megala,
>
> For improving the search friendli
Hi Megala,
For improving the search friendliness, are you defining a new format for
the audit log entry ?
Currently we have following format.
| | | |
Eg: INFO {AUDIT_LOG}- Initiator : admin@carbon.super | Action : Add User |
Target : newuser | Data : { Roles : } | Result : Success
In OWA
Hi All,
I am working on improving audit logs related with user management tasks.
Currently we have audit logs upto some extent, however it could be further
improved. So in this improvement I will focusing on following tasks
1. Modifying the current audit logs, so that they will give better
