Operational Risk Management

Every process can fail. Know which ones actually will.

Operational failure caught in the self-assessment, not the post-mortem.

Falconry360 unifies RCSA, loss event capture, and KRI monitoring across people, process, and systems — using the Basel event-type taxonomy — so the same gap doesn't get rediscovered the hard way twice.
Basel II Event Types

7

Pre-built — internal fraud through to physical damage

Frameworks Pre-Mapped

20+

NCA, SAMA, ISO 27001, NIST CSF & more

Frameworks Mapped

24

ISO, NIST, SAMA, NCA, PDPL & more

RCSA Review Lines

2

First-line self-assessment, second-line challenge

Risk Domains Covered

6

Identity, Infra, Endpoint, Data, Cloud, Third-Party

Control Reuse Rate

73%

Controls shared across 2+ frameworks

Loss-to-Register Linkage

100%

Every loss event tied to the process and control that failed

Severity Signals Blended

3

CVSS · EPSS · KEV-aware prioritisation

Cross-Framework Coverage

96%

Requirements mapped to a control

Reporting Views Unified

3

Losses, KRIs, and RCSA in one board pack

Enterprise Risk Register

Connected

Shared taxonomy, shared severity scale

Open Mapping Gaps

14

Requirements without a control

One Platform

One System for RCSA, Losses, and KRIs

Stop assembling the quarterly operational risk pack from four disconnected spreadsheets. One workflow, one taxonomy, one feedback loop.

Process Risk Register (RCSA)

Every business process risk-assessed by the first-line owner, challenged by the second line, scored on inherent and residual likelihood and impact.

Basel-Classified Loss Events

Every loss and near-miss captured with severity, frequency, and Basel II classification — then linked to the process and control that failed.

Leading KRIs, Not Just Lagging Losses

A loss event tells you what already happened. A KRI tells you it's about to. Falconry360 correlates both and escalates before the next incident.

Core Capabilities

Operational Risk, the Way Examiners Expect It

Six connected capabilities that turn RCSA, loss events, and KRIs into one coherent operational risk programme — not three disconnected spreadsheets.

01

One Register, Owned by the People Who Run It

Every business process risk-assessed by the first-line owner and challenged by the second line. High-risk processes surface automatically — not three months later.

02

Basel II Event-Type Classification

The seven Basel event types pre-built — internal fraud, external fraud, employment practices, and the rest — so every loss is classified consistently from day one.

03

Leading Indicators, Not Just Lagging Losses

Key risk and control indicators tracked against thresholds, correlated with loss history, and escalated before the next event — not after.

04

Loss Events That Feed the Register Back

Every loss and near-miss linked to the process and control that failed — so the same gap doesn't get rediscovered the hard way twice.

05

Scenario Analysis for Tail Risk

Loss history can't tell you about the failure that hasn't happened yet. Structured scenario workshops model low-frequency, high-impact events.

06

Board Reporting, Fully Integrated

Loss trend, RCSA coverage, and KRI breaches tracked automatically — board pack drafted with FalconryX narrative, evidence already attached.

Inside the Platform

From Self-Assessment to Board Pack, in One System

Three screens the RCSA register your first line works in, the Basel-classified loss event database, and the board pack that integrates losses, KRIs, and RCSA automatically.

Process Risk Register (RCSA)

Every business process, risk-assessed by the first line and challenged by the second — with inherent and residual scoring visible at a glance.

Loss Event Database — Basel II Classified

Every loss and near-miss, classified by Basel event type and linked to the process and control that failed.

Operational Risk Board Pack

Loss trend, RCSA coverage, and KRI breaches integrated into one report — drafted automatically, evidence already attached.

How It Works

From Self-Assessment to Board Decision

A defined lifecycle connecting RCSA, loss events, and KRIs — so the gap is caught in the assessment, not the post-mortem.

Self-Assess & Challenge

First-line owners assess their process; second line challenges the rating. Inherent and residual risk both scored.

Classify by Basel Type

Every loss and near-miss classified against the seven Basel II event types — consistent from day one, audit-ready by design.

Track Leading Indicators

KRIs and KCIs tracked against thresholds, correlated with loss history, escalated before the next incident — not after.

Stress-Test the Tail

Scenario workshops model the low-frequency, high-impact failure that hasn't happened yet — across operational, financial, and reputational lines.

Report, Integrated

Loss trend, RCSA coverage, and KRI breaches compiled automatically into one operational risk board pack.

Why Falconry360

Built for How Examiners Actually Review Operational Risk

RCSA, loss events, and KRIs share one register — not three disconnected spreadsheets

Basel II event-type taxonomy built in — classified consistently from day one

Leading KRIs correlated with loss history — escalation before the next event, not after

Every loss event linked back to the process and control that failed — the gap gets fixed, not rediscovered

FalconryX connects the loss event to the RCSA rating that missed it — and tells your team what to reassess

Take Control

Catch Operational Failure in the Assessment, Not the Post-Mortem

RCSA, loss events, and KRIs — finally working as one system.