Chapter 13: Incident Data Collection Flashcards

1
Q

What is the definition of “Incident Data Collection”?

A

The process of gathering detailed information about incidents and events that may pose risks to the organisation.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What is the Importance of “Incident Data Collection”?

For identifying what, what does this support?

A
  • Identifying root causes, patterns and improvng risk management
  • Aids with reg compliance
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What are the 4 data collection methods?

A
  • Automated systems: Software to capture and log incidents in real time
  • Manual Reporting: Staff report incidents through forms / channels
  • Audits and reviews
  • Using existing soucres: general ledgers, client complaints, IT logs and legal provisions to collect incident data.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

When discussing loss reporting, why is “Data Beyond Regulation” important?

Why might reporting data for regs actually help the firm?

A

It not only meets data requirements but can also improve the profitability and internal controls.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What is the link between loss data reporting and Basel II?

A

Collecting and analyzing high-quality loss data improves governance and reduces capital addons under regulatory frameworks.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Is loss data a major driver of regulatory capital requirements?

If so, under which regulations?

A

Yes.

Under Basel regulations (AMA and SMA)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

What are the BCBS data quality requirements?

How many years history period and threshold?

A

10 years and a 20,000 EUR threshold

Must be reviewed indepdently.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What is meant by a firms “Broader View”, when comparing Losses Vs. Incidents?

What will they track that regulators wont?

A

Organizations will also track “incidents” (e.g., near misses, unintentional gains, incidents
without direct financial impact), not just losses

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What is the definition of a “Near miss”?

A

Avoided losses by luck or by accident outside of normal controls.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What type of losses do regulators focus on (Basel Committee)?

What do they ignore?

A

Basel Committee focuses only on directly identifiable financial losses for regulatory purposes, ignoring other operational incidents.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What is a “Direct loss”?

Give examples

A

An immediate financial consequence e.g. client compensation or a regulatory fine

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What is meant by the “Non-financial impacts fallacy”?

What can happen if this has not been taken into account?

A

Non-financial impacts have real financial consequences. Failing to identify them properly leads to underestimating operational risk costs.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What is an “Indirect loss”?

Give examples

A

Resulting impacts that can have knock on financial loss, like loss of customers or reputational damage

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

When recording data, why is it important to stick to essential data fields?

A

To avoid over-reporting. Use drop-down menus to ensure consistency in reporting risks, causes, impacts, and controls

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What is the difference between Net and Gross Losses?

A

Net includes reimbursements; gross is total impact

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What are the thresholds in data loss reporting?

Can these be manipulated?

A

Vary from zero to €20,000; must be justified and not manipulated.

17
Q

What are the 4 key dates when reporting an incident?

A
  • Date of discovery (first identified)
  • Date of occurrence (when it actually happened)
  • Date of reporting (entered into database)
  • Date of accounting (when financial impacts occur on the GL)
18
Q

When should material incidents be reported (No. Days)?

What about for smaller events?

A

Within 2-5 days, minor incidents can be summarised periodically.

19
Q

What is meant by “Grouped losses”?

Why might this be necessary?

A

Combine multiple events from the same failure into one loss for accurate reflection.

20
Q

Should a company use potential impact, not actual losses when guaging severity?

What are severity bands?

A

Yes, near misses and unintentional gains should be treated like actual losses.

Use severity bands (e.g., >10k, >100k) for ease.

21
Q

What are the steps in the incident data collection process?

4 Rs, 1 A (NOTE: Reporting sandwich)

A
  • Reporting: Establish a clear and acessible reporting system.
  • Recording: Use standardised forms and fields to record incidents
  • Reviewing: Regularly review and validate the data collected
  • Analysing: Analyze the data to find root cause and trend
  • Reporting: Generate regular reports for management and rregulatory bodies.
22
Q

What is meant by a boundary event?

When the risk impact materialises where?

A

Boundary events occur when the impact materializes in a different risk class than
the cause (e.g., a credit loss due to an operational error).

23
Q

What are the types of incident data?

There are 3.

A
  • Internal Data
  • External Data
  • Near miss data
24
Q

What are the challenges with data collection?

There are 4.

A
  • Under reporting: Fear of blame or repercussions limit this.
  • Data Quality: Ensuring completness and accuracy.
  • Integration: Combining sources can lead to inconsistency.
  • Timeliness: Delays in reporting can affect accuracy and usefulness.
25
What is the Basel Committeee approach to Boundary Event Reporting? ## Footnote Recording records in what line of business?
Basel suggests recording events **where they materialize**, as long as credit losses are covered by risk-weighted capital, without untangling causes.
26
Compared to the Basel approach, what is the management perspective on where to record "Boundary Events"? ## Footnote What issue can this cause? ARIGINAL!!!
* Many firms reclassify boundary events to their original risk class, especially for significant losses. This practice can face resistance from business lines, especially for small, recurring events.
27
What is the purpose of regulatory focus in data management? ## Footnote Ensures the completion of what fields?
Ensures completeness and accuracy of key fields such as dates, loss classifications, group loss consolidation, and comparison of expected vs. settled losses.
28
How do regulators assess comprehensive data collection? ## Footnote What techniques/bodies do they also use?
By evaluating the breadth of incident reporting and validating data through reconciliations with the general ledger, internal audit, or third-party reviews.
29
What role does the General Ledger (GL) play in data collection?
It is a valuable source for identifying operational losses, though its usability depends on ledger rubrics.
30
How are IT logs utilised in operational risk management? ## Footnote How many priorities are there?
Priority 1 and 2 incidents often feed directly into the operational risk database.
31
What are some other sources of data that can benefit operational risk management? ## Footnote Law, CaaSm, IL4U and BBC
Provisions for lawsuits, customer complaints, compensations, and media alerts.
32
Why should firms integrate data collection across departments? ## Footnote What should be leveraged instead?
To reduce effort, duplication, and improve data quality by leveraging existing databases rather than using standalone systems.