Will the SOAR SDK and Siemplify methods be deprecated after migrating SOAR to GCP?
References:
- https://docs.cloud.google.com/chronicle/docs/soar/admin-tasks/advanced/migrate-to-gcp
- https://docs.cloud.google.com/chronicle/docs/soar/admin-tasks/advanced/api-migration-guide
Background:
We are in the process of migrating to GCP for Google SecOps SOAR. We currently have an integration that uses the SOAR SDK internally, and that SDK is built on the older Siemplify APIs.
Questions:
1. Will the SOAR SDK be fully migrated to the new Chronicle API?
The SOAR SDK currently uses the old Siemplify APIs internally. After migrating SOAR to GCP, will the SDK itself be updated to use the new Chronicle APIs under the hood — or will we need to make changes on our end?
2. Will Siemplify methods used in Actions, Jobs, and Connectors be deprecated after migration?
We are using Siemplify methods directly in our Actions, Jobs, and Connectors. Will these methods still work after migration, or will they be deprecated?
Some examples of the methods we are currently using:
python
siemplify.extract_action_param()
siemplify.result.add_result_json()
siemplify.LOGGER.info()
siemplify.get_cases_by_filter()
SiemplifyAction()Will we need to refactor all usages of these methods to use the new Chronicle API equivalents, or can we continue using them post-migration?
3. Does integrations after migration will be also going to exist on Content Hub?
4. Is stage 1 of migration is for everyone who is using SecOps SOAR, correct?
