Barrier Implementations

Evaluate how each barrier is implemented and how effective it is in practice.

Why evaluate barrier implementations?

A barrier on paper is only as good as its implementation in practice. A well-designed control that is poorly implemented, inconsistently applied, or untested may provide little or no protection when it matters most. Evaluating implementations closes the gap between what should be in place and what is actually in place.

For each barrier used in an assessment, record how it is implemented, link to the supporting documentation, and assign an estimated effectiveness score. This score is then reflected in the bow-tie diagram — barriers with lower effectiveness are rendered lighter, making gaps in your defences immediately visible.

Describe the implementation

How is this barrier actually deployed? Who owns it? What does "in place" mean for this control?

Link to documentation

Point to the procedure, policy, system record, or test result that evidences the barrier exists.

Score effectiveness

0 % = not in place or non-functional. 100 % = fully implemented, tested, and maintained.

6

Barriers in use

0

Evaluated

6

Not yet evaluated

Avg. effectiveness

? no eval
ERP Patch Management prevention

No implementation description yet

1 assessment
Not evaluated
? no eval
Immutable Offline ERP Backups mitigation

No implementation description yet

1 assessment
Not evaluated
? no eval
MFA on ERP Access prevention

No implementation description yet

1 assessment
Not evaluated
? no eval
Network Segmentation of ERP Environment prevention

No implementation description yet

1 assessment
Not evaluated
? no eval
Ransomware Incident Response Plan mitigation

No implementation description yet

1 assessment
Not evaluated
71% eff.
Business Continuity Procedures mitigation

We hebben alle administratie ook op papier in multomappen.

1 assessment
Evaluated 2026-04-10…