Forum Discussion
Red Hat: Custom RPM Repository Handling Improvements...
Red Hat: Custom RPM Repository Handling Improvements
Summary
Users with custom Red Hat repository naming conventions in their enterprise can now upload a custom mapping file in json format that maps custom RPM repository relative URLs to the official Red Hat counterparts for the purposes of vulnerability scanning.
Problem
Many Red Hat and Tenable customers utilize custom repository configurations and/or mirrors. In these cases, where neither the configured repository label or URL match Red Hat’s official mapping, Tenable plugins are unable to determine what software updates are available to the scan target. This can result in an increased number of potential false positive findings for Red Hat Local Checks.
Solution
With this update, we have introduced a method that allows users to upload a json file via their scan policy that maps their internal custom repository relative URL to the official Red Hat label and URL of the repository it mirrors. To upload this json file to your scan policy, go to “Settings > Advanced > Vulnerability Options > Custom Red Hat Repository Mapping” and click on the “Add File” link.
For a more detailed overview of how this works in practice, please refer to the following user guide: How Red Hat Local Vulnerability Checks Use Repositories To Determine Scope
Impacted Plugins
- All plugins in the Red Hat Local Security Checks family
- New plugin added: Plugin ID 233963, redhat_custom_repos.nasl
Updated Scan Policy Templates
- Nessus Scanner
- Advanced Scan
- Advanced Dynamic Scan
- Basic Network Scan
- Nessus Agents
- Advanced Agent Scan
- Basic Agent Scan
Targeted Release Date
- Nessus and Tenable VM: Monday, April 14, 2025
- Tenable Security Center: TBC