Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
We configured the API keys today. This was fairly painless for us. After creating the Key Admin API Key, and generating the client api key, they are activated automatically. No futher action needed. We noticed that prior to this change, the API URL ...
As far as I'm aware, there is no SE version what works well with 24H2. My testing showed the issue even with the 8.2.x train.If you can't wait for the fix, you have the option to make a TAC case, and have them disable the offending exploit prevention...
We got a TAC update last night. The issue will be resolved in Secure Endpoint connector 8.4.4. The release is expected somewhere in January 2025. As usual, timelines can change. Hopefully they deliver in in Jan '25.
