Audit logging
Recording who touched personal or sensitive data, in a form an auditor accepts, without hand-writing it in every handler. It is often confused with application logging, which records what the code did rather than who accessed what.
Overview
com.sap.cds:cds-feature-auditlog-ng A CAP Java plugin that sends audit log events to the SAP Audit Log serviceSAP Audit Log serviceIngests compliance audit data from BTP services and applications and keeps it for ninety days by default; retrieval and longer retention are separate services.sap official, btp in the format the Audit Log Event Catalog expects.
com.sap.cds:cds-feature-auditlog-v2 The CAP Java handler that sends the SDK's AuditLog events to the SAP Audit Log serviceSAP Audit Log serviceIngests compliance audit data from BTP services and applications and keeps it for ninety days by default; retrieval and longer retention are separate services.sap official, btp over its API version 2, once a service binding is present.
com.sap.cds:cds-services-bom Ships an AuditLogService for personal data access, personal data modification, configuration change and security events, with a default handler that writes them to the application log; a service binding to SAP Audit Log serviceSAP Audit Log serviceIngests compliance audit data from BTP services and applications and keeps it for ninety days by default; retrieval and longer retention are separate services.sap official, btp v2 needs the separate cds-feature-auditlog-v2 module.
Not covered: The automatic part stops at what the model annotates as personal data: configuration changes and security events are defined as event types, and only the application's own code sends them, through audit.log in Node.js or the AuditLogService methods in Java. It writes the trail and does not read it back: production needs a premium-plan instance of the SAP Audit Log serviceSAP Audit Log serviceIngests compliance audit data from BTP services and applications and keeps it for ninety days by default; retrieval and longer retention are separate services.sap official, btp, and retrieval goes through a separate auditlog-management instance or the SAP Audit Log Viewer.
No community artifact is documented here.
On BTP the audit trail is a service an application writes to, not a library it links. SAP Audit Log serviceSAP Audit Log serviceIngests compliance audit data from BTP services and applications and keeps it for ninety days by default; retrieval and longer retention are separate services.sap official, btp ingests compliance audit data from BTP services and from the applications running on them, and keeps it ninety days by default.
Present, not yet described.
Not covered: At ingestion and the default ninety days. Reading the trail back, and keeping it longer than that, are separate services — so "the platform records it" does not by itself answer the question an auditor asks.
Core-only here reads the SAP-published entries behind the door: the SAP Audit Log serviceSAP Audit Log serviceIngests compliance audit data from BTP services and applications and keeps it for ninety days by default; retrieval and longer retention are separate services.sap official, btp and s4hana-hana-audit-policiess4hana-hana-audit-policiesSQL templates for the SAP HANA audit policies of the database tenant an SAP S/4HANA system uses, in four sets from the mandatory default policies to scenario examples.sap official, btp, which defines audit policies for the HANA database tenant under S/4HANA. It is an assessment of the corpus, and what_core_does is left empty: no page has been checked that states an intent here, and the entries carry their own descriptions and links.
No community artifact is documented here.
Artifacts
Content
Show 10 more
Show 3 more
Seen working
Details
Coverage
For your agent
- Ref
capability:audit-logging- JSON
- /capabilities/audit-logging.json
- MCP
- Connecting an agent