Getting Started
Glossary: Terms You'll See in SeqOps
Plain-language definitions of the terms used across SeqOps and this Support Centre.
Plain-language definitions of the terms you'll see in SeqOps and in these articles.
Findings, Alerts, and Severity
- •Finding — A vulnerability or configuration risk that SeqOps identified in a connected cloud environment or server. A finding can be marked Accepted Risk or False Positive.
- •Alert — A notification-worthy event tracked in Alert HQ. Alerts move through their own statuses: New → Acknowledged → In Progress → Resolved or False Positive. Alerts and findings are separate and use different status vocabularies.
- •Severity — How urgent a finding or alert may be, based on its potential security impact. SeqOps uses five levels: Critical, High, Medium, Low, and Informational. See SeqOps Alert Categories & Severity Levels.
Compliance
- •Compliance framework — A set of controls, such as CIS or PCI DSS, that SeqOps scans your environment against. See the Compliance Framework Reference.
- •Compliance score — How your environment aligns with your selected framework, based on the controls SeqOps evaluated. It is not a certification or an audit result. See Understanding SeqOps Compliance Scores.
- •Policy — A rule SeqOps uses to evaluate configurations and generate findings. See SeqOps Policy Configuration.
Infrastructure
- •Cloud environment — One AWS account, one Azure subscription, or one GCP project. Each counts separately toward your plan. See What Counts as a Cloud Environment.
- •Cloud connector — The connection that links one cloud environment to SeqOps.
- •Server agent — The SeqOps software installed on a Windows or Linux server to monitor it. Each monitored server uses one agent slot.
- •Agent state — Whether an agent is active (online and reporting) or offline (SeqOps is no longer receiving data from it). See Agent Shows Offline: Step-by-Step Diagnosis.
Plans and Capacity
- •Plan limit — The capacity your plan includes for each resource, such as agents, cloud environments, users, storage, and API calls.
- •Grace period — The 24 hours after a resource reaches 100% of its limit, during which you can still add capacity while you upgrade. See Capacity Limits & Grace Periods.
- •Data retention — How far back your active account's history goes: 14, 30, or 45 days depending on your plan.
glossarytermsdefinitionsseverityfindingalert