What is "Vulnerability Management"?
Vulnerability Management is a self-service feature in the Cognna Platform. Use Vulnerability Management to run your own vulnerability scans, monitor the health of your agents and scanners, review the vulnerabilities and software found across your assets, and export findings directly from the platform. Administrators can link agents and a network scanner, launch or schedule scans, follow each scan from start to finish, and share the findings as a technical CSV.
Core capabilities include:
- Endpoint Agent Onboarding: Link lightweight agents on workstations, laptops, and servers so they scan locally and report to the platform.
- Network Infrastructure Scanning: Deploy a dedicated on-premises scanner to assess switches, routers, firewalls, printers, and unmanaged subnets without installing anything on them.
- Vulnerability Discovery: Review every finding across your assets with severity, risk metrics, and host details.
- Software Inventory: See which applications and packages are installed, and on how many hosts.
- Scan Orchestration: Create, schedule, run, and monitor Agent scans and Active scans.
- Technical Export: Download granular findings as a CSV file for analysts and remediation teams.
Section 1: Prerequisites & Onboarding
Data reaches Vulnerability Management through two distinct deployment types. Choose the one that matches the assets you want to cover, or deploy both for full coverage. Complete onboarding before you create scans or review findings.
Endpoint Agent | Network Active Scanner | |
|---|---|---|
Purpose | Lightweight local agent for workstations, laptops, and internal servers. | Dedicated on-premises scanner for agentless network scanning. |
How to install & Guides | Settings > Vulnerability Management > Agent Configuration | Settings > Vulnerability Management > Network Active Scanner |
Note for Administrators & Owners: Downloading agent installers, retrieving linking keys, and configuring the network scanner are restricted to users with the Owner or Administrator role. The setup pages under Settings > Vulnerability Management are not visible to other roles.
A: Endpoint Agent Onboarding (Agent Configuration)
Agents are small programs installed on your endpoints. They scan the endpoint locally and send the results to the platform over an outbound connection. Once an agent is linked, it appears under Linked Assets and can be placed in an Agent Group that you target with an Agent scan.
Navigate to Settings > Vulnerability Management > Agent Configuration. The Vulnerability Management settings page has four tabs: Agent Configuration, Linked Assets, Agent Groups, and Network Active Scanner.
Vulnerability Management Settings Tabs:

1 - Agent Configuration : Retrieve linking parameters, download agent packages, and access OS-specific setup guides.
Navigate to Settings > Vulnerability Management > Agent Configuration
How to configure and link an Agent?.
The page is organized into two distinct sections:
1. Linking Parameters (Top Panel)
Note: Note: This process takes several minutes and is required before an agent will return results.
Contains your organization's core connection details and installer download link:
- Download page: Click the link in step 1 to access the installer repository.
- Deployment Method: Deploy the package manually on the target machine, or silently via enterprise tools such as Group Policy (GPO), SCCM, or MDM.
- Connection Parameters: Use the credentials displayed in step 3 during the setup process:
- Host: Your designated tenant manager domain (e.g., demo-manager.internal).
- Default Group: The default grouping container assigned to new agents (e.g., demo_group).
- Port: Target communication port (443).
- Linking Key: Your unique masked authentication key with a dedicated copy button.
2. Installation Guides (Bottom Panel)
Pro Tip: Whitelist Domain & Verify Connectivity (IT / Network Team):
Ensure your internal firewall and network proxy permit outbound DNS resolution and HTTPS traffic on Port 443 to your assigned host:
Domain: <HOST_DOMAIN> (e.g., id-vm.prod.cognna.com or your assigned manager address)
You can verify reachability before linking by running:
- Windows (PowerShell):Test-NetConnection -ComputerName <HOST_DOMAIN> -Port 443
- Linux / macOS (Terminal):nc -zv <HOST_DOMAIN> 443
(or curl -kIv https://<HOST_DOMAIN>:443)
Install and Link Agent
Under Installation Guides, select your target operating system tab (Windows, Linux RPM, Linux DEB, or macOS) to display its platform-guided steps.
Across all operating systems, deployment follows three basic stages:
- Install Package: Run the installer package on the target machine (via GUI wizard on Windows/macOS, or package manager on Linux).
- Link Agent: Enter the required parameters in the configuration window or terminal:
- Key (Required): Your linking key copied from the top panel.
- Server (Required): Your host address and port (xxxx.cognna.com:443).
- Groups (Required): The target agent group name.
- Start Service: Verify the agent service is running (starts automatically on Windows/macOS, or via systemctl on Linux).
Pro Tip:
To verify that the agent is actively running and properly linked directly from the endpoint's terminal:
- Windows (PowerShell as Administrator):
- Check service status: Get-Service -Name "Tenable Nessus Agent"
- Check linking status: & "C:\Program Files\Tenable\Nessus Agent\nessuscli.exe" agent status
- Linux (Bash as Root):
- Check service status: systemctl status nessusagent
- Check linking status: /opt/nessus_agent/sbin/nessuscli agent status
- macOS (Terminal):
- Check service status:sudo launchctl list | grep tenablesecurity
- Check linking status: sudo /Library/NessusAgent/run/sbin/nessuscli agent status
3- Agent Groups: you can create Agent Groups to effectively manage manage the assets
Agent Groups control which agents a scan targets. Navigate to Settings > Vulnerability Management > Agent Groups.

1. Agent Groups: The tab where you organize the agents linked to your account. An agent can belong to any number of groups.
2. Search: Locates a group by its name.
3. + New Group: A button to create a new group.
4. Name: The group name. The Default badge marks the permanent baseline group that automatically receives any newly linked agent when no group is specified. This group is permanent and cannot be deleted. .
5. Linked Assets: The number of agents currently in the group.
6. Last Modified: The date and time the group was last changed.
7. Action: Edit (pencil icon) or delete (trash icon) the group.
When you create an Agent scan, you select one or more groups as its targets, and every agent in a selected group runs the scan. Group endpoints in a way that matches how you scan them, for example by environment (Demo Production, Demo Staging), by operating system, or by business unit.
2. Linked Assets: Monitor connected endpoints, check real-time agent status (Online/offline/Unlinked ), and view host details.
Navigate to Settings > Vulnerability Management > Linked Assets.

1. Linked Assets: Displays the total number of connected assets against your allocated license quota (e.g., 131 out of 200)
2. Name: The hostname of the endpoint, for example DEMO-HOST-01, DEMO-STAGING-01, or DEMO-mac-01.
3. Status: The current state of the agent: Online, Offline, or Unlinked.
4. Platform OS: The operating system of the endpoint, such as Windows, Linux, or Darwin (macOS).
5. Groups: Groups: Displays the asset's groups. Every asset includes the Default group automatically; click (+) to assign additional groups previously created under Agent Groups.
6. Search assets: Allows you to search and locate endpoints by Hostname or IP address.
Note: Table Controls: Supports ascending/descending sorting via the arrows (⇅), as well as in-column search and checkbox filtering by clicking on the column header.
Agent Statuses
Status | Meaning |
|---|---|
Online | The agent is active and communicating normally. |
Offline | The agent is disconnected from the platform. |
Unlinked | The agent's connection to the manager was revoked. It cannot receive scan jobs or report results until it is linked again with a valid key. |
B: Network Infrastructure Scanner Onboarding (Network Active Scanner)
Nessus Network Scanner is deployed at the client site and managed by Cognna's Tenable Security Center (SC). The bash script provision_nessus_scanner.sh runs unattended (no user interaction) and covers installation, SC linking, logging, ports, SSL certificate authentication, and service startup.

This section provides the tools and instructions needed to deploy, configure, and manage on-premises active scanners within your local environment. It consists of three primary sub-tabs:
- Provisioning & Installation Guide: Step-by-step instructions, host prerequisites, and an automated deployment script to install and link the scanner unattended.
- Scanner Configurations: Settings for managing scanner authentication, host connection details, and communication status with the management platform.
- Scan Zones: Configuration area to define and assign local network ranges (subnets/IP pools) targeted for scanning by this scanner.
1. Provisioning & Installation Guide:

- Overview: Explains that the deployment runs unattended using an automated script (provision_nessus_scanner.sh) managed centrally via Security Center (SC).
- Prerequisites: Outlines host specifications (RHEL/EL9 with root access), outbound package download access, and inbound communication requirements on TCP 443.
- Installation Guide: Follow the on-screen steps in the platform to obtain the latest deployment script and files.
Pro Tip:
Once finished, verify the scanner status:
Service Status:
systemctl status nessusd → Expected result: active (running)
Port Listening Check:
ss -tlnp | grep -E ':443|8834' → Expected result: nessusd is listening on both ports (443 and 8834)
2: Scanner Configurations
Navigate to Settings > Vulnerability Management > Network Active Scanner > Scanner Configurations

Important: Do not copy and paste the certificate contents, as this corrupts the file. Download the .pem file directly to your machine and upload it.
Go to the Scanner Configurations tab and fill in the details:
- SSL Certificate: Upload /root/nessuscert.pem.
- Host: Enter the scanner's Public IP address.
- Port: 443 (Fixed default — cannot be changed).
- Click Save.
3: Scanner Configurations (Scan Zone)
Navigate to Settings > Vulnerability Management > Network Active Scanner > Scan Zones. Scan Zone ranges determine which zone covers a scan's targets when the platform distributes scans automatically.

1. Scan Zones: The list of zones, with a counter in the heading. Columns include Name, Owner, Created On, Last Modified, and Action.
2. Search by scan zone name: Locates a zone by its name.
3. + New Scan Zone: A button to create a new scan zone.
4. Action: Edit (pencil icon) or delete (trash icon) the zone.
To create a new scan zone:

1. Click + New Scan Zone.
2. Enter a Scan Zone name: A short name that describes the zone, for example Demo Core Network.
3. Enter a Description: An optional summary of what the zone covers.
4. Enter the Ranges: The IP ranges the zone covers, separated by commas, for example 192.168.1.0/24, 10.0.0.0/16.
5. Save the zone.
Important: Before initiating any scan, the Owner or Administrator must verify that all target devices have the Agent installed (under Linked Assets), or that the Network Active Scanner provisioning and setup steps in Section 1 are fully completed.
Section 2: Accessing Vulnerability Management
How to use Vulnerability Management?
To get started, navigate to Discover > Vulnerability Management from the top menu.

1. Vulnerability Management: The main workspace where you manage vulnerabilities, software, agents, and scans.
The page is organized into five tabs. It opens on the Vulnerabilities tab, and the active tab is highlighted in blue.
1. Vulnerabilities: The default view. It lists every vulnerability discovered across your assets, with details such as severity, affected asset, and discovery dates.
2. Software: Lists the software discovered on your assets and the number of hosts on which each item was found.
3. Agent scans: Where you create, run, edit, and delete scans that target Agent Groups.
4. Active scans: Where you create, run, edit, and delete scans that actively scan network targets through a Scan Zone.
5. Scan results: Shows the history of every scan that has run, with its status and duration. Open a scan to review its findings.
Each tab has its own search box and Date filter, and most tabs also include Export and Manage table columns.
Section 3: Vulnerabilities List
The Vulnerabilities tab lists every vulnerability discovered across your assets. The heading shows the total for the selected date range, for example Vulnerability list (9140).
![]()
1. Search by (Plugin ID, CVE, or Plugin Name): Locates a specific vulnerability by its Plugin ID, CVE identifier, or any part of the plugin name.
2. Export: Downloads the vulnerability list as a CSV file for external reports, audits, or offline analysis. CSV is the only supported export format.
3. Manage table columns (Icon): Customizes the table to show only the information most relevant to you.
4. Date: Filters the list to vulnerabilities within the defined date range, which defaults to Last 7 days or a custom range.
Below the controls, the table displays each discovered vulnerability. Click a row to open its full details. The table has the following columns:
1. Plugin ID: The unique identifier of the scan check that detected the finding.
2. Plugin Name: The name of the check or vulnerability.
3. Family: The category the plugin belongs to, such as Port scanners, Windows, or Service detection.
4. Severity: The urgency level of the finding: Critical, High, Medium, Low, or Info.
5. VPR: The Vulnerability Priority Rating, which indicates how urgently the vulnerability should be addressed.
6. EPSS (%): The estimated likelihood that the vulnerability will be exploited.
7. Asset: The name of the affected asset, for example DEMO-HOST-01.
8. IP Address: The IP address of the affected asset.
9. ACR: The Asset Criticality Rating, which shows how important the asset is to the business.
10. AES: The Asset Exposure Score, which reflects how exposed the asset is.
11. MAC Address: The hardware address of the affected asset.
12. First Discovered: The date and time the vulnerability was first detected.
13. Last Observed: The date and time the vulnerability was most recently detected.
Sorting and Filtering
![]()
1. Column Controls: Use the column headers to sort or filter the list, for example by Critical and High severity or by a specific Asset.
2. Sorting: Click the arrow icons next to a column header, such as Plugin ID, Plugin Name, Family, Severity, or Asset, to sort in ascending or descending order.
3. Value Filtering: Click a column header such as Severity or Asset to open a search and select menu. Choose one or more values, then click Apply. Click Clear All to reset the selection.
4. Date Range Filtering: Click a date column, such as First Discovered or Last Observed, to define a timeframe with the From and To selectors, then click Apply.
Pro Tip: Vulnerability scans often return a large number of informational findings. To focus on what needs remediation, click the Severity column header and uncheck Info, keeping Low, Medium, High, and Critical selected. Then click Apply to prioritize the actionable vulnerabilities.
Exporting the List (CSV)
Click Export above the table to download a technical CSV file with granular rows, such as CVSS scores and plugin details, which you can filter, sort, and process offline. Apply your Severity, Asset, and Date filters first so the file contains only the findings you plan to assign. CSV is the only supported export format.
Section 4: Vulnerability Details Workspace
Click a vulnerability in the list to open its details. The example below uses a Critical kernel finding on a Linux host.

1. Header & Severity: Shows the plugin name and Plugin ID, with a Severity badge such as Critical, High, Medium, Low, or Info.
2. Synopsis: A short, one-line summary of the issue.
3. Description: A fuller explanation of the vulnerability, the affected component, and why it matters.
4. Steps to Remediate: The recommended fix. For the Critical kernel finding, the steps direct you to update the affected kernel packages to the patched release and restart the host.
5. Plugin Output: The evidence returned by the scan check on the host. Use it to confirm the finding and see exactly what was detected.
6. Risk Metrics: The scores that help you prioritize the finding:
- ACR: The Asset Criticality Rating, which shows how important the affected asset is to the business.
- AES: The Asset Exposure Score, which reflects how exposed the asset is.
- VPR: The Vulnerability Priority Rating, which indicates how urgently the vulnerability should be addressed.
- EPSS: The estimated likelihood that the vulnerability will be exploited.
- CVSS: The Common Vulnerability Scoring System score, which rates the technical severity of the vulnerability.
7. Host Information: Details of the asset where the vulnerability was found, such as its name, IP address, and MAC address.
Pro Tip: Severity alone does not tell you what to fix first. Combine VPR and EPSS with the asset's ACR and AES to find findings that are both likely to be exploited and located on your most important or most exposed assets.
Section 5: Software Inventory
The Software tab is your software inventory. It maps the operating system packages and installed software discovered on your assets, so you can see which applications are present and how widely they are installed. The heading shows the total for the selected date range, for example Software list (11079).

1. Search by software name: Locates a specific application or package by its name.
2. Export: Downloads the visible software list as a CSV file.
3. Date: Filters the list to software within the defined date range.
4. Software list table: Displays each discovered software item. Use the arrows next to a column header to sort.
- Software Name: The name and version of the package.
- Hosts Count: The number of hosts on which the software was found.
- Created: The date and time the software record was created.
To see where a package is installed, click its Software Name. The Assets list panel opens on the right and shows the software name and the affected assets. Click Show more to load additional assets. The footer shows how many are displayed, for example Showing 50 of 97 assets. Click X to close the panel.
Pro Tip: Sort the table by Hosts Count to find the packages installed on the most hosts. A single vulnerable package that is widely installed affects many assets at once.
Section 6: Scan Orchestration (Agent Scans & Active Scans)
Agent Scans
Open the Agent scans tab to create and manage scans that run on your linked agents. The heading shows the number of scans for the selected date range, for example Agent scans (1).

1. Search by scan name: Locates a scan by its name.
2. Export: Downloads the visible list of scans as a CSV file.
3. Manage table columns (Icon): Customizes the table columns.
4. Date: Filters the list to scans created within the defined date range.
5. + New agent scan: A button to create a new agent scan.
6. Scans table: Displays each scan with these columns:
- Name: The scan name.
- Created: When the scan was created.
- Start Time: When the scan last started. It shows Never if the scan has not run yet.
- Schedule: How the scan runs, such as On Demand.
- Last Modified: When the scan settings were last changed.
- Owner: The user who created the scan, for example Security Analyst 1.
- Action: Run (play icon), edit (pencil icon), or delete (trash icon) the scan.
If no scans match the selected date range, the table shows No Data with the message "No records were found."
Pro Tip: If you do not see a scan you created, widen the Date filter. A scan can appear under Last 30 days but not under Last 7 days.
To create an agent scan:
1. Click + New agent scan.
2. Fill out the form:
- Name: A short name that describes the scan.
- Agent Group: The groups to include. Every agent in a selected group runs the scan.
- Scan Window: The period during which the agents in the selected groups are allowed to run the scan.
- Schedule: When the scan runs, for example On Demand.
3. Save the scan. It appears in the Agent scans table.
4. Click the play icon in the Action column to run it. Progress appears in the Scan results tab.
Active Scans (Network Infrastructure)
Use the Active scans tab to scan your network infrastructure through the Network Active Scanner you onboarded in Workflow B. An active scan reaches out to the IP addresses and ranges you choose. The tab has the same controls and table columns as Agent scans, with a + New Active Scan button. Navigate to Discover > Vulnerability Management > Active scans :
- + New Active Scan: A button to create a new active scan.
- Action: Run, edit, or delete a scan from its row.

Creating an Active Scan
- Click the + New Active Scan button.
- Fill out the New Active Scan form:


- Name: A short name that describes the scan. Required.
- Description: An optional summary of the scan, up to 500 characters.
- Scan zone: The network zone the scan runs from. Select a zone you created under Scan Zones. Required.
- Targets: The IP addresses or CIDR ranges to scan. Targets must fall within the selected scan zone's ranges. Required.
- Max scan duration (Hours): The longest time the scan is allowed to run. The default is Unlimited. Required.
- Inactivity timeout duration (hours): How long the scan waits without activity before it stops. The default is 12 Hours. Required.
- Schedule: When the scan runs. The default is On Demand. You can also run it on a daily, weekly, or monthly basis. Required.
- Create scan: Saves the scan. Click Cancel to close the form without saving.
The new scan appears in the Active scans table. Use the Action column to run (play icon), edit (pencil icon), or delete (trash icon) the scan.
Pro Tip: Use Max scan duration (Hours) to keep a scan from running into business hours or a blackout window. Set a limit for scans of large ranges instead of leaving the default Unlimited.
Section 7: Scan Results
The Scan results tab is the audit log of every agent and active scan that has run. The heading shows the total, for example Scan results (27).

1. Search by scan name: Locates a scan by its name.
2. Status filters: Narrow the list by scan status, for example Completed, Failed, or Stopped.
3. Manage table columns (Icon): Customizes the table columns.
4. Date: Filters the list to scans within the defined date range.
5. Scan results table: Displays each scan run with these columns:
- ID: The unique number of the scan run.
- Scan name: The name of the scan. Click it to open the scan details.
- Type: The kind of scan, either Agents or Active.
- Scanned IPs: The number of IPs scanned out of the total targeted, for example 107/127.
- Start Time and Finish time: When the scan started and ended. Finish time shows N/A while the scan is running.
- Duration: How long the scan ran.
- Status: The completion state of the run, such as Running, Completed, or Error.
- Action: A stop button appears for scans that are running.
Scan Details
Click a completed scan's name to open its details page, which lists all the vulnerabilities discovered by that scan.

1. Scan summary: The header shows the scan name with its Status, ID, and Type, followed by Scanned IPs, Start time, Finish time, and Duration.
2. Search, Export, and Manage table columns: The controls above the table work as on the main page. Export downloads the current view as a CSV file.
3. Scan results tabs: Switch between four views. The number next to each tab is its total, such as Vulnerabilities (7008).
- Vulnerabilities: The vulnerabilities found by this scan, with the same columns as the main Vulnerabilities tab.
- Software: The software detected by this scan.
- Remediations: The recommended fixes for the findings.
- IP Summary: An overview of each scanned asset.
Remediations Tab

1. Steps To Remediate: The action to take, such as updating a package or upgrading a product.
2. Risk Reduction: The percentage of overall risk the fix removes.
3. Hosts Affected: The number of hosts the fix applies to.
4. CPE: The platforms and products affected. Click Show More to see the full list.
5. Vulnerabilities: The number of vulnerabilities the fix resolves.
6. Vulnerability (%): The share of all vulnerabilities in the scan that the fix resolves.
7. Score: The priority score of the remediation.
8. CVEs: The number of CVEs the fix addresses.
IP Summary Tab

1. Asset name: The name of the scanned asset, for example DEMO-HOST-01.
2. IP address and MAC address: The network identifiers of the asset.
3. ACR: The Asset Criticality Rating.
4. AES: The Asset Exposure Score.
5. Score: The overall risk score of the asset.
6. Total Vuln.: The total number of vulnerabilities found on the asset.
7. Vulnerabilities distribution: A severity bar showing the number of Critical, High, Medium, Low, and Info findings for the asset.
Pro Tip: Start with the Remediations tab and sort by Risk Reduction to apply the fixes with the biggest impact first. Use IP Summary to find the assets with the most Critical and High findings.
Exporting Scan Data (CSV)
Use Export on the scan details page to download granular data from the tab you are viewing (Vulnerabilities, Software, Remediations, or IP Summary). The Technical CSV is a detailed file for analysts and remediation teams, with rows such as CVSS scores and plugin details that you can filter, sort, and process offline. CSV is the only supported export format.
Pro Tip: Apply your Severity, Asset, and Date filters before you click Export, so the CSV contains only the findings you plan to hand to the remediation team.

