Audit Log Support in Storage Data Service (SDS)

date september 9, 2024 we're excited to announce the latest updates to our sds service in accordance with gdpr and other compliance standards, we have introduced a new audit logging feature for the sds data api core/api/v1/sds/data to ensure traceability of data access and modifications this update aims to enhance compliance, security, and data traceability supported features audit logging all api requests to the sds data api will now be automatically recorded in the audit log stream the logs will capture critical information, including the aaa user id, user name, and application id from the x coreos user info header handling the x coreos user info header when present if the x coreos user info header is included in the api request, it must be forwarded unchanged to ensure audit data integrity when absent if the x coreos user info header is not provided, it will be automatically populated by the service mesh layer of the os1 platform storage and access audit logs will be stored as parquet files in s3 logs can be queried via amazon athena, with access available at the tenant level or for individual sds resources data access requests the psi team will provide audit log data dumps upon request ensure to provide adequate justification when requesting sensitive audit information reference documentation for detailed information on how to use audit logs, refer to the audit logging developer guide