access change report fails when report end-date (not start-date) is more than 3 months ago

  • 1
  • Problem
  • Updated 1 week ago
When running an access change report (which contains less information than I really wanted, but that's another issue) the report fails when the report end date is more than 3 months ago, regardless of start date.
So today, it's possible to generate a report for date range feb 4 - may 5, but not possible to generate a report for date range mar 4 - apr 4, for example.
So it seems this is not because of a lack of data, but due to deliberately failing even though the data for that period is available and can be extracted in a broader report.

Maybe it's an intentional "feature" to limit access to the data after 3 months, but it's not compliant to actually keep the data stored and just make it harder to access. And for compliance reasons, we need to be able to produce logs for longer than 3 months. So can this be fixed?
Photo of Maarten

Maarten

  • 15 Posts
  • 0 Reply Likes

Posted 2 weeks ago

  • 1
Photo of Leo

Leo, Official Rep

  • 367 Posts
  • 25 Reply Likes
Hi Maarten,

When you run the Feb 4th - May 5th report, do you actually see entries from before 90 days?

-Leo
Photo of Maarten

Maarten

  • 15 Posts
  • 0 Reply Likes
Yes, I see data for the full date range.
Photo of Maarten

Maarten

  • 15 Posts
  • 0 Reply Likes
Any update yet? Would be great if this could be fixed so we can prepare all necessary documentation before the audit team comes in.