Vigiles subscriptions are annual, with clear pricing and no hidden extra costs.
Learn more about Timesys Vigiles Vulnerability Management Suite
Compare Vigiles Versions
Free, basic version providing
CVE monitoring for a single SBOM
The Free version’s CVE monitoring upgraded to unlimited SBOMs, plus collaboration tools for CVE triage and mitigation, advanced filtering, detailed notifications, advanced reporting tools, patch notification & Management features, links to related Linux kernel patches, and OSS fixed version notifications.
All features of Free and Prime, with single sign-on compatibility, powerful group administration functionality, role-based access control, and on-premises hosting with remote CVE database updates.
CVEs affecting your software components
List of the Common Vulnerabilities & Exposures (CVEs) specific to your software components in your SBOM
Push notifications of vulnerabilities
Notification of new CVEs that are associated with the software components in your loaded manifest
Track multiple Software Bill of Materials (BOMs)/manifests
Ability to load product manifests listing your software components and versions
On-demand CVE report generation via Web
Notifications of vulnerabilities available on-demand in multiple formats
On-demand CVE report generation via command line
Notifications of vulnerabilities available on-demand in multiple formats
CVE summary by severity, status, and software package
View summary counts of Common Vulnerabilities & Exposures by the severity score derived by the Common Vulnerability Scoring System as listed in the National Vulnerability Database (NVD) maintained by the US Government’s National Institute of Standards and Technology. Also includes ability to view CVEs by the status of resolution in your manifest and by those specific to your software components.
Build system support: Yocto, Buildroot, PetaLinux, Wind River Linux, PTXdist, OpenWrt, and Timesys Factory
Ability to upload Yocto manifest (generated by meta-timeys), Buildroot manifest.csv, OpenWrt manifest, or Factory workorder from command-line and web for CVE scanning
Upload your Software BOM or create one using Web wizard
Upload open source component lists used by applications and BSPs for CVE scanning. Also includes ability to create custom software component lists in order to generate a CVE report and receive security notifications independently of any build engine.
Software License information (Yocto and Buildroot only)
View summary of CVEs and license stats for each package.
Filter based on Component or Status
Filter CVEs by those specific to your software components or by the status of resolution in your manifest.
CVE search tool for Timesys curated CVE database
Ability to search for CVEs by package name and version, or by ID
CVE report history with CVE trend plot
View previously generated reports and track how threats in your build have changed over time
CVE report sharing
Share a view-only version of the latest CVE report via a link. This is particularly useful when you want to quickly share a report with others who might not be on the same team.
Export your Software Bill of Materials (SBOM) in SPDX format
SPDX format is an international open standard for SBOMs that communicates information including components, licenses, copyrights, and security references. This feature is helpful for tracking packages, reporting, audits, and streamlining and improving compliance.
Early CVE notification
Notification of newly discovered CVEs that are not yet in the NVD data base
Team sharing and CVE mitigation collaboration tools
Vulnerability management workspace and tools for you and your team members to comment, annotate, and collaborate on triage and mitigation of each vulnerability listed in your manifests.
Continuously track specific issues and CVE status changes
Continuous tracking of vulnerabilities based on resolution status for your manifests.
Integration with Jira to further streamline vulnerability issue tracking and management
Ability to create/add an issue per CVE in a Vigiles report, with issues being tied to the manifest.
Whitelist already reviewed CVEs to streamline reviews
Ability to hide CVEs that are already being addressed so as to simplify reports, collaboration and mitigation
Filter reports by severity (CVSS) score or attack vector
Filter Common Vulnerabilities & Exposures by the severity score derived by the Common Vulnerability Scoring System as listed in the National Vulnerability Database (NVD) maintained by the US Government’s National Institute of Standards and Technology or by the technique by means of which unauthorized access can be gained to a device or a network. Also includes ability to view CVEs by the status of resolution in your manifest.
Software BOM/Manifest editor and revision management
Add packages, modify package names or versions for Buildroot, CSV, and Yocto SBOMs/manifests, and modify licenses for Buildroot and Yocto SBOMs/manifests. Saving creates new SBOM/manifest in the same product as the previous version with the changes applied.
Download reports in different formats
Ability to export reports in a variety of formats
Comparison of changes between builds/releases (SBOM/manifest difference)
Quickly generate reports and bulletins to document security issues and vulnerability status on releases for submission to customers and regulatory authorities.
Comparison of reports for new and changed CVEs
Comparison of any two scans to view new, removed, and status changed CVEs
Custom vulnerability score/prioritization and filtering
Assign a custom severity or priority value to each CVE (0.0 to 10.0). Sort and filter based on the custom score, and easily prioritize CVEs based on custom metrics.
Reference links to available patches, mitigation, and exploits
Links to the available patch, workarounds for mitigation when a patch is not available, and for recreating the CVE exploit for testing.
Link to mainline kernel fix commit for Linux kernel CVEs
A direct link to the CVE fix in the mainline kernel
Minimum kernel version with a fix for a kernel CVE
Identification of the minimum version of a kernel with the CVE fix
Filter reports based on kernel and U-Boot configuration
Ability to filter vulnerabilities based on the kernel configuration and U-Boot configuration in your loaded product manifest
Suggested fix for OSS CVE remediation
Identifies a version of software where the CVE is fixed and/or provides links to user space patches where available
Access to free Vigiles Quick Start Education Program
A complimentary service for Vigiles customers and Vigiles Prime trial users that gets your vulnerability management process up and running quickly.
Companies that use identity management systems can leverage SSO and have employees sign in to Vigiles using their corporate identity.
Collaborate more easily within teams while controlling access on an as needed basis.
Role-based access control
Utilize an expanded user role set that includes admins, maintainers, developers, and guests.
What is the difference between Vigiles Free, Prime and Enterprise?
Vigiles Prime provides vulnerability monitoring and more detailed reports for an unlimited number of product manifests, along with collaboration and communication tools to enable your team to analyze and work on mitigation for vulnerabilities. You also get Patch Notification & Management features, identifying patches and minimum versions to secure the software components that are identified in your manifests.
Vigiles Enterprise gives you single sign-on capability, an expanded group control function to more easily collaborate within teams while controlling access to work, and expanded role-based access control. All hosted on-premises so you can keep your triage efforts inside of your own network.
How does Patch Notification & Management in Vigiles Prime help with vulnerability management?
By identifying patches and minimum fixed versions, the patch management features of Vigiles Prime slash the amount of time your team spends on investigating identified vulnerabilities and exploring the mitigation steps to fix them.
Without Vigiles Prime patch management, your triage and mitigation activities will include identifying each component supplier and researching which version of a component has an available fix for a given vulnerability, if one is even available.
In contrast, Vigiles Prime patch management will automatically notify you of a patch associated with a given vulnerability for your specific components. Vigiles Prime will give you a direct link to the download for the patch. Further, Vigiles Prime will provide you with details on the minimum versions of libraries or packages and kernels that address the identified vulnerability.
Our analysis shows that Vigiles can cut your vulnerability identification and mitigation process cycles by 90 percent when compared with manual detection, investigation, and mitigation.
What are Triage Collaboration and Mitigation Tools in Prime and Enterprise?
These tools enable you and your team members to annotate, comment on, whitelist and otherwise collaborate on the vulnerabilities identified in your loaded product manifests. These communications tools are the foundation of highly efficient security vulnerability management workflows and risk mitigation processes.
For example, a team assigned to review a set of vulnerabilities might assign some team members to conduct impact analysis. Those team members can communicate quickly and easily about their evaluation of the security risks posed by specific vulnerabilities.
Other members may focus on high severity vulnerabilities to investigate expedited mitigation options, sharing their findings to weigh options and accelerate the response and fix.
Throughout these processes, some vulnerabilities may be whitelisted, which means they are tagged as acknowledged and in process or fixed. That way they do not clutter up the broader evaluation of inbound vulnerabilities or the mitigation workflows.
Along with flexible filtering, dashboarding, and reporting features, these collaboration tools can significantly cut the time your team spends on understanding the impact of a vulnerability and fixing it.
How do I upgrade to Prime?
Is Vigiles open source?
Vigiles is divided into two parts.
One part of Vigiles collects the software manifest from a Yocto project and is licensed under MIT license with Timesys copyrights (see: https://github.com/TimesysGit/meta-timesys/tree/zeus).
The other part consists of the Vigiles scanner, backend database and user interface. This part of Vigiles is a Timesys proprietary product.
Does Vigiles only support Yocto or does it support other build systems? Are custom Linux kernel, crosstools and bootloaders also supported?
Vigiles supports a number of build systems, including: Yocto, Buildroot, PetaLinux, Wind River Linux, PTXdist, OpenWrt, and Timesys Factory. And Vigiles can be used with other build systems as well.
Using the Vigiles UI, you can upload software manifests from Yocto, Buildroot and Factory. In addition, Vigiles supports .csv format, so you can generate a software manifest from any other build system and format it as a .csv spreadsheet that you can upload. We provide guidance on creating a Vigiles .csv manifest here: https://linuxlink.timesys.com/docs/wiki/engineering/VigilesCSV.
You can also create your software manifest from scratch entirely online using the Vigiles “Create Manifest” UI.
Can Vigiles be used with any BSP or processor?
As mentioned above, Vigiles is integrated with different build systems. As long as your build system or manual SBOM is used, it can track vulnerabilities with one caveat: Vigiles tracks processor vulnerabilities. So, if your processor or architecture has vulnerabilities tracked by NVD, Vigiles will track it.
Currently, we use Linux kernel 4.9 in our project. Can it be scanned using Vigiles or does the kernel need to be a newer version?
Yes, projects using Linux kernel 4.9 can be scanned for vulnerabilities using Vigiles. And projects using older versions of the Linux kernel can be scanned as well.
With older kernel versions, you should expect to see more vulnerabilities in the Vigiles report. In general, we recommend that our customers use a recent Long Term Support (LTS) version of the Linux kernel. Because security fixes get backported by LTS kernel maintainers, using a recent LTS version of the Linux kernel will allow you to leverage those backports in your BSP/product.
What is a product manifest?
A product manifest is the inventory of your product’s software components and the versions in your design, loaded into Vigiles for security monitoring.
Do I need to manually load my product manifest each time a report is generated?
Vigiles does not require you to upload the product manifest each time it is run. In a typical Yocto build environment, the Vigiles Yocto layer will extract the manifest from your source code.
How are Vigiles results presented? Are the reports exportable (json/xml) for integration into company-wide issue trackers?
Yes. The Vigiles results can be exported. You can export them as a spreadsheet or a PDF, so the results can be easily integrated into your own issue tracker.
In the upcoming Vigiles release, you will also have the ability to get reports via JSON directly in your build system. This will provide further integration into your company-wide issue tracker.
Is there a limit to the number of the projects you can have in Vigiles?
No. For a given CPU, there is no limit to the number of projects you and your team can set up in Vigiles.
How is Vigiles different from other vulnerability scanners including Black Duck?
Vigiles is best suited for embedded. Specifically, Vigiles:
- Tracks CVEs already fixed in Yocto/Buildroot, letting you/your team focus on vulnerabilities that need to be fixed.
- Enables up to 4x reduction in CVE review with kernel and U-Boot configuration-based filtering.
- Provides superior vulnerability reporting with fewer false positives.
- Provides links to patches and commits, reducing time to needed address/mitigate vulnerabilities.
- Features an advanced filtering capability, helping you/your team to prioritize and focus on only the vulnerabilities that matter.
In addition,Vigiles customers have access to the Timesys TRST Security team for help with any CVE questions as well as access to a Managed BSP Maintenance Service option for those who do not want to fix the vulnerabilities themselves.
Does Vigiles support Android security patches?
Vigiles is not fully enabled for Android yet. However, you can use Vigiles and BSP Maintenance to monitor CVEs and fixes, and for help with triaging the Linux portion of Android.
For the Android Open Source Project components from Google, use the security tracking bulletin from Google (https://source.android.com/security/bulletin).
Do Vigiles and Linux Test Project (LTP) overlap?
The two solutions do not overlap, but can be used together.
Vigiles monitors vulnerabilities for the entire Linux BSP including the Linux kernel, bootloader and userspace packages, and LTP helps with verifying/testing Linux feature functionality. Therefore, you can use Vigiles to identify CVEs and available fixes, and then once you and your team go through triaging and fix implementation, you can run LTP to verify Linux functionality.
Is it possible to run Vigiles on a device not connected to the Internet?
Vigiles does not interact with the target device.
Vigiles works by extracting package/version information from the build system Yocto/Buildroot) or by the user generating/uploading a Software BOM CSV file to Vigiles. Vigiles then compares the list of packages/versions against a Timesys-curated vulnerability database and generates a web report accessible only by the end user and/or user’s team.
Currently, Vigiles is a hosted/cloud only solution; we do not provide an on-premises version of Vigiles that can be on your network without internet access. However, we do plan to provide an on-premises version later this year.
What is Timesys Vigiles?
Vigiles is a software composition analysis and vulnerability management solution optimized for embedded Linux that tracks Common Vulnerabilities and Exposures (CVEs), providing end-to-end vulnerability management, while improving on the CVE data publicly available from the National Vulnerability Database (NVD).
How does it work? How does Vigiles determine which CVEs to report?
Vigiles pulls CVE information from National Vulnerability Database (NVD) every 24 hours.
For a particular CVE, there is a unique name for the specific software or hardware that is affected. This scheme is called Common Platform Enumeration (CPE), and it’s used for mapping a CVE to a product name and version. Most commercial and open source tools use CPE.
If this hardware or software CPE appears in a client’s Software Bill of Materials (SBOM), then Vigiles pulls the data for the corresponding CVEs. The SBOM is automatically generated for Yocto and Buildroot.
Of the approximate 350 new CVEs announced each week, is this just the number of CVEs reported against the Linux kernel mainline?
The approximate number of 350 vulnerabilities reported each week refers to all vulnerabilities reported in CVE tracking databases for all software.
On average, you should expect that approximately 10 CVEs/month will directly apply to your embedded Linux product. And many of these issues will indeed be reported for the Linux kernel itself.
Can you get false positives?
Tools relying on CPE data from NVD, like Vigiles, are still prone to missed CVEs, false positives (reported CVE is not applicable to the package/version), and reporting delays.
This can be due to CPE data quality issues (like incorrect product names or version information), incorrect SBOM information (name/version number), or delays in a CVE being published in the NVD.
Timesys takes a number of steps to improve coverage and reduce false positives; see the next question and answer for further details.
How does Vigiles filter out false positives?
Filtering out false positives begins with the Timesys TRST Security Team. The team uses in-house developed automation and some manual work to mark CVEs correctly in our in-house curated CVE database. This work, which involves fixing some of the issues typically encountered, such as version issues, LTS kernel minor release info, etc., enables us to host a curated CVE database that contains highly accurate CVE info.
Then, Vigiles relies on our curated CVE database during the scanning process. In addition, Vigiles takes into account any filters you may applied such as the Linux kernel configuration and U-Boot configuration filters, along with factoring in any CVE patches already applied, resulting in a highly accurate security vulnerability report.
How does Vigiles improve upon info from the National Vulnerability Database (NVD)?
Vigiles provides up to 40% accuracy improvement over the NVD with Timesys’ curated CVE/CPE database.
Timesys’ security team has error detection mechanisms in place via our Linux OS/BSP Maintenance service, customer feedback, and upstream Yocto patch submissions. Using this info, the security team manually analyzes incorrect CVEs and updates it in our systems. We also cross-verify our database with Upstream mailing list, issue trackers, security bulletins, Debian/Ubuntu/RedHat security trackers, SoC vendor advisories.
Additionally, we’ve created intelligent curation algorithms for the Linux kernel and u-boot that run on a nightly basis. We automatically update our curated database with fix commit and backports using git.
Finally, we minimize reporting delays. By augmenting our database with information from multiple feeds, we can notify our customers of CVEs not yet reported by the NVD — sometimes up to four weeks earlier!
Does Vigiles have a way to catch errors like typos or missing mappings?
If a package in the SBOM is not found in our database, we alert the user in the CVE report page. The customer can fix the package name or map it to our database using the override mechanism. The Timesys security team also periodically reviews and adds missing mappings. And finally, it allows users to include/exclude packages from auto-generated SBOMs, and override mapping.
However, Timesys cannot guarantee that Vigiles is entirely free from errors, defects, or bugs, currently known or unknown.
Can Vigiles be used to report vulnerabilities in userspace applications?
Vigiles tracks vulnerabilities for all software layers in a Linux BSP. This includes the bootloader, Linux kernel, drivers, userspace packages, and applications.
Vigiles does not scan your BSP source code for code injections. Vigiles reports on the version of individual software packages you are using in your BSP and a list of patches that are applied on top.
Therefore, if CVEs are reported against application software you’ve used, Vigiles will be able to provide you with information. However, if you are using an in-house developed proprietary application for which CVEs are not reported, Vigiles will not be able to provide any vulnerability information.
If we have made custom changes in the kernel driver, would Vigiles be able to report on related vulnerabilities?
Vigiles does not track custom changes to software at a source code level.
If you modify the driver before applying a CVE patch, you will have to adjust the CVE patch to apply on top of your changes. Therefore, it is recommended to first apply a CVE patch and then make customizations. This would possibly require adjustments to your customization patch.
What information is collected when I upload my product manifest for security monitoring?
Timesys Vigiles only collects package/recipe names, version, patches applied (if any), and build system version information. This information will only be shared with members of your team.
Timesys Vigiles does not require you to upload your product source code.
What does Timesys do with the information in my confidential product software manifest?
We currently don’t do anything with the customer information uploaded to Vigiles. Your product manifest(s) will remain in your Vigiles account for as long as you need.
When no longer needed, you can delete the information you’ve uploaded yourself or ask us to delete it for you.
What security measures has Timesys implemented to ensure my product software manifest does not get shared with other Vigiles users?
By default, all CVE links are private and are not accessible to other users based on login authentication.
What assurances can Timesys provide that my product software manifest information will not be hacked or otherwise leaked from Vigiles?
Timesys stores all manifest information in an encrypted disk.
How does Vigiles handle third-party source code that is included, but not shown in Yocto recipes? For example, QtWebEngine has Chromium source code included and hence is subject to the same CVEs as Chromium, with a number of proprietary patches. Will Vigiles report on these CVEs when including QtWebEngine?
If the Chromium CVEs are also marked for QtWebEngine, they will show up in the Vigiles report for the Qt package that contains QtWebEngine module. If a CVE is reported against Chromium but is not marked as applicable to QtWebEngine, Vigiles will not show it in the report.
Applicability of a CVE reported on one package to another requires engineering triaging. If maintainers of the Qt package do this, CVEs will be marked by them as applicable.
We provide a BSP Maintenance service where our engineering team does the triaging of CVEs. This service could be also used to triage Chromium CVEs for QtWebEngine.
How does the vulnerability report get updated to our project account in Vigiles? Does it update automatically or do we/does the developer need to update the report as necessary?
To obtain an updated Vigiles vulnerability report, you have several options including:
- You can push the software manifest to your Vigiles account every time you run a Yocto build or request a security report using YoctoBitBake commands. When you rerun the build on the same Yocto image, the software manifest can be updated in place. This way, if you add another package to your BSP, it gets reflected in the same product Vigiles report. Because Vigiles stores the older versions of the manifest, you can always go back to view and/or generate reports for older manifests.
- You can subscribe to notifications on new vulnerabilities reported against a manifest. Once a manifest is in Vigiles, you can choose to receive vulnerability notifications daily, weekly or monthly. Vigiles will automatically run a security scan and email you the information based on your cadence preference.
- You have the ability to upload either a new manifest or an updated version of a manifest at any time using the Vigiles UI.
Using Vigiles and this product model, who is responsible for fixing/mitigating a vulnerability?
Vigiles assists with the monitoring and tracking of vulnerabilities and available fixes.
The process of triaging identified CVEs and how they apply to your product, the decision to apply available fixes, the implementation of fixes, and the building and testing of the modified Linux product image is the responsibility of you/your engineering team. Additionally, suggested fixes, patch, and mitigation information is not verified by Timesys.
For those wanting to offload this task, we offer managed Linux OS and BSP Maintenance.
I already have Black Duck. Do I really need Vigiles too?
Black Duck is a good choice to identify and mitigate open source-related risks when all you have is end device binaries to work with. If you are using Yocto or Buildroot, then Vigiles leverages information about exactly what is being built (configurations, patches applied, etc.) to reduce false positives by 95% and reduce CVEs to analyze by 85% as compared to Black Duck. In short, Black Duck users add Vigiles to save many hours of work. Learn more here: https://timesys.com/solutions/vigiles-vulnerability-management/software-composition-analysis/
What about vulnerabilities not in the CVE dictionary?
Vigiles does not cover vulnerabilities that are not reported to or published by the CVE Numbering Authorities (CNAs), or “bug” fixes that were missed being identified as vulnerabilities. Additionally, it does not cover undiscovered vulnerabilities. In short, Vigiles is used for publicly known vulnerabilities.
To achieve the most comprehensive vulnerability data, Timesys recommends that you run static analysis tools, fuzzing tools, monitor mailing lists, issue trackers, and security bulletins / advisories.
How can I report an issue?
You can report an issue or submit feedback by creating a support ticket within Vigiles. Typically, issues are addressed within 72 hours. Once the issue is resolved, all Vigiles users benefit from it, so users are encouraged to report any issues. Additionally, issues can be reported to the NVD and/or MITRE.
Glossary of Terms
CNA: CVE Numbering Authorities are organizations from around the world that are authorized to assign CVE IDs to vulnerabilities affecting products within their distinct, agreed-upon scope, for inclusion in first-time public announcements of new vulnerabilities. (Source)
CPE: Common Platform Enumeration is a structured naming scheme for information technology systems, software, and packages. Based upon the generic syntax for Uniform Resource Identifiers (URI), CPE includes a formal name format, a method for checking names against a system, and a description format for binding text and tests to a name. (Source)
CVE: Common Vulnerabilities and Exposures
A vulnerability is a weakness in the computational logic (e.g., code) found in software and hardware components that, when exploited, results in a negative impact to confidentiality, integrity, or availability. Mitigation of the vulnerabilities in this context typically involves coding changes, but could also include specification changes or even specification deprecations (e.g., removal of affected protocols or functionality in their entirety). (Source)
A vulnerability that has been assigned a CVE identifier number is colloquially referred to as a CVE.
NVD: The National Vulnerability Database is the U.S. government repository of standards based vulnerability management data represented using the Security Content Automation Protocol (SCAP). This data enables automation of vulnerability management, security measurement, and compliance. The NVD includes databases of security checklist references, security-related software flaws, misconfigurations, product names, and impact metrics. (Source)