Is anyone using the Wiz Integration for Security Operations 1.0.2?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-04-2023 08:10 AM
We're trying to get the Wiz Integration for Security Operations version 1.0.2 plugin up and running, but I'm getting a setAbortAction cross-scope access error when I try to hit submit on the Wiz Record Producer:
If I try to skip this step and run the integration I get an invalid authentication header error:
When I check the Wiz audit logs it doesn't even look like the service account we're using for the integration is attempting to authenticate. I think the initial 'setAbortAction' error is causing the plugin to crash before authentication takes place. Is this an issue with the plugin, or an issue with our configuration? Is anyone else successfully using this version of the plugin and if so, did you encounter this issue?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-25-2023 06:19 AM
Hi @Josh_M ,
The error is not relevant. The Authentication error you are getting is because of a KMF issue with the client's secret. I also faced the issue and was able to resolve it as follows:
- Assign sn_kmf.cryptographic_manager role to your user if you don't have it already. Note: The user should have security_admin and sn_kmf.admin roles to perform this activity.
- Navigate to Key Management > Module Access Policies > All.
- Filter the list view with Crypto Module = com_snc_security_support_core_glideencrypter.
- You can skip this step if you have already run the Integrations once. Execute any Wiz scheduler to test the connectivity. If the feature executed has the requirement of decrypting the value from the Integration Item Configurations (sn_sec_core_integraiton_item_config) table and the caller entity does not have access to decrypt, the system will create a corresponding MAP record.
- This record is created with Result = Reject and Crypto Module = com_snc_security_support_core_glideencrypter and you can view this log as Access Denied to cryptographic module 'global.com_snc_security_support_core_glideencrypter': no thrown error in System Logs.
- Name the MAP record created appropriately and set Result = Track. This will set the record to track or grant access for the crypto module to the target mentioned in the MAP record.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-22-2024 09:46 AM
@Josh_M - were you able to resolve this? I am encountering the same issue.