Skip to content
    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 vulnerability is shown as open or fixed; SeqOps updates it when a later scan shows the issue is gone.
    • •Alert — A notification-worthy event tracked under Alerts. Alerts move through Open → Acknowledged → In Progress → On Hold → Closed. A judgement, such as False Positive, is recorded separately from the status.
    • •Severity — How urgent a finding or alert may be, based on its potential security impact. SeqOps uses five levels: Critical, High, Medium, Low, and Info. 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. You switch frameworks on or off under Compliance → Library. 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.
    • •Monitor — A count-based rule that raises an alert when matching log events pass a threshold.

    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 — A 24-hour window that starts with the first request over your user limit. During it you can still add users while you upgrade, and it resets when usage drops back under the limit. Storage, API requests, agents and cloud connectors have no grace period. See Capacity Limits & Grace Periods.
    • •API requests — Requests SeqOps makes to outside sources while scanning your servers and cloud accounts, for example looking up a new software version for known vulnerabilities or reading a cloud account. You don't make them yourself, and they don't limit how often we scan.
    • •Data retention — How far back your active account's history goes: 30, 45, or 60 days depending on your plan.
    glossarytermsdefinitionsseverityfindingalert

    We use cookies

    We use essential cookies to run this site. With your permission, we'd also like to use analytics cookies to see how the site is used, and functional cookies for chat and videos. Change your choice any time under Cookie settings. Read our Cookies Policy