SecPod

Learn Search

Search across all Learn content

← Back to Security Research
Strengthening Vulnerability Management Using the CMDB Feature in SanerNow

Strengthening Vulnerability Management Using the CMDB Feature in SanerNow

Feb 12, 2024By Koushik Kota2 min read

Configuration management database (CMDB) gives vulnerability management a strong underpinning. CMDB functions as a centralized database that contains information about software and hardware components used within the IT environment. It is one of the cornerstones of vulnerability management and makes the entire process more robust.  

You will be able to quickly identify asset classes having issues, phase them out, or substitute them to dampen the chaos caused by their errors, preventing the IT environment from spiraling out of control.  

SanerNow, your favorite fully integrated, continuous, automated vulnerability management platform, is now powered by the CMDB feature. How does it help you? With the SanerNow CMDB feature, you get a comprehensive understanding of the IT environment, risk assessments based on asset categories and their configurations, or keep a record of assets to ensure compliance. It strengthens your attack surface management efforts and improves IT operations.  

Here are a few good reasons why CMDB is needed for vulnerability management:

    • A well-maintained CMDB gives clarity to the IT environment, ensuring better visibility and transparency.  
    • Enables risk assessment efforts by identifying relationships between assets and configurations and finding any security gaps 
    • Get precise information about systems having certain types of vulnerabilities and ensure faster remediation efforts. 
    • Gain a comprehensive view of IT infrastructure and the interdependencies within. 

How to import CMDB data into SanerNow

Go to the Control Panel Page. Click the Manual Import button under the Discovery section on the Control Panel page. Click the Select File button on the right side and select the CMDB data file. 

When you successfully import the file, your screen will look like the one below.

In the above example, we’re importing 50 devices into SanerNow. After a successful import, all these devices will appear in the Unmanaged Devices section on the Managed Devices page.

How to export device data from SanerNow

SanerNow enables you to import device data into your CMDB by exporting it.

On the Managed Device page, click the All Devices button on the left side of the page. All the devices that have SanerNow Agent installed on them are listed.

Click the Export Devices button. You can choose the file format to be either CSV or JSON.

Once you confirm the file type for the export file, SanerNow will download the file on to your device.

Secure your device and your Organization with SanerNow.

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