Skip to content

[FEAT] Add a blocking option to controls #488

Description

@Karine-Bauch

Description

Suggestion from @p1-dta

Plumber currently determines whether a pipeline passes or fails based on the configured minimum score/points.

This works well for defining an overall acceptable compliance level, but it does not allow users to make specific controls mandatory.

For example, a project may accept a minimum score of 80 while having some requirements that must never be violated, such as forbidding Docker images using the latest tag.

If such a control produces a finding but the final score remains above 80, the Plumber check still passes.

This means there is currently no way to express:

"A score of 80 is acceptable, but this specific control must always pass."

The severity of a control is defined by Plumber, so users also cannot rely on changing a control to critical to enforce this behavior.

Describe the solution you'd like

Add an optional blocking property to controls.

For example:

controls:
  containerImageMustNotUseForbiddenTags:
    enabled: true
    blocking: true
    tags:
      - latest

When blocking: true, any finding produced by this control should cause the Plumber check to fail, regardless of the final score.

For example:

Minimum required score: 80
Final score: 85

containerImageMustNotUseForbiddenTags: FAILED
blocking: true

Result: FAILED

Without blocking: true, the existing scoring behavior would remain unchanged.

Expected behavior

Given:

controls:
  controlA:
    enabled: true
    blocking: false

  controlB:
    enabled: true
    blocking: true

If controlA produces a finding but the final score remains above the configured threshold, the check passes as it does today.

If controlB produces a finding, the check fails regardless of the final score.

This would allow the global score to represent the acceptable overall compliance level while specific controls can be used as hard requirements.

Backward compatibility

blocking should default to false.

Existing configurations would therefore keep the current scoring behavior without requiring any changes.

Why It's Valuable

Not all compliance requirements have the same semantics.

Some findings can reasonably contribute to an overall compliance score, while others represent organization-specific requirements that must always be enforced.

Adding blocking would make it possible to combine both approaches:

  • Score-based compliance for the overall quality/security level.
  • Hard gates for specific requirements that must never be violated.

This also keeps the severity defined by Plumber separate from an organization's enforcement policy: a control can remain medium or high from Plumber's perspective while still being mandatory for a specific organization.

Activity

  1. changed the title [-][FEATURE] Add a blocking option to controls[/-] [+][FEAT] Add a blocking option to controls[/+] on Sep 25, 2026
  2. p1-dta commented on Sep 25, 2026

    @p1-dta
    Contributor

    IMHO this is mandatory as soon as you want to protect yourself from supplychain attacks and in order to not freeze the CICD of a huge organization only because one component is updated 5 minutes ago.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions