The Date Limit determines how far back Audit Scan will look for evidence
When performing audit scans from within an audit, all evidence in scope for that audit will be evaluated. Unlike an audit, Continuous Compliance mode doesn't have a fixed start date, so we introduced Date Limit to control how far back in time Audit Scan will look for evidence.
Additional background: Evidence Relevant Date and Audit Scan and Compliance Roadmap FAQs.
Without a way to limit the date, all evidence within an account could be considered valid when conducting an audit scan. That could be exactly what is expected when an account is brand new, but at a certain point some of that evidence is no longer relevant and may actually cause issues. The Date Limit addresses this challenge by setting a limit to how far back audit scan will look in Continuous Compliance mode.
Using Date Limit
Your Date Limit is set to the account creation date by default. Once the Date Limit is more than a year in the past, the Trustero platform will recommend updating the Date Limit to another date that is less than a year old.
The Date Limit can also be set at any time by going to Settings -> Account in the left navigation window and then selecting Date Limit.
Implications of Date Limit
Audit scan completeness and spot check results are related to a given context - the audit or continuous compliance mode with a given Date Limit. If that context changes, a new audit scan will have to be conducted to give accurate results for that context.
After you change the Date Limit, you will no longer see audit scan results for completeness and spot check in your Compliance Roadmap Audit Readiness page because the context has changed. You will need to run audit scan again to get new results that are valid for the updated context. This also means the completeness and spot check results from Continuous Compliance mode and audit mode need to be determined independently.