Hi @craig
Yes, as @kose pointed out, we have mitigation steps and patches available in this post: Urgent Log4j server security vulnerability - REQUIRES IMMEDIATE ATTENTION!
We reached out on several channels (CoP, newsletter/email, slack) but if you know of any implementations that have not received the announcement, please pass on the info/link.
Kind regards,
Phil
(I’ll add Log4j explicitly to the title)