How does SecurityScorecard detect vulnerabilities?
SecurityScorecard scanning technology examines an organization's digital footprint (in this case, IP addresses) by assessing it for externally exposed products and services. This assessment runs a number of custom probes to identify products and services; it is a passive scan. We do not do intrusive scans to determine if a device or system is actually vulnerable.
We determine vulnerabilities by matching detected products from an outside-in assessment against a large, extensive vulnerability database of known CVEs.
SecurityScorecard raises an issue type in the platform when we can confidently determine that the product we observe is impacted by that vulnerability. Other vendors will sometimes raise a CVE even if it isn’t a direct match, but we detect it based on general product class; we consider this a Potential Vulnerability. We do the same for many products where we can’t get information 100% of the time; we raise a finding for potential vulnerabilities in the Application Security factor on any given Scorecard.
Further, not all products can be detected through outside-in scanning (e.g., local software or libraries within larger packages), and even when they are, the results may not provide enough information to confidently say it's an impacted version.
How does SecurityScorecard detect 0-days?
We often encounter 0-day vulnerabilities where information about an impacted product or service is limited. From a detection standpoint, if we can detect the product, it will either surface as a vulnerability finding in Patching Cadence automatically or fall under the Potential Vulnerability issue type in Application Security. Either Way, this process is fairly automatic if the product is detectable. When the product isn’t directly observable (as with Log4j, where it wasn’t a product but a software library used by products), we take additional steps to ensure coverage. The SLA for this is typically 24/48hrs to surface in the platform due to the additional work required. In these cases, as described above, we will research and identify additional ways to detect the product through metadata we collect via scanning (HTTP headers, titles, HTML body, banners, etc.). The end result is a finding as a Potential Vulnerability, unless we can 100% determine the version externally through metadata.
CVEDetails
SecurityScorecard has a Vulnerability Intelligence module that provides critical details about new vulnerabilities. This module covers vulnerabilities for products and services that are not detectable from outside-in.
This product lets you set up alerts to notify you as new vulnerabilities emerge. You can also access this module through the SecurityScorecard platform by going to Threat Intelligence > Vulnerability.