You are viewing limited content. For full access, please sign in.

Question

Posted to Government

Question

Audit Reporting - Recommended Procedures

asked on March 16, 2015

I have questions regarding what I should be doing in the Audit Trail component, any pro-active type procedures so the information will be there if we come across an unexpected problem.  Questions I can't find answers to after looking at the usual LF training resources:

  • Should I be setting up any additional audit reporting besides what Audit Trail is already tracking?  Or does it track everything, and all I have to do is create a report to obtain the data when I want it (I have done some exploration and practicing with audit reports).
  • Should I be saving audit reports to another location every so often?  (I've seen some posts that some people are doing this.  Is this something every office should be doing?  Is there a particular type of data people feel they need to save elsewhere?)
  • How long does the Audit Trail component keep the data for?
  • If a doc is to be presented in court and we need to prove it wasn't altered during a period of time, how would I go about proving it using Audit Trail?

 

These are the settings for our repository.

Any tips on policy or procedure for pro-active auditing would be appreciated.

Connie P., Flagstaff County, AB

2 0

Answer

SELECTED ANSWER
replied on March 30, 2015

Connie,  The 30 day info is what is loaded in the reporting DB, but the info is retained for as long as you do not remove the Audit log files.

 

To get data farther back then 30 days, open the Audit reporting configuration site and change the date range.  AT then will load the Audit logs for the period specified.  Under normal conditions, you do not always need the data from an extended time ago, so to save drive space, AT unloads it from the DB (but retains it in a log file for future use if ever needed).

2 0

Replies

replied on March 26, 2015

Connie, I am not sure what your relationship is with your VAR, but first I would get them to do all the heavy lifting. I know that Audit Trail keeps the data in perpetuity. You have to point to what time period you want to search and then it is queued up. The longer the time period, the longer you will wait to get your results.

I also know that the data is derived from your SQL db. I don't know the details too well. I am not sure which SQL log it is.

Hope this helps,

Chris Cartrett

1 0
replied on March 27, 2015

I discovered this week that my Audit Trail is set to only track for 30 days, then it dumps the data.  This kind of eliminates a lot of what I thought I could do with this reporting tool.  I do realize that I can change the setting so it dumps less often, but there is a downside to that and I will need to seriously consider what will be the optimal thing to do.

Wish List from Laserfiche:  A White Paper type document for new Administrators on what settings are recommended for what purposes.  Currently, I am relying on the default settings to be right for us, but I have no idea if they are.  That makes me very uncomfortable.

 

0 0
SELECTED ANSWER
replied on March 30, 2015

Connie,  The 30 day info is what is loaded in the reporting DB, but the info is retained for as long as you do not remove the Audit log files.

 

To get data farther back then 30 days, open the Audit reporting configuration site and change the date range.  AT then will load the Audit logs for the period specified.  Under normal conditions, you do not always need the data from an extended time ago, so to save drive space, AT unloads it from the DB (but retains it in a log file for future use if ever needed).

2 0
replied on March 31, 2015

It sounds like Connie needs to keep playing around with AT to get shake out all of its secrets. I had to go in to my AT yesterday and reviewed all of the Administration documentation online. There is not much there!

I know quite a bit from working with my VAR on it. It is a simple animal, but definitely a tool that can be used.

Connie, why don't you post to the regular Answers site to get some feedback from the designers and developers of Audit Trail? You could even just copy and paste in your original question. The groups here don't see much traffic from Laserfiche technical support.

 

1 0
replied on April 9, 2015

Thanks for the tips.  Good to know that the 30 day setting isn't for how long to track data, but only telling it how many days data to load for the reports.

And I will post on the regular Answers site, as suggested.

Thanks!

Connie

1 0
You are not allowed to follow up in this post.

Sign in to reply to this post.