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.
Part of the cds-services-bomcom.sap.cds:cds-services-bomThe Maven bill of materials for CAP Java, pinning every com.sap.cds module in a release, from the API and core runtime to the Spring Boot starters and the CQN engine, to the same version.sap official, cap release line, this module is the AuditLog v2 handler for the AuditLog service built into the CAP Java SDK. By default the SDK only writes AuditLog messages, personal data accesses, personal data modifications, configuration changes and security events, to the application log at DEBUG level; adding this feature with runtime scope in srv/pom.xml and a service binding to the AuditLog v2 service instead 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 over its API version 2. A project can still register its own custom AuditLog handler alongside it, or turn this one off with the cds.auditLog.v2.enabled property. Node.js reaches the same service through @cap-js/audit-logging@cap-js/audit-loggingIntegration with the SAP Audit Log service, so operations on personal data are recorded in the form an auditor expects without the application writing the entries.sap official, cap.
Facts
Where it sits
What it declares
Every artifact
- Type
- Package
- Origin
- By SAP
- Runtime
- Java
As a package
- Where it runs
- does not say
- Distributed through
- does not say
Connections
Recording who touched personal or sensitive data, for auditors
Ingests and retains compliance audit data from BTP
Download
Where it sits in your app
Download
Others providing
Compare all 6 on the Audit logging page →- 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, btpIngests and retains compliance audit data from BTPfrom BTP/BAIP
- com.sap.cds:cds-feature-auditlog-ngcom.sap.cds:cds-feature-auditlog-ngA CAP Java plugin that sends audit log events to the SAP Audit Log service in the format the Audit Log Event Catalog expects.sap official, capCAP Java plugin sending audit log events to SAP Audit Log servicefrom CAP
- com.sap.cds:cds-services-bomcom.sap.cds:cds-services-bomThe Maven bill of materials for CAP Java, pinning every com.sap.cds module in a release, from the API and core runtime to the Spring Boot starters and the CQN engine, to the same version.sap official, capMaven bill of materials pinning CAP Java module versionsfrom CAP
- @cap-js/audit-logging@cap-js/audit-loggingIntegration with the SAP Audit Log service, so operations on personal data are recorded in the form an auditor expects without the application writing the entries.sap official, capCAP integration with the SAP Audit Log servicefrom CAP
- 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, btpSQL templates for HANA audit policies of an S/4HANA tenantfrom BTP/BAIP
Details
Sources
Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.
Compatibility and provenance
Flavors
“As of CAP Java 1.18.0, an AuditLog service is provided for CAP Java applications.” — Audit Logging
History in the atlas
- Enables the SDK's AuditLog v2 handler, which writes the audit messages to the SAP Audit Log service via its API version 2 once a service binding is present; without this feature the default handler only writes them to the application log.
- First seen.
For your agent
- Ref
artifact:cap-java-cds-feature-auditlog-v2- JSON
- /artifacts/cap-java-cds-feature-auditlog-v2.json
- MCP
- Connecting an agent