Controls & RCSA
Maintain one control library, test design and operating effectiveness, run risk and control self-assessments, and see effectiveness derived from evidence rather than opinion.
What it does
Document each control with its type, nature, frequency, category, owner and unit. Link it to the risks it mitigates and the requirements it satisfies, so one control can serve several programmes.
Record design and operating tests and RCSA self-assessment results. Each control's effectiveness is derived from its latest tests, so the status on the dashboard always traces back to a dated result and the person who recorded it.
Key capabilities
What works in the platform today, and what is on the roadmap.
- Available working in the current release
- Planned on the roadmap — not yet available
- Available
Control library
Controls with type (preventive, detective…), nature, frequency, category, owner and unit.
- Available
Design and operating tests
Record test kind, method, result, weaknesses found, tester and date.
- Available
RCSA self-assessments
Control owners record self-assessment results alongside independent tests.
- Available
Derived effectiveness
Effectiveness is calculated from the latest design and operating results — not typed in by hand.
- Available
Risk ↔ control ↔ requirement links
One control can mitigate several risks and satisfy several requirements.
- Available
Coverage gaps
See requirements without controls, flagged by the rule engine.
- Planned
Scheduled test campaigns
Automatic scheduling and assignment of periodic test cycles.
How it connects
Records are linked across modules, so the same fact is entered once and seen wherever it matters.
See Controls & RCSA with your own data
Book a guided walkthrough, or sign in to your workspace to explore the module.
Consulting: consulting@4each1.com · Projects & systems development: projects@4each1.com