Initial Release

[crestdatasystems]

Features

New App: Google Threat Intelligence

Manual Documentation

Have you made any changes that should be documented in manual_readme_content.md?

The following changes require documentation in manual_readme_content.md:

• New, updated, or removed REST handlers
• New, updated, or removed authentication methods, especially complex methods like OAuth
• Compatibility considerations with respect to deployment types (e.g. actions that cannot be run on cloud or an automation broker)

• I have verified that manual documentation has been updated where appropriate

Other information

---

Please refer to our Contribution Guide for any questions on submitting a pull request.

Thanks for contributing!

[crestdatasystems]

Hello Splunk Team,
We have resolved the pre-commit failures on our end. It seems that some updates might be required from the Splunk side to address the remaining failing scenarios.

Please let us know if there’s anything still pending from our side. Also, do you have an estimated timeline for when the merge request will be merged?

[mmomin-crest]

Hello @crestdatasystems, thank you for your contribution. We’ll add this to our queue and begin reviewing the PR shortly.

[stutib-crest]

@crestdatasystems The description of the connector needs to be short, one of the possible descriptions could this:
"Supercharge Splunk SOAR with Google Threat Intelligence by integrating real-time IOCs, breach insights, and threat actor data from VirusTotal, Mandiant, and Google for automated, context-rich responses". Could you please update it? The rest of the information can be included in the manual_content_readme file of the connector.
Thanks

[crestdatasystems]

@stutib-crest Thanks for the suggestion. We have updated the app description as per your recommendation and moved the previous description to manual_content_readme.

[splunk-soar-semantic-release]

🎉 This PR is included in version 1.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀