Chronicle - June 18th, 2024 [Change, Feature]

## Feature Google SecOps now integrates with [Access Transparency](https://cloud.google.com/assured-workloads/access-transparency/docs/overview). If you enabled Access Transparency in your organization, Google SecOps writes Access Transparency logs when any Google personnel accesses customer content that supports SIEM features. For more information, see [enabling Access Transparency](https://cloud.google.com/assured-workloads/access-transparency/docs/enable) and [viewing Access Transparency logs](https://cloud.google.com/assured-workloads/access-transparency/docs/reading-logs#viewing-logs). ## Feature Google SecOps now supports [data RBAC](https://cloud.google.com/chronicle/docs/administration/datarbac-overview). This feature enables you to control user access to data within your Google SecOps environment based on their assigned roles. ## Change `lastAlertStatusChangeTime` is added to the response of the [GetRule](https://cloud.google.com/chronicle/docs/reference/detection-engine-api#getrule) Detection Engine API. This indicates when `alertingEnabled` was last updated from `true` to `false` or from `false` to `true`. The field is also added to [RuleDeployment](https://cloud.google.com/chronicle/docs/reference/rest/v1alpha/RuleDeployment) of Chronicle API v1 alpha.