SBN CyberSaint’s Response to the Log4j Vulnerability

Members of the CyberSaint Community,

My name is Padraic O’Reilly, the Chief Product Officer of CyberSaint. In light of the impacts of the Log4j vulnerability on the greater digital business ecosystem, I thought it most effective to pen an open letter to our community members. As a cyber and IT risk management company, we take vulnerabilities like Log4j very seriously and want to address concerns regarding its impact on CyberSaint.

What is Log4j?

Log4j is a ubiquitous open-source Java-based ​​logging utility widely used by enterprise applications and cloud service providers. The ​​Cybersecurity and Infrastructure Security Agency (CISA) discovered a serious vulnerability in Log4j. The vulnerability was scored a 10 by NIST, making it a critical issue to services that use Java and can afford hackers a method to gain high-level access to systems.

Does it affect CyberSaint?

Our solutions are not affected by the security vulnerability described in CVE-2021-44228. While we do employ Java, we do not use the Apache Log4j library in any of our dependencies.

What has CyberSaint done?

We have taken the following steps:

  1. Manually check our dependencies and verify we do not have the affected log4j jar
  2. Run the CyberStrong docker image through scanners, which detect the affected log4j vulnerability
  3. Verify with our vendors that handle customer data whether they have been affected by the log4j vulnerability. So far none have been.

While we do not use the affected jar file, we routinely patch and update to the latest versions for all of our software components. We have found that current deployments of CyberStrong are not vulnerable and no action is required at this time. We will continue to keep up to date with the packages used within CyberStrong and the java version that we employ.

Next steps

The CyberSaint team continues to stay vigilant as new vulnerabilities emerge and ensure that customer and partner data remains secure in our products. We are committed to maintaining the highest level of security.

If you are a CyberSaint customer and have any further questions, please contact your CSM.

Thank you and happy holidays,

Padraic O’Reilly, CPO, CyberSaint

Members of the CyberSaint Community,

My name is Padraic O’Reilly, the Chief Product Officer of CyberSaint. In light of the impacts of the Log4j vulnerability on the greater digital business ecosystem, I thought it most effective to pen an open letter to our community members. As a cyber and IT risk management company, we take vulnerabilities like Log4j very seriously and want to address concerns regarding its impact on CyberSaint.

What is Log4j?

Log4j is a ubiquitous open-source Java-based ​​logging utility widely used by enterprise applications and cloud service providers. The ​​Cybersecurity and Infrastructure Security Agency (CISA) discovered a serious vulnerability in Log4j. The vulnerability was scored a 10 by NIST, making it a critical issue to services that use Java and can afford hackers a method to gain high-level access to systems.

Does it affect CyberSaint?

Our solutions are not affected by the security vulnerability described in CVE-2021-44228. While we do employ Java, we do not use the Apache Log4j library in any of our dependencies.

What has CyberSaint done?

We have taken the following steps:

  1. Manually check our dependencies and verify we do not have the affected log4j jar
  2. Run the CyberStrong docker image through scanners, which detect the affected log4j vulnerability
  3. Verify with our vendors that handle customer data whether they have been affected by the log4j vulnerability. So far none have been.

While we do not use the affected jar file, we routinely patch and update to the latest versions for all of our software components. We have found that current deployments of CyberStrong are not vulnerable and no action is required at this time. We will continue to keep up to date with the packages used within CyberStrong and the java version that we employ.

Next steps

The CyberSaint team continues to stay vigilant as new vulnerabilities emerge and ensure that customer and partner data remains secure in our products. We are committed to maintaining the highest level of security.

If you are a CyberSaint customer and have any further questions, please contact your CSM.

Thank you and happy holidays,

Padraic O’Reilly, CPO, CyberSaint

*** This is a Security Bloggers Network syndicated blog from CyberSaint Blog authored by Padraic O'Reilly. Read the original post at: https://www.cybersaint.io/blog/cybersaints-response-to-log4j