ControlUp’s Compliance Module provides app patching capabilities through a template-based system that defines which applications are scanned and managed for vulnerabilities. Currently, the accessible and comprehensive list of all applications available for patching is embedded within the templates section of the product. This means that users can view all the apps included in the scanning process only by reviewing the template library, as there is no separate, standalone database publicly exposed for all patchable apps.
Within the Compliance Module interface, users can also see information about specific applications on the per-device basis, including which devices did not scan a particular app. The apps page and issue page offer visibility into app scan status and vulnerability findings. However, the interface typically defaults to showing only applications with detected vulnerabilities or issues. For example, if an organization has no vulnerabilities reported for Google Chrome, that app will not be visible by default on the app page. This design can make it challenging to review the complete set of applications that can potentially be patched if no issues currently exist.
Recognizing this limitation, the ControlUp team is developing a new feature aimed at broader visibility, which will enable users to see all issues and applications regardless of current vulnerability status. This enhancement will also provide detailed insights into the number of devices that have scanned each app and flag those that have not been scanned, offering more comprehensive monitoring and management of application patch compliance.
For organizations intending to proactively configure and patch applications before any security vulnerabilities (CVEs) are detected, the current approach is to leverage templates that cover all common or commodity applications. Operators may consult the templates to ensure coverage and discuss with stakeholders about the included applications. Until the new feature is released, users interested in a full, easily accessible list of all potential patchable applications will need to rely on the template definitions and usage in their environments.
For the most up-to-date information about the Compliance Module templates and app patching, users can refer to ControlUp’s official documentation at https://docs.controlup.com and keep an eye on announcements for new features that expand app visibility and management.
Read the entire ‘Understanding Application Visibility and Template Use in ControlUp’s Compliance Module for Patching’ thread below:
Good day!
Is there a database we can access where we can see which apps are available for patching with the compliance module. I understand that in the template section I can see which apps are scanned on the devices. But is there a list of all apps?
Hi Arjan,
As far as I know, the template is the only accessible library to the available apps.
Tagging and to keep me honest here.
The full list of apps is in the template page
In our apps page toy can see on each app which devices didn’t scanned this app
Also in issue page.
But in default we are showing only effected apps so if org don’t have any vulnerabilities on google chrome for example you won’t see it in the app page.
We are working now on a new feature to see all the issues ( and I think the apps as well ) and per issue we will presented how many devices scanned and which device didn’t scanned
Thanks for the insights. We are leaning towards using templates for all commodity apps for automatic patching. But we also would like to configure apps even though they are not yet affected by CVE’s. There for a complete list would be preferred so we can discuss with our customers if ‘all’ apps are covered.
Continue reading and comment on the thread ‘Understanding Application Visibility and Template Use in ControlUp’s Compliance Module for Patching’. Not a member? Join Here!
Categories: All Archives
