Logging

Logging is done with our S3 server access and object-level API activity. We utilize versioning to track changes over time, which allows easy rollback to previous versions. Flosum also uses cross-region replication for geographically separate backups and enhanced availability. We maintain object locks and MFA delete on backup buckets. Logs are collected through Syslog from multiple instances and tiers, including application, network, and OS events. These logs are then centrally reviewed and analyzed for further insights and actions. Additional logging is available in the AWS Cloud Trail for the tool. Extensive audit trails record all actions performed by users (login/creation/change/addition/deletion of content, settings, parameterizations, etc.) and on users (creation/change/deletion of users, inclusion/change/deletion of access profiles, password changes, etc.).