Skip to main content

Overview

Snoozes temporarily pause follow-up on vulnerabilities and policy violations for a fixed duration. Use snoozes when the item remains valid, but the team needs time for remediation, an upstream fix, or a planned review window. Snoozes keep the item visible in Cysmiq while recording who requested the pause, how long it should last, and whether approval was required. When a vulnerability is snoozed, related open or pending-review policy violations for that vulnerability are snoozed for the same window.
Availability depends on your Cysmiq plan.
After snoozes are enabled:
  • Snoozes appears in the workspace navigation
  • Workspace owners can configure governance from Snoozes
  • Vulnerability and policy violation action menus include Snooze

Governance settings

The Snoozes settings page has separate governance sections for Policy violations and Vulnerabilities. Each section supports the same settings:
SettingMeaning
Require approvalIf enabled, snooze requests stay pending until an approver approves them. If disabled, requests apply immediately.
Max snoozesMaximum approved snoozes allowed for each item. A value of 0 means no limit.
Approver rolesRoles that can approve, reject, or clear snoozes for the selected scope.
Default settings:
TargetRequire approvalMax snoozesApprover roles
Policy violationsEnabled2Owner
VulnerabilitiesEnabledNo limitOwner

Scope overrides

Snooze governance can be configured at these scopes:
  • Workspace
  • Organization
  • Repository
  • Application
Selected scopes inherit effective settings from broader scopes until an override is saved. Use Reset overrides to clear local settings and return the selected scope to inherited behavior.

Request workflow

Users request snoozes from the Snooze action on a vulnerability or policy violation. The request form includes:
FieldValues
Duration1 day, 3 days, 7 days, 14 days, or 30 days
ReasonOptional text describing why the snooze is needed
After the user selects Request snooze, Cysmiq either applies the snooze immediately or creates a pending request based on the effective Require approval setting.

Review workflow

Pending requests show who requested the snooze and the requested duration. Available actions depend on the user’s role and relationship to the request:
StateAvailable actions
Pending request for an approverApprove, Reject
Pending request for the requesterCancel request
Pending request for other usersAwaiting approval
Active snooze for an approverClear snooze
Approving a request applies the snooze and increments the item’s snooze count. Rejecting or canceling a pending request leaves the item active. Clearing an active snooze ends the current snooze window.