CRB-SCHED-001

A schedule must not point at a process that cannot run

Risk
High

Absent, it prevents detection, investigation or response.

Evidence
metadata

Decidable from the instance’s own configuration.

Section
Schedules

Timers, and whether what they start still runs.

Fix shape
entity · Process

One task per non-compliant process.

Control Statement: A process schedule must reference a process that exists and is enabled.

Description: Creatio allows a scheduled trigger to remain configured after the process it starts has been disabled or removed. The schedule then fires against nothing: the timer is live, the work is not.

Rationale: This fails in the most reassuring way available. The schedule is visibly configured, so anybody checking whether the nightly job is set up will find that it is — and the job has not run since somebody disabled the process during an incident eight months ago and never switched it back on. Nothing errors, because from the scheduler’s point of view there is simply nothing to start.

Audit Procedure:

  1. Enumerate the configured process schedules and the process each starts.
  2. Resolve each against the processes in the configuration.
  3. Record every schedule whose process is missing, or is present but disabled.
  4. For each, establish what the schedule was supposed to do and when it last did it.

Remediation:

  1. Where the work is still needed, re-enable the process, or repoint the schedule at its replacement.
  2. Where it is not, delete the schedule rather than leaving it configured and inert.
  3. Add a check of dependent schedules to the procedure for disabling a process.

Default Value: Creatio does not remove or disable a schedule when the process it starts is disabled or deleted, and reports nothing.

Cite this control as CRB-SCHED-001, Release Readiness Benchmark v0.2.0. Verified against Creatio 8.x. Published by ctx10; not affiliated with or endorsed by Creatio.