# 35 terms, each with a sourced example

GLOSSARY, read 10 Nov 2026

**The short answer.** Every term is defined in plain words and carries one real example with its source and read date, so the definition can be checked rather than taken on trust. Terms are listed alphabetically; each page links to the related terms used alongside it.

- [Agent-based scanning](/glossary/agent-based-scanning/): Agent-based scanning uses a small program installed on each host to collect vulnerability and configuration data and report it to a manager.
- [Asset criticality](/glossary/asset-criticality/): Asset criticality is a rating of how much the business depends on an asset, set by rule, tag or owner input.
- [Authenticated scanning](/glossary/authenticated-scanning/): Authenticated scanning logs into a target with provided credentials to inspect installed software, patches and configuration from the inside.
- [Bi-directional ticket sync](/glossary/bi-directional-ticket-sync/): Bi-directional ticket sync keeps a remediation ticket in an IT service tool and its finding in the vulnerability platform in step: status changes in either place update the other.
- [Business context](/glossary/business-context/): Business context is information about what an asset does for the organization: the application, the data it holds, the team that owns it, the regulation it falls under.
- [CMDB](/glossary/cmdb/): A CMDB, or configuration management database, is the record of IT assets and their relationships, owners and business services.
- [CMMC 2.0](/glossary/cmmc-2-0/): CMMC 2.0 is the Department of Defense's Cybersecurity Maturity Model Certification program for contractors that handle federal contract information or controlled unclassified information.
- [Compensating control](/glossary/compensating-control/): A compensating control is a safeguard that reduces the risk of a weakness that cannot be fixed now, such as a firewall rule, a configuration change or a web application firewall signature.
- [Connector](/glossary/connector/): A connector is the integration that pulls findings or asset data from one source, or pushes tickets to one destination, on a schedule or by event.
- [Correlation](/glossary/correlation/): Correlation links findings that are related but not identical, for example a code-level flaw and the running service built from that code, or a scanner result and the asset record it belongs to.
- [De-duplication](/glossary/de-duplication/): De-duplication merges findings that describe the same weakness on the same asset, reported by different scanners or on different runs, into one record.
- [Exposure assessment platforms](/glossary/exposure-assessment-platforms/): Exposure assessment platforms are a Gartner category for products that aggregate and prioritize exposure data from scanners, asset and cloud tools to support continuous threat exposure management.
- [False positive](/glossary/false-positive/): A false positive is a finding that reports a weakness that is not present on the asset, for example from a version-string match on a backported fix.
- [FedRAMP High](/glossary/fedramp-high/): FedRAMP High is the authorization level for cloud services holding the government's most sensitive unclassified data, where a breach could have severe or catastrophic effects.
- [FedRAMP Moderate](/glossary/fedramp-moderate/): FedRAMP Moderate is the authorization level for cloud services that handle controlled unclassified information where a breach would have serious adverse effects.
- [Finding](/glossary/finding/): A finding is one record that a specific weakness exists on a specific asset, as reported by one tool at one time.
- [Flat-file import](/glossary/flat-file-import/): A flat-file import loads findings or assets from a spreadsheet-style file, usually CSV, by mapping its columns to platform fields.
- [Mean time to remediate](/glossary/mean-time-to-remediate/): Mean time to remediate (MTTR) is the average time from a finding being detected or prioritized to its confirmed fix.
- [Multi-tenancy](/glossary/multi-tenancy/): Multi-tenancy is a platform design where one deployment serves many customers or business units with their data, users and settings kept separate.
- [NIST RMF](/glossary/nist-rmf/): The NIST Risk Management Framework is the process US federal agencies use to categorize systems, select and implement controls, assess them, authorize operation and monitor continuously.
- [Normalization](/glossary/normalization/): Normalization converts findings from different tools into one schema: the same field names, severity scale, asset identifiers and status values.
- [Owner assignment](/glossary/owner-assignment/): Owner assignment routes each finding to the person or team accountable for fixing it, by rule: asset tags, a configuration database field, a repository owner or a group lookup.
- [Plan of action and milestones (POA&M)](/glossary/plan-of-action-and-milestones/): A plan of action and milestones (POA&M) lists each known weakness in a system, the resources needed, milestones and a scheduled completion date.
- [Platform risk score](/glossary/platform-risk-score/): A platform risk score is a number a vendor calculates for each finding or asset from its own inputs: severity, exploitation signals, asset context and sometimes customer weights.
- [Remediation grouping](/glossary/remediation-grouping/): Remediation grouping bundles many findings that one action fixes, for example a patch that closes forty CVEs on a host, into a single task.
- [Remediation SLA](/glossary/remediation-sla/): A remediation SLA is the maximum time allowed to fix a finding, set by severity or priority and sometimes by asset class.
- [Risk acceptance](/glossary/risk-acceptance/): Risk acceptance is a documented decision by an accountable owner to leave a known weakness unfixed for a stated period, with a reason and an approver.
- [Risk-based vulnerability management](/glossary/risk-based-vulnerability-management/): Risk-based vulnerability management ranks findings by the likelihood and consequence of an attack on your own assets, not by severity alone.
- [Role-based access control](/glossary/role-based-access-control/): Role-based access control (RBAC) grants permissions to roles, not individuals, so a user can only see and change what their role allows.
- [Scanner coverage](/glossary/scanner-coverage/): Scanner coverage is the share of known assets that a scanner or agent assessed in a given period.
- [Unified vulnerability management](/glossary/unified-vulnerability-management/): Unified vulnerability management brings findings from many scanners, application security tools, cloud tools and penetration tests into one normalized, de-duplicated record set, then ranks and routes them from one place.
- [Universal adapter](/glossary/universal-adapter/): A universal adapter is a connector framework for sources a vendor has not built a named connector for.
- [Vulnerability aggregation](/glossary/vulnerability-aggregation/): Vulnerability aggregation is the collection of findings from every scanner and assessment source into a single store before any ranking happens.
- [Vulnerability backlog](/glossary/vulnerability-backlog/): The vulnerability backlog is the set of open findings past or approaching their service level.
- [Vulnerability exception](/glossary/vulnerability-exception/): A vulnerability exception is the record in a platform that excludes a finding from overdue counts, either because it will not be fixed (accepted) or cannot be fixed yet.

Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/glossary/
