Tasks

Tasks are how CyberGuard tracks the operational work that keeps controls effective: the weekly access review, the monthly backup test, the quarterly policy refresh, the one-off offboarding checklist. They are deliberately separate from applied controls — a control says what is done; a task says that someone has actually done it on a given date.

Where to find it

Operations → Tasks in the sidebar. The list shows each definition with its recurrence, Assigned to, last occurrence status and Next occurrence.

Key concepts

Definitions and occurrences

Tasks come in two layers:

• A task definition (template) is the reusable spec — title, description, assignees, expected evidence and the recurrence rule. It says what should happen and how often.
• A task occurrence is a single scheduled run produced from a definition — the actual row with a due date, a status (pending → in progress → completed, or cancelled) and the evidence collected when the work was done.

A one-off task is simply a definition that produces a single occurrence.

Recurrence

Mark a definition Recurrent and configure its schedule: a frequency (daily, weekly, monthly or yearly), an interval (“every 3 months”), and refinements such as specific days of the week, weeks of the month or months of the year, plus an optional end date. The schedule is rendered in words wherever it appears — Monthly, Every 3 months — and occurrences are materialized automatically as their due dates come into view, so upcoming work is always visible.

Links to controls and audits

A definition can be wired to the objects its work maintains: applied controls (the canonical link — this work keeps that control healthy), audits, risk assessments, assets, findings and incidents. When an occurrence is completed, the evidence it produced stays back-linked to it, so the audit trail closes the loop: an auditor asking for proof of monthly backup testing is answered by the task and its completed occurrences.

Working with tasks

1. Define — create the task with the add button: name, domain, assignees, what’s expected when it runs, and the schedule.
2. Work the occurrence — when a due date arrives, the assignee opens the occurrence, records what was done, attaches evidence and marks it completed.
3. Iterate — edit the definition to adjust cadence, assignees or expected evidence. Existing occurrences keep their state; future ones pick up the change.

Tip

Attach the evidence on the occurrence, not in a shared drive. Tracking tasks inside the platform is precisely so the proof of execution lives next to the rest of the compliance record.

Note

The Enabled toggle on a definition pauses occurrence generation without deleting the schedule — useful for seasonal work or controls under redesign.

Related

• Control plan — the grid that verifies recurring tasks actually ran on cadence.
• Applied controls — the controls this work maintains.
• Calendar — occurrences plotted by month.