Glossary
Short definitions of the terms used in Revo and this knowledge base.
Updated
Terms are in alphabetical order. Each links to the article that explains it in full.
| Term | Meaning |
|---|---|
| Act now | The most urgent items for a customer or across customers, on Home and the customer overview. See Insights. |
| Action plan | A customer's ordered roadmap of controls to fix, in three stages. See Action plan. |
| Active scan | An external assessment that probes the customer's systems (port scan, zone transfer). Needs a verified domain, an attestation and admin approval. See Scope and authorization. |
| Agent | RevoAgent: signed software installed on a computer that reports its state and runs signed jobs. The computer itself is a device. See Devices. |
| Alert | A security event: something that just happened, such as malware found or a new administrator. See Alerts. Also, a notification that goes to the alert recipients by default. |
| Alert recipients | The team members who receive critical alerts by default. See Notifications. |
| Approval request | A change proposed by the AI analyst that waits for a person to approve it. See AI approvals. |
| Assessment | A run of checks against a customer: external, Microsoft 365 or internal. Produces check results and findings. See External assessments. |
| Attack surface | A customer's internet-facing systems: domains, hosts, IP addresses, mail servers. See External assessments. |
| Baseline | Another name for a customer's ideal state. |
| Break-glass account | An emergency Microsoft 365 administrator account, expected to be excluded from Conditional Access and rarely used. See Investigating users. |
| Compliance | How close a customer is to its ideal state, control by control. See Ideal state. |
| Confidence | How sure RevoSecure is about a finding: confirmed, firm or suspected. See Confidence. |
| Control | One security requirement (for example "MFA for every user"). Checks belong to controls; the ideal state and action plan are built from them. |
| Coverage gap | Something RevoSecure couldn't check, shown as such rather than as a pass. |
| Customer | An organisation you manage or are selling to, with its own workspace. See Key concepts. |
| Customer mode | Working inside one customer's workspace (/c/<customer>/…), where every page is about that customer only. See Key concepts. |
| Customer portal | Read-only access for a customer's own users to their overview, shared findings and client reports. See Customer portal. |
| Deployment | One patch run (a maintenance window, install now, scan, restart or retry) across devices, with per-device results. See Deployments. |
| Device | A computer or server running RevoAgent. See Devices. |
| Enablement package | A small Microsoft update that switches on a newer Windows 11 version on 24H2 and later, with one restart. See Windows upgrades. |
| EPSS | Exploit Prediction Scoring System: FIRST's estimate of how likely a vulnerability is to be exploited in the next 30 days. See KEV and EPSS. |
| Finding | A problem RevoSecure found, with severity, confidence, evidence and remediation. See Triage. |
| Grade | A–F, from the security score. See Severity and the security score. |
| Ideal state | The controls and thresholds a customer is measured against. See Ideal state. |
| Installer link | A secret, expiring link that installs the agent for one customer. See Devices. |
| KEV | CISA's Known Exploited Vulnerabilities catalogue: vulnerabilities attacked in the wild. See KEV and EPSS. |
| Maintenance window | The days and hours when updates may install and devices may restart. See Policies. |
| Managed customer | A customer you look after, as opposed to a prospect. See Add and manage customers. |
| Module | One capability or data source (Microsoft 365, devices, ThreatLocker…), active or not per customer. See Modules. |
| Passive assessment | An external assessment that uses public information only; safe for prospects and needs no permission. |
| Patch policy | What auto-approves, when it installs and how devices restart. See Policies. |
| Pillar | One area a customer's posture is measured across. See Posture pillars. |
| Portfolio | All customers together: the default mode, with pages that cover every customer. |
| Prospect | An organisation you're selling to. Can be assessed passively and converted to a managed customer. |
| Quick look | The panel that opens details on the right without leaving the list. See Finding your way around. |
| Release channel | Beta or stable: which agent releases a device is offered. See Release channels. |
| Ring | A group of devices that gets approved updates after a set delay (for example Pilot, then Broad). See Policies. |
| Risk score | 0–100 priority of one finding, from severity, exploitation evidence, confidence and asset criticality. See Severity. |
| Safeguard hold | Microsoft holding a Windows upgrade back from devices with a known problem. See Troubleshooting Windows upgrades. |
| SBOM | Software bill of materials: a list of the components in an application. See Applications from an SBOM. |
| Secure Score | Microsoft's own score for a Microsoft 365 tenant's security settings. See Secure Score. |
| Security score | 0–100 score per customer from its open findings, weighted by category. See Severity and the security score. |
| Show to customer | The switch on a finding that controls whether the customer portal and client reports include it. See Branding and sharing. |
| Sign-in strength | A grade of Microsoft 365 users by their strongest MFA method. See Sign-in strength. |
| Suspected | The lowest confidence: inferred, for example from a version banner. Verify before acting. |
| Test device | A device allowed to run a newer Windows version than its policy, to try it first. See Windows upgrades. |
| Threat watch | A rule that answers "is anyone running X below version Y?" across every customer. See Threat watches. |
| Workspace | Your MSP's account in Revo: your team, customers, settings and billing. See Key concepts. |