Glossary
Octiga’s docs use each of these terms with one specific meaning.
- Account risk
One of a fixed set of per-user findings Octiga checks for in a tenant, such as a dormant admin account or a shared mailbox that can still sign in. Each has its own remedy. See Account risk.
- Alert
The umbrella word for anything graded that reaches an operator’s alert list. An alert comes from an event, a deviation or a general notification. See Alerts.
- Baseline
One desired security setting Octiga can check and, in most cases, set (for example, “MFA enforced by Conditional Access”). Baselines are grouped into categories such as Conditional Access Policy and Email Security.
- Default group
The group every user in a tenant automatically belongs to. It is always the lowest priority in the group stack, and it cannot be reordered or removed. See Groups and priority.
- Deviation
An open finding: a baseline’s required value doesn’t match what’s set in Microsoft 365. A deviation opens when the mismatch appears, and resolves when the setting comes back into line or the baseline itself changes. Deviations are counted, not ranked by severity. See Deviations.
- Direct
A baseline reaching one user or one group specifically, rather than through a group they belong to. At user level, a Direct value always wins over anything from a group. See Groups and priority.
- Effective value
The value that wins for one user and one baseline: the one Octiga enforces and displays.
- Event
A Microsoft 365 audit-log record, classified as critical, danger, warning or info the moment Octiga ingests it. Event rules act on events only, not on deviations. See Events.
- Event rule
A rule that re-grades or suppresses future events matching a country, geographic region, network operator, user or tenant. Classification happens once, at ingest, so a rule doesn’t change events that have already happened. See Event rules.
- Group-direct baseline
A baseline added to a tracked group by hand, alongside anything a scheme already supplies it. It resolves at that group’s own priority, the same way as a scheme-supplied baseline. See Groups and priority.
- Lockout
Short for automatic lockout: Octiga disabling a user’s sign-in on its own, triggered by a high-severity event such as an impossible-travel sign-in. Governed by a tenant-level switch and a per-user switch. See User remedies.
- Managed
A governance mode in which the target stays linked to its scheme, so later edits to the scheme propagate automatically to everything it’s deployed to. Managed is a link; Direct is a snapshot. See Schemes.
- MSP
The managed service provider — the organisation that owns the Octiga account, its staff, and its client tenants.
- Org-level
A scheme, or a baseline resolution, that targets a whole tenant rather than individual groups or users within it. See Schemes.
- Provenance
The effective value plus every value that lost the resolution for that baseline and user. A superseded value is kept and can be shown, but has no effect. See Groups and priority.
- Remediation
Octiga writing a baseline’s required value back into Microsoft 365, either automatically (through a per-baseline switch) or manually (as an operator-triggered task with live progress). See Remediation.
- Resolution
The process that decides, for one user and one baseline, which value applies out of every place that baseline could reach them from. See Groups and priority.
- Scheme
A named bundle of baselines, authored once and deployed to many targets. An org-level scheme targets a whole tenant; a user-level scheme targets Azure groups and individual users. See Schemes.
- Service plan
The unit Microsoft licensing is checked against, such as “Entra ID P1”, rather than a bundle name such as “Microsoft 365 Business Premium”. See Licence requirements.
- Supersedes
Provenance language for a value that lost the resolution — for example, “Direct value X supersedes Finance’s Y”. It describes what would have applied, not what does.
- Tenant
One client’s Microsoft 365 directory, connected to Octiga.
- Tracked group
An Azure group included in a tenant’s priority stack. You choose which groups Octiga tracks and their order in the stack; Octiga never changes who belongs to them. See Groups and priority.
- User-level
A scheme, or a baseline resolution, that targets Azure groups and individual users within a tenant, rather than the tenant as a whole. See Schemes.
- Verdict
What Octiga’s check for one baseline concludes for a user or a tenant. Passing: the setting matches. Deviated: it doesn’t, and a deviation is open. Excluded: the tenant or user lacks the licence the baseline needs, so it wasn’t evaluated. A rarer fourth state, Not assessed, appears when Octiga hasn’t been able to check yet, for example before the first sync completes.