![]() ![]() If anyone knows anything or has done anything, I'm all ears. It looks to me like Environment Manager and a couple of mid-tier products might need some adjustments. ![]() ![]() I do have an open track on this: SAS 7613479191, but we didn't hear anything before the end of the day so I'm going to wade into after hours support, because security is still waiting for our answer. Didn't see anything on the security bulletins page about this, so I thought I'd ask here. But we utilize CI360 as SaaS and are uncertain if there is anything on SAS's end that has been done or anything that CI360 might be able to do via the direct agent to put itself in harm's way. We've shut down anything on our SAS 9.4 mid-tiers. Our server admins and information security folks are asking us to define potential exposure to the zero-day log4j2 vulnerabilities discovered recently. I actually am about to employ SAS follow-the-sun support on this in about 20 minutes but was wondering if there's anything I missed. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |