Vulnerability Management

Vulnerability management in IT operations is the work of getting security weaknesses across systems, applications, and infrastructure fixed: assigning each finding, tracking it to closure, and meeting remediation timelines. Scanners find the weaknesses; the operations team has to resolve them, and that is where most programs lose track. In SmartSuite each finding is a record linked to its asset and owner, with a due date and a task, so what needs fixing and who owns it is visible on one dashboard.

Findings are imported from scanners and security tools by CSV, through the REST API, or by webhook into one findings table, and matched to assets by hostname or identifier. Each finding carries its severity, affected system, and owner from the linked asset. Repeat imports update existing findings rather than duplicating them, so the table reflects the current scan.

Priority is a formula on the finding that combines scanner severity with the linked asset’s criticality and exposure, so an internet-facing production system outranks a test server with the same CVSS score. Views sort the queue by that priority. Teams work from the top of the list rather than from the scanner’s raw order.

An automation assigns each finding to the owner of its asset and creates the remediation task, whether patching, a configuration change, or a system update. The task carries the due date, and comments on the finding keep the discussion with the record. The finding closes when the task completes and the next scan no longer reports it.

Findings link to the same asset records that the Service Desk & Request Portal and IT Incident Management use, so a vulnerability can open a change request or an incident with the context attached. Remediation tasks appear in the teams’ existing queues. Vulnerability work is scheduled alongside the rest of operations instead of in a separate tool.

Remediation targets are set by severity, and a formula field computes each finding’s due date and days remaining from its detection date. Automations notify the owner as the date nears and escalate past it. Dashboards show the share of findings resolved within target by team and severity, so leads see where timelines slip.

Yes. Large scan volumes are handled by importing findings into one table and working from filtered views, so teams see their own assets and the priorities that matter rather than the raw list. Permissions limit each team to its systems, and rollups keep totals current at the environment level. Adding a data center or business unit means importing its scans into the existing table.

Security improves because findings are assigned, due-dated, and tracked to closure instead of sitting in scan reports. Operations improves because remediation runs through the same queues and assets as the rest of IT work. Over time, dashboards show fewer open critical findings and faster closure, and the trend is the evidence of a better security posture.