SecPod

Learn Search

Search across all Learn content

← Back to Security Research
“What’s the Proof?” The Most Frequently asked Question by Security Teams, Now Answered by SanerNow

“What’s the Proof?” The Most Frequently asked Question by Security Teams, Now Answered by SanerNow

The odds are stacked against the IT team, who are at work daily to protect their organization against cyberattacks. It will make life easier for the security teams if they get clarity on the vulnerabilities of their IT environment. For instance, the name of the vulnerability, the associated CVE ID, ...

Feb 22, 2024By Koushik Kota4 min read

The odds are stacked against the IT team, who are at work daily to protect their organization against cyberattacks. It will make life easier for the security teams if they get clarity on the vulnerabilities of their IT environment. For instance, the name of the vulnerability, the associated CVE ID, and the exact location on which the vulnerability resides.

However, IT teams need proof of why these vulnerabilities were detected as vulnerable, and the reasons need to be represented in an insightful way for them to comprehend and act.  

The Proof of Detection feature in SanerNow does just that. It offers deeper insights into vulnerabilities and misconfigurations, including clarifying where they are located and why they were detected as vulnerable on the devices. The feature clearly represents the vulnerability detection summary for easier understanding of vulnerabilities and misconfigurations with obvious evidence.

This evidence helps IT teams know the nature of vulnerabilities and misconfigurations and prioritize remediation efforts to reduce the attack surface. They will be able to accurately prioritize vulnerabilities based on risk and contextualize the severity of the vulnerability.  

Let’s see the Proof of Evidence in action. 

Viewing Proof of Evidence for Vulnerabilities Detected on Devices

SanerNow’s Proof of Evidence feature provides you with a crystal clear view of the vulnerabilities found on your devices.

On the Individual Device page, SanerNow lists the vulnerabilities and misconfigurations detected on the device.

Click the + symbol to view the vulnerabilities detected in the Asset listed on the right side of the page.

Click the icon to view the Proof of Evidence for the vulnerability identified. A pop-up window containing all the evidence information for the selected vulnerability appears.

The pop-up window contains the following information:

  1. The CVE-ID associated with the vulnerability found on the device.
  2. The description of the check(s) SanerNow performed to find the evidence for the detected vulnerability. Here, you can find the actual value SanerNow found versus the expected value.
  3. The table on the right side of the page provides detailed information about the checks performed. Here, you need to focus on the information presented in bold.

Viewing Proof of Evidence for Misconfigurations Detected on Devices

Access the Individual Device page in SanerNow and select the device for which you want to find the Proof of Evidence for detected misconfigurations.

If you see an icon under the Risk Status column, it indicates a misconfiguration exists for the selected asset, and you need to take action to fix it. However, suppose you see a icon under the Risk Status column. In that case, it indicates that the misconfiguration for the selected asset has been taken care of, and no further action is needed.

IconDescription
This icon indicates that the asset is non-compliant, as SanerNow has detected misconfigurations that need to be fixed.
This icon indicates that the asset is compliant, as SanerNow has detected misconfigurations that need no fixing.

SanerNow Proof of Evidence provides evidence for both compliant and non-compliant risks.

Non-Compliant Risk

Click the icon to view the Proof of Evidence for the misconfiguration identified.

A pop-up window containing all the evidence information for the selected misconfiguration appears.

The pop-up window contains the following information:

  1. The CCE-ID associated with the misconfiguration found on the asset.
  2. The description of the check(s) SanerNow performed to find the evidence for the detected misconfiguration. Here, you can find the actual value SanerNow found versus the expected value.
  3. The table on the right side of the page provides detailed information about the check performed. Here, you need to focus on the information in bold or red font.

Compliant Risk

Click the icon to view the Proof of Evidence for the misconfiguration identified.

A pop-up window containing all the evidence information for the selected misconfiguration appears.

The pop-up window contains the following information:

  1. The CCE-ID associated with the misconfiguration found on the asset.
  2. The description of the check(s) SanerNow performed to find the evidence for the detected misconfiguration. Here, you can find the actual value SanerNow found versus the expected value.
  3. The table on the right side of the page provides detailed information about the checks performed. Here, you need to focus on the information in bold.

Schedule a Demo Right Away

We bet you found the Proof of Evidence feature quite compelling. Why not try it yourself? If you are a new customer, please email us at [email protected] to schedule a demo, and we will contact you.

Existing customers, please log in to your SanerNow web console to try the new Proof of Evidence feature. If you have any questions, please email [email protected] for any queries.

Featured Posts

Open WHIPSHOT and SLAPSHOT: Citrix NetScaler Zero-Days Exploited to Plant Root Web Shells and Internal Tunnels
WHIPSHOT and SLAPSHOT: Citrix NetScaler Zero-Days Exploited to Plant Root Web Shells and Internal Tunnels

CVE Research

WHIPSHOT and SLAPSHOT: Citrix NetScaler Zero-Days Exploited to Plant Root Web Shells and Internal Tunnels

Oct 1, 2026

Open OpenSSL’s DTLS State Handling Error Opens the Door to Heap Data Exposure
OpenSSL’s DTLS State Handling Error Opens the Door to Heap Data Exposure

CVE Research

OpenSSL’s DTLS State Handling Error Opens the Door to Heap Data Exposure

Oct 1, 2026

Open Patch Analysis & Exploitation Timeline: Critical WSO2 and Adobe Flaws Show 1-Day vs. 133-Day Exploitation Window , September 24, 2026 KEV Additions
Patch Analysis & Exploitation Timeline: Critical WSO2 and Adobe Flaws Show 1-Day vs. 133-Day Exploitation Window , September 24, 2026 KEV Additions

CVE Research

Patch Analysis & Exploitation Timeline: Critical WSO2 and Adobe Flaws Show 1-Day vs. 133-Day Exploitation Window , September 24, 2026 KEV Additions

Two critical vulnerabilities added to CISA KEV on September 24, 2026 reveal sharply different exploitation timelines. CVE-2026-71362 saw publicly documented exploitation roughly one day after Adobe's patch release, while CVE-2026-5430 had a 133-day vendor-remediation-to-observed-exploitation interval.

Oct 1, 2026

Open Patch Analysis & Exploitation Timeline: Same-Week KEV Additions, Year-Apart Patch Dates - Linux Kernel, September 18, 2026
Patch Analysis & Exploitation Timeline: Same-Week KEV Additions, Year-Apart Patch Dates - Linux Kernel, September 18, 2026

CVE Research

Patch Analysis & Exploitation Timeline: Same-Week KEV Additions, Year-Apart Patch Dates - Linux Kernel, September 18, 2026

Three Linux kernel vulnerabilities entered CISA’s KEV catalog on September 18, 2026, although their Linux 6.12 fixes were available 91–386 days earlier. This analysis separates patch availability, CVE publication, and known-exploitation status without treating KEV dates as first-attack dates.

Sep 28, 2026