Mandatory for categories A to D (optional consideration for E): software products implement audit logging that makes user access and actions traceable, for detecting anomalies and investigating incidents. Logs cover access and events including changes to privileges, permissions and authorisations; privileged users are identifiable; shared or generic logins are not allowed so every user and session or event is uniquely identifiable; logs are kept at least 12 months and not deleted within that period, and relevant logs are supplied to the ATO after a security incident. Evidence is sample or real logs (redacted) showing authentication and authorisation, date and time, unique user identifier, success or failure, event description and ICT equipment location and identification, with confirmation of 12-month retention; an audit log policy may cover the inclusions.
This control maps to 3 controls across 2 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.
The graph holds this control, the 3 it maps to, and the evidence behind each claim, over MCP and REST.