At BuildOps, we’re committed to keeping our customers’ data secure. That’s why we’ve been working around the clock to address the vulnerabilities associated with Java’s Log4j code since the flaw was identified on Dec. 9.
When the Log4j vulnerability was announced, the BuildOps security team immediately launched an audit to determine how our systems might be impacted and developed a strategic proactive action plan to protect valuable user data.
Our survey of the BuildOps system concluded:
- BuildOps source code is not directly impacted by the Log4J vulnerability.
- One third party integration was identified as exploitable.
As a result of the survey, our security experts have patched the single third party app that was vulnerable and remain in very close communication with their security teams.
While the Log4j vulnerability is a major cybersecurity risk, we’re confident that BuildOps’ existing industry-leading security protocols offer significant protection against possible breaches related to this bug. In addition, our enhanced security strategy has established a new standard for cyber protection and directly addresses any and all BuildOps issues revealed by the global Log4j crisis.
We are continuing to monitor the situation and our systems. Our security platform is continuously evolving and will be updated to reflect any new developments related to Log4j.
Protecting customer data is our top security priority at BuildOps. You can trust us to follow the highest industry standards and best practices regarding the security of your information. Additionally, our policy of transparency and accountability means we’ll keep you updated on any developments or issues related to your confidential information.
If you have questions or comments about Log4j and how it impacts BuildOps, please contact us at email@example.com.