(Dec. 15, 2021) The Zerion team is hard at work understanding and adjusting to the present Log4j vulnerability. Given the fluidity of the situation, we will be posting updates here as we learn more and steps are taken to address any issues or concerns. Please bookmark this page in your browser or follow the article for notifications when updates are made.
We appreciate your patience and understanding!
UPDATE December 15, 2021 3:47PM EST
Zerion Software has reviewed the infrastructure and sub service providers used to host our commercial software, along with our internal delivery and support tools.
There are two Amazon Web Services services we use that are impacted by Log4j, and those are actively being upgraded per the remediation steps from AWS. These services are used for internal auditing and usage metrics of the application.
Customer data is not processed in either of these tools, and no action is necessary from you. At this time, we have no reason to believe customer data has been exposed or is at risk. Additionally, no foreign network traffic has been flagged for review.
The two services mentioned above will be updated by December 15, 2021 at 11 PM EST.
We are monitoring impacted service providers that are not in our direct control for updates every 8 hours.
Comments
5 comments
Hi all, update for 12/16/21 11 AM EST.
Upgrades for the impacted AWS service were initiated last night and are pending completion from the AWS team. We will continue to post a brief update twice a day indicating if the upgrade is still pending or complete.
Hi all, update for 12/17/21 9 AM EST.
Upgrades for the impacted AWS service are still pending completion from the AWS team.
Hi all, update for 12/17/21 4:30 PM EST.
Upgrades for the impacted AWS service are still pending completion from the AWS team.
Hi all, update for 12/18/21 6:00 PM EST.
Upgrades for the impacted AWS services have been completed.
I am looking for jobs that l m engineering
Please sign in to leave a comment.