bcbs 239 data lineage
|
BIS assessment of BCBS 239 compliance
BCBS 239 lists out four major categories and fourteen principles (11 of which are applicable to banks the remaining three are applicable to regulatory supervisors) The core focus areas for banks include: (1) Overarching Governance and Infrastructure; (2) Risk Data Aggregation Capabilities; and (3) Risk Reporting Practices |
How can data lineage help banks achieve BCBS 239 compliance?
Supervisors across jurisdictions should cooperate to oversee and review the Principles and implement remedial action if needed. With a requirement of BCBS 239, banks with a significant number of data sources are challenged with understanding, managing, and tracing their metadata. Data lineage can help banks achieve BCBS 239 compliance.
Are G-SIBs complying with BCBS 239 principles?
In June 2018, the BCBS published a progress report on global systemically important banks (G-SIBs) adopting BCBS 239 principles. The progress report noted the following in a comparison of 2016 versus 2017 compliance information:
What is BCBS 239?
The purpose of BCBS 239 (Basel Committee on Banking Supervision’s standard number 239) is to ensure that systemically important banks’ risk data aggregation capabilities and internal risk reporting practices give thorough insight into the risks to which they are exposed.
|
Living with BCBS 239
BCBS 239 has set a standard for regulators globally are questioning the value of data lineage in the context of broader data controls. Most banks. |
|
Principles for effective risk data aggregation and risk reporting
Many banks lacked the ability to aggregate risk exposures and identify concentrations quickly and accurately at the bank group level across business lines and |
|
BIS assessment of BCBS 239 compliance
reporting (BCBS 239).1 The set of principles in the paper data lineage data aggregation |
|
ITC_BCBS 239
The objective of BCBS 239 is to help banks improve risk data aggregation governance data flow & lineage and data architecture including the ones on ... |
|
FROM COMPLIANCE TO RISK MANAGEMENT: IMPLEMENTING
challenges they are facing in the process of implementing BCBS 239. The key challenges revolve around data lineage and auditability interoperability |
|
BCBS 239 compliance can beef up banks risk management
To address these systemic issues the BCBS has introduced the. Principles for Effective Risk Data Aggregation and Risk. Reporting |
|
Progress in adopting the Principles for effective risk data
and data lineage; when banks have modified the scope of BCBS 239 implementation (eg data and reports in scope). 3. Adoption of the proportionality ... |
|
BCBS 239 – Raising the standard - November 2017
Since it was issued in January 2013 |
|
Report on the Thematic Review on effective risk data aggregation
global systemically important banks – have fully implemented the BCBS 239 The data lineage analysis which was applied to two selected data points |
|
Data Lineage Handbook 2019
28-Feb-2019 data lineage rose to prominence following the implementation of BCBS 239 in January. 2016 a Basel Committee on. Banking Supervision (BCBS). |
|
Living with BCBS 239 - McKinsey & Company
environment for risk data aggregation and reporting BCBS 239 has set a standard for regulators globally are questioning the value of data lineage in the |
|
BCBS ï - Deloitte
data lineage, responsible organizational unit, type of risk process BCBS #239 Monitoring Risk Reporting Data Governance Processes IT Infrastructure |
|
BCBS 239 Compliance: A Comprehensive Approach - Cognizant
BCBS 239 principles, most domestic systematically important banks (DSIBs) remain in the early data, data transmission and data lineage The next step is to |
|
BCBS 239 - PwC
Since it was issued in January, 2013, BCBS 239 (The Basel Committee on Banking Supervision, including information on data lineage and controls |
|
The Implementation of Basel Committee BCBS 239 - Sciendo
data aggregation and risk reporting (BCBS 239) and outlined the paths to compliance for glob- The lineage of risk data throughout the data lifecycle must be |
|
Solidatus for BCBS 239 - Global Investment Bank Case Study
To meet this challenge it was clear to them that they required a fit-for-purpose metadata management process and data lineage solution Solidatus was chosen in |
|
BCBS 239 Whitepaper - Solidatus
Principles for effective risk data aggregation and risk reporting publication code , BCBS 239) contained performance criteria for global systemically thorough understanding of the lineage of each of the data elements that are being drawn |
|
Progress in adopting the Principles for effective risk data
BCBS, Principles for effective risk data aggregation and risk reporting, January 2013, www bis org/publ/bcbs239 pdf 2 and data lineage; when banks have modified the scope of BCBS 239 implementation (eg data and reports in scope) 3 |
|
BCBS 239 - Celent
assess and on-board additional enhancements to their risk-data aggregation and reporting, and data lineage capabilities under BCBS 239 CHALLENGES |
