Event logs must be reviewed by continuous automated monitoring or by manual review at a documented frequency to find irregularities and propose remediation, logs must where possible record access to personal data including who accessed it, when, whose data it was and what changes resulted, roles must be defined and agreed where several providers share the logging duty, log information that itself contains personal data must be access controlled so it is used only as intended and deleted or de-identified per the retention schedule, and a processor must define and publish to customers the criteria for making log information available while ensuring one customer can never read or amend another's records; protection of logs, administrator and operator logs and clock synchronization apply as the base guidance requires.
ISO 27701:2019 6.9.4 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of ISO 27701:2019 your existing evidence covers. Hold SOC 2 and 58 of 108 ISO 27701:2019 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. 289 were rejected on the SOC 2 pair alone.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.