05.02 Recording a Vulnerability
Core SimpleRisk gets vulnerabilities in two ways, by importing a scanner export into the Vulnerabilities list or by recording one by hand as a risk. Here's when each fits, the conventions that keep hand-recorded vulnerabilities filterable, and when the Vulnerability Management Extra's scanner integrations are worth adding.
Why this matters
There are two ways a vulnerability gets into Core SimpleRisk, and picking the wrong one is how a risk register fills up with scanner noise. Scanner findings belong in the Vulnerabilities list: you import the scanner's export, SimpleRisk shows each vulnerability once with every asset it affects, and you triage the few that need risk treatment into the register (see Importing Scanner Exports). One-off vulnerabilities that no scanner reports, such as a penetration test finding, a vendor advisory for an appliance you can't scan, or a researcher's email, go straight into the risk register by hand. This article covers that second path, and how to tell which path a vulnerability belongs on.
The hand-recorded path works because it's low volume. Dozens of vulnerabilities a year, each one worth a risk-register entry on its own, are fine to submit through the standard form. Hundreds of findings a month are not; that's a scanner's output, and it belongs in an import, where triage keeps most of it out of the register.
One thing to plan for if you've been doing this for a while. Risks you recorded by hand before you started importing stay exactly as they are. An import never matches a vulnerability to a risk by itself; triage does that, and only when a risk's subject is exactly the vulnerability's title or when you attach the vulnerability to the risk yourself. When an import brings in a vulnerability you already track as a risk, use Attach to existing risk to tie the two together rather than creating a second risk.
Before you start
Have these in hand before recording vulnerabilities by hand:
- The Able to Submit New Risks permission on your account. The hand-recorded path uses the standard risk-submission form. (See Permission Reference.)
- An honest read on where the vulnerability came from. If a scanner reported it, import the scanner's export instead; that path keeps the per-asset detail, the EPSS and KEV signals, and the link back to the finding.
- A CVSS scoring method (v2.0, v3.0, v3.1, or v4.0) selected as the per-risk method for vulnerability submissions; use the version your scanner or the NVD entry reports. CVSS is one of SimpleRisk's nine built-in scoring methods (see Risk Scoring Methodologies) and is the right fit for vulnerability scoring because the upstream CVSS scores published in the National Vulnerability Database are already defensible.
- A documented internal convention for what to record. The discipline is to record only the vulnerabilities that genuinely need risk-register treatment: significant residual exposure, an accepted-risk decision, or a mitigation plan that needs cross-team coordination.
Step-by-step
Path A: Record a vulnerability via the standard risk-submission form
Each vulnerability becomes its own risk record.
-
Open the Submit Risk form. Sidebar: Risk Management → Submit Risk opens
/management/index.php. The full walk-through of the form is in Submitting a Risk; the conventions below are the vulnerability-specific tweaks on top of that. -
Set the Subject to the vulnerability identifier and a brief description. A useful pattern: CVE-2024-12345 — Apache HTTP Server SSRF — Production Web Tier. The CVE number anchors the vulnerability for cross-referencing; the brief description scans well on dashboards; the affected scope (Production Web Tier) tells the reader where the exposure lives.
-
Pick a Risk Source that says where it came from, such as a penetration-test or vendor-advisory value, or whichever value your install uses. The Risk Source field doesn't affect downstream behavior, but it lets you filter risks by source later — useful for splitting "vulnerability-derived risks" from "audit-derived risks" or "incident-derived risks" in reporting.
-
Set the Risk Scoring Method to the CVSS version your scanner reports (CVSS v2.0, CVSS v3.0, CVSS v3.1, or CVSS v4.0). CVSS v2.0 opens a card with Base, Temporal, and Environmental metric groups that you fill in from the scanner's published metrics. The v3.0, v3.1, and v4.0 widgets have a Vector box: paste the scanner's vector, choose Apply, and every metric fills in. In every version you can use the upstream NVD score as a starting point and adjust the Environmental metrics for your context (see Risk Scoring Methodologies). For a published CVE there's a shortcut: type the CVE ID into External Reference ID and SimpleRisk fetches the NVD entry and scores the risk with the newest CVSS version the CVE has, keeping the other versions alongside it (see Looking up a CVE).
-
Link the affected assets. Use the Affected Assets widget to link the risk to the specific systems with the vulnerability (see Tying Risks to Assets). The asset linkage is what makes "show me everything affecting our PCI-scope systems" filterable later.
-
Tag the risk for filtering. Add a
vulnerabilitytag so vulnerability-derived risks are filterable as a population, and acve:tag per CVE (for examplecve:CVE-2024-12345). Risks triaged from imported vulnerabilities carrycve:tags in exactly that form, so matching it puts your hand-recorded risks in the same filter. Tags are free text and can be created on the fly. -
Set the Risk Assessment to a one-paragraph summary. What the vulnerability is, what an attacker could do with it, and why it matters in your environment. The Risk Assessment field is the abstract; the Subject is the headline.
-
Save. The risk lands in the standard register and flows through the standard review-and-mitigation workflow.
Path B: Import scanner findings instead
If a scanner reported it, don't type it in. Export the scanner's findings and import the file from Vulnerabilities → Vulnerabilities, Import Vulnerabilities. Each vulnerability shows up once with all of its assets, and you triage the ones that need it into the register with Create risk or Attach to existing risk. The walk-through is in Importing Scanner Exports, and the triage itself in From Vulnerability to Risk.
Importing is manual: someone exports a file and imports it, as often as you choose. The Vulnerability Management Extra does the same job automatically, syncing from Qualys, Rapid7 or Tenable.io on a schedule into the same list. The signals that it's worth adding:
- You're importing from the same scanner every week or more, and someone's job has become "do the export."
- More than one scanner is in use.
- You want high-scoring findings triaged automatically, or a record of each sync and what it found.
- An auditor wants scanner-derived tracking with timestamps from the scanner itself, not from whoever ran the export.
Path C: Record a vulnerability you don't intend to promote
Not every vulnerability needs a risk-register entry. A scanner finding the team will patch in the next maintenance window, with no risk-acceptance decision and no mitigation plan beyond "patch it," doesn't add anything to the risk register that wouldn't be cleaner to track in the scanner's own console. If it came in through an import, Hide it on the Vulnerabilities list.
For this case, the right SimpleRisk action is no action — let the patch process handle it, and reserve the risk register for the findings that genuinely need risk-management treatment. The discipline of not recording every vulnerability as a risk is what keeps the risk register readable.
The exception: if the scanner doesn't have a remediation-tracking surface and you need something to track the patch through, the standard SimpleRisk pattern is to record a single risk per recurring batch ("Q3 2026 Patch Cycle") with a mitigation plan covering the batch as a whole, rather than per-finding.
Common pitfalls
A handful of patterns recur when teams record vulnerabilities by hand.
-
Recording every scanner finding as a risk. This is the most common failure. A program with 800 scanner findings per month and a policy of "every finding gets a risk-register entry" produces a register where 95% of the entries are routine vulnerabilities the patch process will close without any risk-management work. The register becomes unreadable and the auditor's "show us your top risks" question can't be answered. Restrict risk-register entries to vulnerabilities that genuinely need risk-management treatment.
-
Skipping the CVSS Environmental metrics. Using the upstream NVD CVSS Base Score as the risk's score, without adjusting for the Environmental metrics that represent your specific context, produces scores that are accurate in the abstract and wrong in your environment. A CVSS 9.8 on an internet-isolated system isn't operationally a 9.8 in your environment. The Environmental metric group exists for exactly this case; SimpleRisk's CVSS calculator exposes the fields.
-
No standard tagging convention. Recording a hundred vulnerability-derived risks without a
vulnerabilitytag (or worse, with an inconsistent set of tags —vuln,vulnerability,cve,scan-finding) produces a register where the vulnerability subset isn't filterable. Pick a convention before you start; write it down so the second person doing this follows the same pattern as the first. -
Typing in what a scanner already reported. Hand-recording a scanner finding loses the per-asset detail, the EPSS and KEV signals, and the link back to the finding. Import the export instead, and triage from the list.
-
Expecting imports or the Extra to find your hand-recorded risks. Neither touches existing risks. Triage reuses a risk only when its subject is exactly the vulnerability's title, and a hand-written subject like the pattern above almost never is. When an imported or synced vulnerability matches one of your hand-recorded risks, attach it with Attach to existing risk so the register keeps one risk, not two.
-
Confusing the CVSS score with the residual risk score. A CVSS 9.8 vulnerability with a strong compensating control (the affected service is firewalled off from any attacker who can reach it) doesn't have a residual risk of 9.8. The CVSS score describes the vulnerability's severity in the abstract; the residual risk is what's left after your controls. Record the mitigation plan and the residual percent; let the residual-risk calculation reflect the actual exposure rather than the headline CVSS.
-
Not linking the affected assets. A vulnerability risk that doesn't link to the specific assets with the vulnerability is missing the most important context ("which systems does this affect?") and the asset-by-risk reporting won't surface it. Always link to the affected assets; if the asset isn't yet in the inventory, add it (see Managing Assets in SimpleRisk).
-
Treating "patched" as the close criterion without a rescan. Closing a vulnerability risk with a comment of "patch applied" but no rescan to confirm the finding is gone produces an evidence trail the auditor can't verify. Wait for the next scan; close the risk only when the scanner confirms the finding has dropped off.