Skip to main content
Version: 1.0.0-beta

How-To: Map Controls

Learn how to create controls, map them to risks, and track their effectiveness.

Prerequisites​

  • At least one risk statement must exist for the entity
  • You must have the Auditor, Manager, or CAE role

Creating Controls​

Step 1 — Navigate to the Library​

Click Library in the sidebar to open the Risk & Control Library.

Library view

Step 2 — Go to Controls Tab​

Click the Controls tab in the Library.

Step 3 — Click "New Control"​

Click + New Control to open the creation form.

Step 4 — Complete Control Details​

FieldRequiredDescription
Control IDAuto-generatedUnique identifier (e.g., CTRL-001)
Title✅Descriptive name (e.g., "Dual approval for payments > SAR 50,000")
DescriptionRecommendedDetailed control description including what, who, when, and how
Type✅Preventive, Detective, Corrective
Nature✅Manual, Automated, IT-Dependent Manual
Frequency✅Continuous, Daily, Weekly, Monthly, Quarterly, Annual, Ad-hoc
OwnerRecommendedPerson responsible for executing this control
EffectivenessOptionalEffective, Partially Effective, Ineffective, Not Tested

Step 5 — Save​

Click Save to create the control in the library.

Mapping Controls to Risks​

Step 1 — Open the Entity or Risk​

Navigate to the entity → Risks tab → click a specific risk.

Step 2 — Go to Controls Section​

In the risk detail, scroll to the Mitigating Controls section.

Click + Link Control to open the control search dialog.

Step 4 — Search and Select​

  • Search existing controls by name, ID, or description
  • Select one or more controls to map
  • Click Link Selected

Step 5 — Set Mapping Details​

For each mapping, optionally set:

FieldDescription
Mapping TypePrimary or Secondary
NotesContext for this specific risk-control linkage
Expected Result

The control appears in the risk's "Mitigating Controls" list. The risk detail now shows a control coverage indicator. When all controls are effective, the residual risk may be automatically recalculated.

Control Effectiveness Testing​

Controls are tested during engagement fieldwork. Results feed back into the Library:

Effectiveness RatingMeaningVisual
EffectiveControl operates as designed🟢
Partially EffectiveControl has gaps but provides some mitigation🟡
IneffectiveControl does not mitigate the risk🔴
Not TestedControl has not been evaluated in current period⚪

Control Types Explained​

TypeDescriptionExample
PreventiveStops errors/fraud before they occurApproval workflow, access restrictions
DetectiveIdentifies errors/fraud after they occurReconciliations, exception reports, monitoring
CorrectiveFixes issues after detectionIncident response, remediation procedures

AI-Assisted Control Mapping​

The AI companion can suggest control mappings:

  1. Open a risk statement
  2. Click AI Suggest Controls
  3. AI recommends controls based on:
    • Industry standard control frameworks (COSO, COBIT)
    • Existing controls in your library for similar risks
    • Regulatory requirements (NCA ECC control requirements)
  4. Review and apply suggestions

Best Practices​

  1. Avoid orphan controls — every control should be mapped to at least one risk
  2. Avoid orphan risks — every risk should have at least one mitigating control
  3. Test regularly — control effectiveness should be re-evaluated at least annually
  4. Document design vs operating — capture both design adequacy and operational effectiveness
  5. Use the control library — centralize controls to avoid duplication across entities