@cap-js/audit-logging
Advanced tools
Changelog
Version 0.4.0 - 2023-10-24
x509
SELECT
s to resolve data subject IDs, which resulted in "Transaction already closed" errorsChangelog
Version 0.3.2 - 2023-10-11
Changelog
Version 0.3.1 - 2023-09-25
@PersonalData.DataSubjectRole
to entity nameChangelog
Version 0.3.0 - 2023-09-05
cds.requires['audit-log'].handle
changed to ['READ', 'WRITE']
, i.e., accessing sensitive data is now logged by default.Changelog
Version 0.2.0 - 2023-09-01
AuditLogService
for extending in custom implementations as follows:
const { AuditLogService } = require('@cap-js/audit-logging')
class MyAuditLogService extends AuditLogService {
async init() {
[...]
// call AuditLogService's init
await super.init()
}
}
module.exports = MyAuditLogService
Changelog
Version 0.1.0 - 2023-08-18
await audit.log('<event>', <data>)
for asynchronous logs (cf. emit
)await audit.logSync('<event>', <data>)
for synchronous logs (cf. send
)LogEntry
aspectSensitiveDataRead
, PersonalDataModified
, ConfigurationModified
, and SecurityEvent
cds.requires['audit-log'].handle: [...]
.
Possible values in the array are READ
and/ or WRITE
, with WRITE
as the sole default entry.
Hence, accessing sensitive data is not logged by default.@sap/audit-logging
)dataAccessLog
, dataModificationLog
, configChangeLog
, and securityLog
@AuditLog.Operation
annotations are ignored. Having the plugin as dependency signals the intent to audit log.cds.features.audit_personal_data: true
is no longer necessary. Instead, simply add the plugin as a dependency.