-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please add support for SCC findings exports to BQ via gcloud scc bqexports
#18848
Milestone
Comments
From triage: This resource would map to this entity in the API, which is possible to manage via CRUD despite representing a single, imperative action. This new resource represents the "One-time exports for existing findings, assets, and security marks" as described in the docs |
github-actions
bot
added
forward/review
In review; remove label to forward
service/securitycenter
labels
Jul 29, 2024
This was referenced Aug 19, 2024
This was referenced Aug 28, 2024
This was referenced Aug 30, 2024
This was referenced Sep 12, 2024
This was referenced Sep 13, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Community Note
Description
Currently, the recommended method to export findings from SCC to BQ is gcloud scc bqexports - however this isn't supported in the GCP provider yet. The other method (SCC -> PubSub -> BQ) is much more toilsome (you need a cloud function to parse and insert the finding, or do post-processing from the
data
field in the BQ table).New or Affected Resource(s)
Potential Terraform Configuration
References
e.g. create
b/356159589
The text was updated successfully, but these errors were encountered: