Posted June 17, 2022 by Charles Bevan ‐ 4 min read
LifeOmic had limited use of the affected software, none of our use was Internet-accessible, and based on all evidence from our extensive logs, LifeOmic was not compromised by the log4j vulnerability. We were aware of the issue within 12 hours of its public disclosure and had mitigated the small number of internal systems affected within 4 hours. We continue to monitor possible impact from vendors who rely on the affected software. For more information, email email@example.com.
Posted December 15, 2021 by Bishop Bettini ‐ 3 min read
LifeOmic is committed to open source, so we shared our quick-start guide to signing commits following a breach of the PHP source code repository. LifeOmic was not affected by this breach.
Posted April 2, 2021 by Bishop Bettini ‐ 2 min read