Confirmed users, Administrators
5,526
edits
CA/Audit Statements: Difference between revisions
added more clarification about the audit period not found error.
(→Providing Auditor Qualifications: Added link to ACAB'c AAL Template) |
(added more clarification about the audit period not found error.) |
||
| Line 105: | Line 105: | ||
| Statement Date Not Found || The audit statement date was not found in the audit statement. || Check that the date that the audit statement was issued is clearly indicated in the audit statement and follows the [https://www.ccadb.org/policy#51-audit-statement-content format requirements] for dates. If needed, request an updated audit statement from your auditor. Sometimes ALV gives false alerts for dates, so if needed you may add a Case Comment about that. | | Statement Date Not Found || The audit statement date was not found in the audit statement. || Check that the date that the audit statement was issued is clearly indicated in the audit statement and follows the [https://www.ccadb.org/policy#51-audit-statement-content format requirements] for dates. If needed, request an updated audit statement from your auditor. Sometimes ALV gives false alerts for dates, so if needed you may add a Case Comment about that. | ||
|- | |- | ||
| Audit Period Not Found || ALV was unable to find the audit period start and end dates in the audit statement. || If the dates in the audit statement follow the [https://www.ccadb.org/policy#51-audit-statement-content format requirements], then this error can also be the result of the audit period being stated in various locations throughout the document or separately in different rows within a table, etc. It helps ALV for the audit period to be stated towards the top of the document and included with words like "during the period from May 1, 2018 through April 30, 2019". | | Audit Period Not Found || ALV was unable to find the audit period start and end dates in the audit statement. || Currently ALV only supports <date> <word that indicates "to", "until", or "through", or a symbol (like a dash)> <date>. | ||
If the dates in the audit statement follow the [https://www.ccadb.org/policy#51-audit-statement-content format requirements], then this error can also be the result of the audit period being stated in various locations throughout the document or separately in different rows within a table, etc. It helps ALV for the audit period to be stated towards the top of the document and included with words like "during the period from May 1, 2018 through April 30, 2019". <br /> | |||
Additionally, you may see this error if there are other problems with the audit period, such as it being less than one month -- point-in-time audits have to be manually reviewed. | |||
|- | |- | ||
| Failed to validate EKU ... because the standard names and standard policies are not found in the audit letters || ALV was unable to find the specific text (case insensitive) that it looks for for each EKU. For example, "319 411-1 v1.1.1, dvcp;ovcp;ptc-br" || Make sure that the audit statement correctly indicates the audit criteria that was used, and that it satisfies [https://www.mozilla.org/en-US/about/governance/policies/security-group/certs/policy/#312-required-audits Mozilla's requirements]. | | Failed to validate EKU ... because the standard names and standard policies are not found in the audit letters || ALV was unable to find the specific text (case insensitive) that it looks for for each EKU. For example, "319 411-1 v1.1.1, dvcp;ovcp;ptc-br" || Make sure that the audit statement correctly indicates the audit criteria that was used, and that it satisfies [https://www.mozilla.org/en-US/about/governance/policies/security-group/certs/policy/#312-required-audits Mozilla's requirements]. | ||