During projects (Eppendorf and Hillrom) we are facing some use cases, where the core platform doens't create audit log entries for specific activities:
Registration of devices
Login/Logout/Failed login attempts (In scope for 10.10)
Events in general
Some of them could of course be covered by custom implementations, but this would lead to non-generalized audit log entries accross different platforms.Some of the scenarios could not be covered by a custom implementation (failed login).
As part of the support to comply with STIG in release 10.14 C8YKERNEL-250 the Access Log has been improved and the number entries increased. The name has also been changed to Audit Log and tracks all incoming and outgoing calls to Cumulocity IoT. This log is set on at the instance level by the Operations Team.