This situation is common for many SecOps teams, but it might expose organizations to greater risk. They move on to other important issues, and new patches are rarely considered until next month’s release is out. The patches are included in the vulnerability management cycle and that’s about it. They spend a few minutes gathering intel and perhaps a few more minutes figuring out which patches should be prioritized based on your organization’s needs.
Imagine this scenario: Your IT staff, pressed for time, checks for patches once every month after the Microsoft Patch Tuesday release.
