Version history

Version 2.13.0, released 2022-04-26

Add connection and description field to finding's list of attributes (commit a6bcaf5)
Add next_steps field to finding's list of attributes (commit 8d16471)
Add iam_binding field to findings attributes. It represents particular IAM bindings, which captures a member's role addition, removal, or state (commit b341824)

Add BigQuery export APIs that help you enable writing new/updated findings from Security Command Center to a BigQuery table in near-real time. You can then integrate the data into existing workflows and create custom analyses. You can enable this feature at the organization, folder, and project levels to export findings based on your requirements (commit 4a00750)

Update documentation for the Finding resource field "project_display_name" (commit 09ff129)
Update documentation for the Mute fields on Findings (commit 09ff129)

Release the access field in the v1 finding proto, which represents an access event tied to the finding (commit 7013d13)

Added more clarification around what event_time means on a v1 finding (commit 7013d13)

Commit 1cda659: feat: Added a new API method UpdateExternalSystem, which enables updating a finding w/ external system metadata. External systems are a child resource under finding, and are housed on the finding itself, and can also be filtered on in Notifications, the ListFindings and GroupFindings API

Commit 9292121: feat: Added resource type and display_name field to the FindingResult, and supported them in the filter for ListFindings and GroupFindings. Also added display_name to the resource which is surfaced in NotificationMessage

Commit e1080c9:
- feat: Added vulnerability field to the finding
- feat: Added type field to the resource which is surfaced in NotificationMessage

Commit d6c34ac:
- feat: added field severity to findings in v1 API
- Clients will now see a new field, severity, on findings. They will also be able to filter and group by severity on ListFinding and GroupFinding API calls.

Commit 0790924: fix: Add gRPC compatibility constructors
Commit 0ca05f5: chore: Regenerate all APIs using protoc 3.13 and Grpc.Tools 2.31
Commit 3cc0bc8: docs: Clarified that event_time can also be considered as the "update time" for a Finding. It also captures when a Finding was updated. The previous wording could've been interpreted as only the creation time.
Commit ccb9c33: fix: correct securitycenter grpc_service_configs
Commit 6bde7a3: docs: Regenerate all APIs with service comments in client documentation
Commit f83bdf1: fix: Apply timeouts to RPCs without retry
Commit d545bad: Specify allowed fields for UpdateNotificationConfig
Commit 4c52b95: feat: Add Resource to the v1 NotificationMessage, which contains resource-related fields associated to the Finding notification. docs: Adjusted wording from Cloud SCC to Security Command Center, and updated filtering docs for List APIs.
Commit 947a573: docs: Regenerate all clients with more explicit documentation

No API surface changes compared with 2.0.0-beta02, just dependency and implementation changes.

This is the first prerelease targeting GAX v3. Please see the breaking changes guide for details of changes to both GAX and code generation.

Initial GA release.