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.
Showing artifacts, examples and content with confirmed Java applicability. View All CAP
Overview
Handles the four CAP audit log event types and sends them 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, matching the Audit Log Event Catalog's semantics so downstream tooling reads standard events.
Enables the SDK's AuditLog v2 handler, which writes the audit messages 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 via its API version 2 once a service binding is present; without this feature the default handler only writes them to the application log.
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.
A Java coverage assessment has not been written. View all flavors
No community artifact is confirmed here for Java.
A Java coverage assessment has not been written. View all flavors
Artifacts
Details
Coverage
For your agent
- Ref
capability:audit-logging- JSON
- /capabilities/audit-logging.json
- MCP
- Connecting an agent