Advisory Database Unresponsive Hosts/Outdated Repositories
Symptoms
Section titled “Symptoms”The Advisory Database managed by the Vulnerability Research Team communicates with many hosts to pull down third party advisories and data. These are almost always updated every day/week. This rule triggers if we are unable to communicate or get fresh information from one of these third parties.
Possible checks
Section titled “Possible checks”- View the URLs and resources in the advisory_db.toml and ensure each resource is up and available.
- Checkout each repository in git and ensure commits have been made with in the allowed timeframe (
git log '--pretty=%aD' | head -n 1) - Check each URL is resolvable
Resolution
Section titled “Resolution”If for some reason the git repository hasn’t been updated, consider changing the must_update_within = "120h"
toml configuration to a longer time frame.