# Tip Tuesday: Zero-Day Vulnerability Best Practices

**URL:** <https://community.sonatype.com/t/tip-tuesday-zero-day-vulnerability-best-practices/12674>\
**Category:** Sonatype Lifecycle & Firewall\
**Created:** [June 4, 2024, 3:09pm UTC](https://community.sonatype.com/t/tip-tuesday-zero-day-vulnerability-best-practices/12674 "2024-06-04T15:09:21Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![mfrost](https://yyz1.discourse-cdn.com/flex047/user_avatar/community.sonatype.com/mfrost/32/1701_2.png) [@mfrost](https://community.sonatype.com/u/mfrost)\
**Post date:** [June 4, 2024, 3:09pm UTC](https://community.sonatype.com/t/tip-tuesday-zero-day-vulnerability-best-practices/12674/1 "2024-06-04T15:09:22Z")

</div>

Welcome back to **Tip Tuesday** , where we share a helpful tip from our Sonatype team to help you find more success with Sonatype solutions.

**A zero-day event is when a previously unknown vulnerability is discovered in a popular open-source component. This is often before the project has a chance to release a fix; giving the community no time to react and little options to move forward.**

**[Read these best practices](https://help.sonatype.com/en/zero-day-vulnerability-best-practices.html) to determine your best defense against 0-day events.**

Let us know what you think below 👇