Any discrepancy in CVE references are typically resolved the same day. Mappings are provided by Tenable’s Research team and audited both internally and from customer product use. Tenable only include links to the CVE identifier. Tenable products do not include CVE entry content. Map Currency Update Mechanism ĭescribe the mechanism used for reviewing CVE for content changes (required): During the plugin authoring, CVE identifiers are added to the plugin if the identifier description matches the vulnerability check. Tenable’s Research team creates Nessus plugins (vulnerability test scripts) to test for a specific issue or set of issues. Map Content Selection Criteria ĭescribe the criteria used for determining the relevance of a givenĬVE Identifier to your Capability (required): This document details how Tenable updates CVE, CVSS, XCCDF and many other standards. Tenable describes its CVE usage, along with other standards, in a document available on its Support Portal titled "Standards Declarations". Should expect an update of your capability’s mappings to reflect newly Map Currency Update Time ĭescribe how and where you explain to your customers the timeframe they ![]() Tenable only includes links to the CVE identifier. ![]() To reflect new CVE versions and describe your approach to keeping reasonablyĬurrent with CVE versions when mapping them to your repository (required): Indicate how often you plan on updating the mappings If new, missing or corrected CVE entries exist, we modify our content accordingly. Tenable synchronizes CVE entries with National Vulnerability Database information daily. The most recent CVE version used to create or update its mappings (required): Mapping Questions Map Currency Indication ĭescribe how and where your capability indicates
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |