The audit must be done by a qualified, objective, independent professional following accepted auditing standards (for example from AICPA, PCAOB, ISACA or ISO). An internal auditor must not design, run or advise on the programme being audited, and the head auditor must report to, be evaluated by and be paid by an executive without direct responsibility for cybersecurity. The business must give the auditor all requested information, disclose relevant facts in good faith, and accept that findings rest mainly on documents, sampling, testing and interviews rather than management assertions. The report goes to the executive responsible for cybersecurity, and both business and auditor keep audit records for five years.
This control maps to 1 controls across 1 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.
CCPA/CPRA CCR 7122 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of CCPA/CPRA your existing evidence covers. Hold GDPR and 17 of 89 CCPA/CPRA controls already carry evidence.
Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 0 were rejected on the GDPR pair alone.
The graph holds this control, the 1 it maps to, and the evidence behind each claim, over MCP and REST.