SecOps knowledge sharing: Bridging the communication gap on new releases

You could post an update in the forums here with an Patch Notes label or something like that. That could help users who would like an update log. As of now the update log is found in documentation, and going over patch notes would help in a forum post, could get gemini to spit it out in a cool format too. As this page gets more popular I see it being an applied use.

I appreciate you sharing your insights. When you're going through update logs and documentation, what parts do you find the most difficult or confusing? Any suggestions for making this process easier? 😁

The updates made to the product is found in the release notes of the main page:

https://cloud.google.com/chronicle/docs

To begin, I just started learning about Google SecOps, took the learning pathway, studied documentation, for context.

Going through this, the URL says chronicle but it's rebranded now. A lot of info about how SecOps works is branded with the old Chronicle name, and i'm assuming there is probably an ongoing effort from Google to rename all old info from Chronicle to the new name. It confuses new users a bit though. SecOps is now a SIEM/SOAR solution, and that should be a forefront effort to tell people, instead of viewing them as separate services as they were previously. Also, distinguishing the Google Cloud SCC from SecOps would assist new users from the two as well, as the only documentation covers these as integrating with one another, but per google response they are completely different products.

This is just feedback for these services in general. For your original question: this is how I keep up to date with the release: notes: https://cloud.google.com/chronicle/docs/secops/release-notes

Something similar to this, or some sort of automation to take the release notes from this page, and post it here in this forum, would create more visibility and cross-site navigation for these tools in my opinion.

Also going over any bug fixes, or any new features to come, etc. would help communication with the community. 

Thanks.

You are absolutely right! We rebranded earlier this spring and SecOps was previously known as Chronicle. I can understand how the distinction between SCC and SecOps might not be clear for new users who are just getting familiar with our platform. I really appreciate your feedback and I'll definitely take note of this. Thank you for joining the conversation!