01-10-2022 09:31 AM
Each year during holidays, management has deployment of signature updates (VDB & VRT) in our Firepower setup on hold (Change Freeze) due to limited team members on hand in case of issues. We recently deployed VDB update 350 to the FMC but then noticed it didn't need to be updated to all our managed FTD devices which was very strange so we didn't bother pushing VDB 351.
So our question is, is the VDB tied to which VRT is installed on the FTD devices and since our VRT hasn't been updated recently is that why VDB isn't being updated on the FTD? For instance, the current Snort rule installed on FTDs is 2021-12-15-001-vrt and VDB is version 349 even though the FMC was updated to VDB 350. We are running FMC & FTD at 6.7 version.
Thx in advance for any assistance provided.
Solved! Go to Solution.
01-10-2022 06:59 PM
The VDB (Vulnerability Database) and Snort Rule Updates (SRU) are not generally tied together or dependent on one another.
01-10-2022 06:59 PM
The VDB (Vulnerability Database) and Snort Rule Updates (SRU) are not generally tied together or dependent on one another.
01-24-2022 10:38 PM
Thx Marvin for the response. Come to find out, Cisco pulled back VDB 350 due to issues and was able to upgrade to VDB 351.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide