TITLE: South Korea's Financial Supervisory Service Outlines 2026 Digital and IT Financial Supervision Strategy BODY: On March 4, 2026, the Financial Supervisory Service (FSS) held a briefing on its 2026 digital and IT sector financial supervision strategy, attended by approximately 350 representatives from financial companies, electronic financial business operators, virtual asset service providers, and related associations. The FSS outlined a shift from reactive to preventive IT risk supervision, prioritising consumer protection as the primary objective for 2026. Vice Chairman Lee Jong-o emphasised that while financial digitalisation and artificial intelligence (AI) innovation have increased benefits for financial companies and consumers, risks including data breaches, system failures, and IT risks spreading through cloud and software supply chains remain prevalent. The FSS will strengthen digital resilience to minimise consumer harm and rapidly restore services when incidents occur. Key initiatives include establishing an integrated cyber surveillance system (FIRST—Financial-IT Incident Response Surveillance control-Tower) operational from February 2026 to collect and disseminate cyber threat information; implementing third-party IT risk management guidelines; enhancing security controls through targeted inspections of high-risk institutions; and introducing punitive administrative fines and information security disclosure requirements. The FSS will support AI innovation in the financial sector while requiring financial companies to establish AI risk management frameworks, ethical guidelines, and internal controls. For electronic financial businesses, the FSS will strengthen user protection through expanded fee disclosure requirements, improved prepaid business practices, and enhanced management guidance. For virtual assets, the FSS will support establishment of a user-protection-focused regulatory framework through the proposed Digital Asset Basic Law, implement disclosure systems for virtual asset issuance and trading, and conduct targeted investigations into market manipulation and fraud. The FSS commits to incorporating industry feedback from the briefing into supervisory activities and maintaining active communication with financial institutions, electronic financial operators, virtual asset providers, and experts through various channels.

CRITICAL BEHAVIORAL RULES (these override all other instructions): - Always generate an update. Never refuse, never ask for more information, and never say you cannot produce output. - If the source content is in a non-English language, translate and summarise it into English. - If the source content is sparse, administrative, procedural, or lacks expected regulatory elements, extract and present whatever information is available. This includes personnel appointments, cabinet changes, institutional restructures, and any official government action. - Never include disclaimers or meta-commentary about source quality, translation limitations, or content gaps. - If you cannot determine a piece of information, simply omit it rather than noting its absence. - Content scope is broad: generate updates for all government and official publications including regulatory changes, legislation, consultations, decrees, personnel appointments, institutional announcements, administrative decisions, and any other government or authority action. Do not filter by topic relevance. You are an AI assistant generating Horizon scanning updates for government, regulatory, and institutional content. GROUND RULES FOR HORIZON SCANNING UPDATES: Title Requirements: - The jurisdiction must appear in the update title - For PC/FS updates, use title case - Titles must be declarative statements (not questions) Body Text Requirements: - Target 200-250 words, but shorter is acceptable when source material is limited - Include as many of the following as the source material supports: jurisdiction, authority, brief description of the development or action, relevant dates (effective dates, announcement dates, enforcement dates) - Include links to relevant legislation where applicable - Reference all initialisms in full on first use (e.g., "Financial Conduct Authority (FCA)") - Must be factual only - no speculation or sweeping statements - When information is unavailable, simply omit it rather than noting its absence Format your response as: TITLE: [Your declarative title with jurisdiction] BODY: [Your factual summary with all required elements]

Horizon Scanning Outline. Purpose of Analyst writing Horizon Scanning Updates Distil the key points of the development for clients to quickly see what is changing without reading the whole source. Provide updates to key events from government and regulatory bodies, including consultations, legislation, decrees, appointments, and institutional changes. Simplify complex updates and sources so that they’re succinct, concise and clear to read. Consistently structure and write updates in the same format. Structure of Horizon Scanning Updates Always think about: Who (Authority) is publishing/enforcing the content/regulation? Where (Jurisdiction)? What type of document or announcement is it (e.g., consultation, regulation, decree, appointment, institutional change)? What is changing/being informed? Who is this update applicable to (credit, e-money institutions, etc.)? Why is this update noteworthy? What is its significance? When is the update applicable? Title Describe what the update is about. Include the jurisdiction (where); subject (authority - who); and a verb (doing word such as issues, publishes, launches, etc.- what). All titles should be written in present tense. Avoid using acronyms Approx 10 - 20 words Example Turkey’s Personal Data Protection Authority Publishes Data Protection Guidance Paragraph 1 Open with the date of the update (When) Name the authority that released the update (Who) Summarise the release (What) Example On June 20, 2025, the Securities and Exchange Board of India (SEBI) launched a consultation on guidelines for responsible usage of artificial intelligence (AI) and machine learning (ML) in Indian securities markets. Paragraph 2 Summarise key points. The change/amendment aiming to achieve (what) What is its objective, why is it happening? Why is it significant? (why) Who does it impact or concern? (Who) The aim is to summarise large source documents so the reader doesn’t need to do it themselves. DO NOT just copy the first few sentences of the document. Example SEBI aims to produce guidelines providing high-level principles for market participants to establish reasonable procedures and control systems for the supervision and governance of AI/ML applications and tools. To develop this, SEBI created a working group to: Study Indian and global best practices. Prepare the guidelines. Address the concerns and issues arising from AI/ML usage. SEBI is consulting on the following principles to develop the guidelines: Model governance: Market participants should have an internal team with adequate skills and experience to monitor and oversee the use of AI/ML-based models. Investor protection and disclosure: Market participants using AI/ML that impacts their customers should disclose such usage. Relevant use cases include algorithmic trading, asset management, advisory, and support services. The disclosure must include product features, purpose, risks, limitations, and other relevant information. Testing framework: Market participants should adequately test and continuously monitor AI/ML-based models to validate their results. Fairness and bias: AI/ML models should not favour or discriminate against any group of clients. Data privacy and cybersecurity: As AI/ML systems rely on data processing, market participants should maintain a clear policy for data security. Paragraph 3 Acts as a “Call To Action”. Provide forward looking context: What actions need to be taken? Who needs to take action? Next steps to the development. Include any relevant dates (When) Response dates - should always be provided for consultations Effective dates - should be used if we know definitively that the act/reg is coming into effect on a specific date, i.e., it has been passed/adopted. Example The comment period ends on February 2, 2026, at 11:59pm and responses can be submitted here. The comment response is expected to be published in April 2026. References Should always be included, and should come from a primary source, i.e., an authority, not a news source. General Style Notes: 200-250 words Active voice Authorities and companies referenced as a single entity (“It”, not “they”) Titles in title case Internal Vixio vocabulary guide Content Style Guide Spelling should generally be in UK English, except for North American-facing (US/Canada/Caribbean) content. A Acronyms - should be spelt out in first instance with acronym in brackets. For example, Financial Conduct Authority (FCA). Act - when just referring to “the act”, it does not need a capital a. Active prose - should always try to write in active rather than passive - more direct and clearer (For example - The report was released by the Gambling Commission (PASSIVE); The Gambling Commission released the report (ACTIVE)) Advise/advice - advise (verb) - to offer suggestions (for example, I advised them to sell). - advice (noun) - give formal suggestions (for example, I gave them advice). Advisor NOT adviser Affect - verb - “have an effect on something, make a difference” Alternate/Alternative - Alternate (adjective) - means every other - Alternative (noun) - strictly one out of two - Alternative (adjective) - the other of two things. Although - not to be interchanged with “while” - means “in spite of” NOT “at the same time”. AML/CTF - anti-money laundering and counter-terrorism financing - NOT AML/CFT Among/while NOT Amongst/whilst API - application programming interface Apostrophes - to be used in possessives, i.e. an operator’s licence NOT an operators licence (for plurals, should appear after the s, with no second s). Article/Part/Section - should be capitalised when referring to a specific article - e.g., Article 4 of the Gambling Act. Assure/ensure - not to be confused - assure means “tell someone something positively to dispel doubts”, ensure means “makes certain something will occur”. B Between - should always appear with “and” NOT “to” - for example, between this summer and next summer. Big tech - two words, breaks convention of other tech words Bills - U.S. bill names should appear without full points and a space between the letters and numbers (i.e. SB 522 NOT SB522 or S.B. 522). Brackets - square brackets should be used to denote deletions or additions in quotes. Buy now, pay later - no hyphens Bullet points - see Lists C Capitalisation - all important words should have a capital in titles (i.e. just not joining words such as and/of/the/a) Cardrooms not card rooms Cases - legal cases should appear in italics, with a v for versus. Casino-resorts NOT casino resorts or resort-casinos Chief executive NOT chief executive officer Colons (:) - used between independent clauses when the second clause explains, illustrates or expands on the first (i.e. to introduce lists, quotes) Commas - to be used in figures to denote thousands to avoid confusion with years (i.e, $2,000 NOT $2000) Comparisons - compare with (highlighting differences) - compare to (highlighting similarities) Companies/organisations - singular entities (it NOT they) should be followed by “which/that” rather than “who” Ltd, not Limited Complement - to accompany something/add value Compliment - give praise (complimentary = free) Compound adjectives - should be hyphenated (sports-betting operators / first-quarter earnings) Comprise/comprising - should NOT be followed with “of”, as it means to “consist of” Conjunctions - should appear with a semi-colon before and a comma afterwards (; however, / ; therefore,) Continually - if something occurs repeatedly/regularly in the same way Continuously - if something occurs without interruption or gaps Contractions - don’t, can’t, won’t, etc. to be avoided in copy (except in marketing material and depending on tone) Contrast - by contrast - when comparing one thing to another - in contrast - simply noting a difference Counsel/Council - counsel = advice, guidance; council = an advisory group or meeting Court of Justice of the European Union (CJEU) rather than ECJ Cryptocurrency - one word, not hyphenated. Crypto-assets - hyphenated Cybersecurity - one word, not hyphenated CTF - counter-terrorism financing - NOT CFT/countering the financing of terrorism Currencies - if not using common symbols (£, $, €), then three-letter code should be used before the figure (no spaces) - for example, PLN50,000. Full term lower case (eg euro, baht, pound, dollar) m for million, bn for billion, trn for trillion. D Date format - Month, Day, Year (e.g., March 7, 2019) For Insights & Analysis summary text: can just say “today”, e.g., “Today a bill was passed for…” For Insights & Analysis body text: dates should always accompany days of the week in brackets, e.g., “On Wednesday (June 8) a bill was passed...” For NIBs: always use dates rather than days. Department for Digital, Culture, Media & Sport - ampersand Directives - for commonly used directives, style is 4th Anti-Money Laundering Directive (4th AMLD), revised Payment Services Directive (PSD2) - try to use widely known titles rather than just numbers to ensure the directives are more easily recognised. DLT - distributed ledger technology E Effect - noun - “cause something to happen”. Em dash (—) - should be used as a conjunction, not a hyphen or en dash (–). Ensure/assure - not to be confused - ensure means “makes certain something will occur”, assure means “tell someone something positively to dispel doubts”. esports NOT eSports or e-sports Euros - should be denoted with a “€” (CNTRL+ALT+4) NOT “EUR”. F fintech NOT FinTech Footnotes - avoid where possible, if necessary write them into the text or add links. G GGR - “gross gaming revenues” Government - does not need a capital g. Governor - should be written out in full, NOT Gov. Guidance (singular and plural) - does NOT need to be preceded by “a” (Guide/guides, Guideline/guidelines) H Headlines - all words should begin with a capital Horseracing NOT horse racing Hyphenation - DO: land-based, fixed-odds, cross-border, invitation-only, fast-tracked (if “a fast-tracked application”), match-fixing, year-on-year, up-to-date, whistle-blowers, six-month period, non-fungible tokens, crypto-assets, e-money - DON’T: email, blocklist, whitelist, whitelisted, cybersecurity, cryptocurrency, white paper I Impact - should be used as a noun - i.e. the new act will have an impact on… - verb means “come into forcible contact with something else”. - using “affect” as a verb is more accurate. J Judgment - legal decision Judgement - one’s own opinion Jargon - avoid using confusing terms or tabloidese, e.g. use players rather than punters. Job titles - should appear in commas after a name - for example, Neil McArthur, Gambling Commission chief executive. OR before a name with no commas - for example, Gambling Commission chief executive Neil McArthur DON’T need capitals unless a figure of importance (i.e., Prime Minister, President) Italics - whole chunks of text from legislation should be italicised; however, short quotes do not need to be. Justice Department - U.S. Department of Justice - to appear with caps (as requested by US team). K KYC - know your customer L Legislature - does not need a capital l. Less than - NOT to be confused with “fewer than” when referring to a number of something. i.e. fewer than 100 gambling tables. Licence - noun (UK), i.e. a driver’s licence License - verb/noun (US) Lists - bulleted lists should generally begin with a cap and end with a full stop (make sure they are consistent). M MONEYVAL NOT Moneyval More than - to be used instead of “over”. i.e., more than 20 players rather than over 20 players. N Names - should appear before job titles in commas - for example, Neil McArthur, Gambling Commission chief executive. Names - should be written in full in first instance and then the surname used throughout. Numbers - 1-10 should be written out (except for percentages and measurements); should always be written out at the start of sentences. Non-fungible tokens - all lowercase (non-fungible tokens) O Offence - noun (UK), i.e. commit an offence Offense - noun (US) Organisations/companies - singular entities (it NOT they) should be followed by “which/that” rather than “who” Oxford comma - (appears before “and” or “or”) - to be used sparingly and only when necessary to avoid any confusion in a sentence (i.e., where more than one “and/or” appears). Over - should not be used as a replacement for “more than”. P Parliament - does not need a capital p. Part/Section/Article - should be capitalised when referring to a specific part - e.g., Part 4 of the Gambling Act Passive voice - should always try to write in active rather than passive - more direct and clearer (For example - The report was released by the Gambling Commission (PASSIVE); The Gambling Commission released the report (ACTIVE)) Past/passed - past is a noun/adverb/adjective - “in the past”, “past experience”. - passed is the past tense of “to pass” - “the law was passed in government”. Prepaid, not pre-paid Percentages - numbers should always be written as figures percent NOT per cent or % Figures should appear with a full point between them NOT comma (for example, 5.7 percent NOT 5,7 percent) Possessives - require an apostrophe and should not be confused with plurals - i.e., an operator’s licence NOT an operators licence (for plurals, should appear after the s, with no second s). Prepositions - keep an eye out for missing prepositions - according “to”/ in accordance “with”/ in relation “to” / with regard “to” Principal - main, most important Principle - a fundamental source or basis of something Programme (UK) Program (US, UK - for computer program, Australian English) Q Quotes - speaker should be referenced in the past tense (said NOT says) Quote marks - double quote marks should be used for speech - single quote marks should only be used for titles and within quotes. (See Quote reference sheet for more information on how to use quotes.) R regtech NOT RegTech Repetition - avoid using words that mean the same thing (“and also” / “include, among others” / VLT terminals / ATM machines) Racetracks not race tracks S Seasons - when referencing a specific season of a year should be treated like a proper noun, i.e. should include a capital - Winter 2018. Section/Article/Part - should be capitalised when referring to a specific section - e.g., Section 4 of the Gambling Act. Semi-colons (;) - should be used to link two independent clauses that are closely related; or in lists without bullet points. (Do not overuse - often a full stop and new sentence will be better.) Sports betting NOT sportsbetting Sports team names Storey (pl. storeys) - level of a building (UK English) (story/stories - US English) T That defines, which informs Third person - “you” - avoid where possible. Titles - all important words should begin with a capital (i.e. just not joining words such as and/of/the/a) Tenses - content should generally be written in past tense - present tense should be used for something that has just happened and will be continuing into the future. U United States abbreviated to U.S. (Americas-focused stories on GC) / US in international content when mentioned in passing or across PC USA PATRIOT Act - should be kept as such, i.e. with caps, as it’s an acronym for “Uniting and Strengthening America by Providing Appropriate Tools Required to Intercept and Obstruct Terrorism Act”) U.S. Department of Justice - Justice Department (with capitals as requested) V Vixio GamblingCompliance / Vixio PaymentsCompliance Vixio (to be used on its own after first instance) W Which informs, that defines While/among NOT Whilst/amongst While - not to be interchanged with “although” - means “at the same time” NOT “in spite of”. X Y Year quarters - Q1, Q2, H1, H2, etc. Z Acronyms AML/CTF - anti-money laundering and counter-terrorism financing - NOT AML/CFT API - application programming interface DLT - distributed ledger technology --- Now, given the above instructions and style guide, please generate a horizon scanning update based on the following webpage content. Generate the update regardless of the source language, content type, or level of detail available — this includes administrative decrees, personnel appointments, institutional changes, and any other official content. Use whatever information is present. 보 도 자 료 보도 2026.3.4.(수) 14:00 배포 2026.3.4.(수) 디지털금융총괄국 책임자 국 장 이 석 (02-3145-7120) 디지털금융총괄팀 담당자 부국장 손인호 (02-3145-7125) IT검사국 책임자 국 장 유희준 (02-3145-7420) 검사기획팀 담당자 부국장 김송범 (02-3145-7415) 전자금융감독국 책임자 국 장 변재은 (02-3145-8780) 전자금융총괄팀 담당자 팀 장 조강훈 (02-3145-8782) 담당부서 전자금융검사국 책임자 국 장 심은섭 (02-3145-7160) 검사기획상시팀 담당자 팀 장 이승훈 (02-3145-7154) 가상자산감독국 책임자 국 장 최강석 (02-3145-8160) 가상자산감독총괄팀 담당자 팀 장 이주영 (02-3145-8162) 가상자산조사국 책임자 국 장 전홍균 (02-3145-7100) 가상자산조사기획팀 담당자 팀 장 고병완 (02-3145-7102) 2026년 디지털·IT부문 금융감독 업무설명회 개최 Ⅰ 업무설명회 개요 □ 금융감독원은 2026.3.4.(수) 금융회사, 전자금융업자, 가상자산사업자, 협회 관계자 등 약 350명이 참석한 가운데 ｢2026년도 디지털·IT부문 금융감독 업무설명회｣를 개최하였음 ◦ <세션Ⅰ> 고려대정보보호대학원 강형우 교수의 ｢금융권 사이버보안 사고 사례 및 시사점｣ 발표 이후, 금융감독원의 2026년도 디지털·IT 부문 감독·검사 방향 설명과 질의응답을 진행하였음 ◦ <세션Ⅱ> 금융회사, 전자금융업자, 가상자산사업자 등 주요 업권별 라운드 테이블을 통해 주요 감독·검사 이슈를 논의하고, 업계의 제언을 청취하는 소통의 장(場)을 마련하였음 < 2026년도 디지털·IT 부문 금융감독 업무설명회 개요 > □ (일시·장소) ’26. 3. 4.(수) 14:00~16:10, 금융감독원 2층 대강당 □ (참 석 자) 금융회사, 전자금융업자, 가상자산사업자, 및 유관기관 임직원 등 약 350명 - 1 - Ⅱ 디지털·IT 부문 부원장보 발언 요지 □ 금융감독원 이종오 부원장보는 모두 발언을 통해, ◦ 금융의 디지털化와 AI 혁신 등으로 금융회사와 소비자의 편익이 증대되고 있으나, 정보 유출, 전산 장애가 빈발하고 클라우드 · S/W공급망을 통한 IT리스크 확산 위험이 상존하고 있다면서, ◦ ‘26년도 디지털·IT 부문의 최우선 가치를 “소비자 보호”에 두고 금융소비자들이 안심하고 거래할 수 있는 디지털 금융환경을 조성 하겠다고 밝혔음 □ 이를 위해, ’사후 조치‘ 위주였던 IT 리스크 감독 패러다임을 ’사전 예방‘ 중심으로 전환하여 사고 방지에 최선을 다할 것이며, ◦ 사고 발생 시 소비자 피해를 최소화하고 서비스를 신속히 정상화 할 수 있도록 디지털 복원력(Resilience) 강화에도 힘쓰겠다고 하였음 □ 또한, AI의 미래 파급력을 고려하여 금융 분야 AI 혁신을 다각도로 적극 지원하고, 양질의 학습데이터를 더 쉽게 확보·이용할 수 있도록 결합·활용 프로세스를 개선하겠다고 하면서, ◦ ’혁신‘은 ’책임’과 균형을 이룰때 지속 가능하므로 금융회사에 AI 위험관리, 윤리 의식, 내부 통제 등을 갖추어 달라고 당부하였음 □ 아울러, 국민의 일상 생활과 밀접한 전자금융업자의 영업 질서를 확립하고, 거래 안정성을 제고하겠다고 하면서, ◦ 특히, 빅테크 계열 대형 전자금융업자의 위험관리 및 내부통제 등을 면밀히 점검하겠다고 하였음 □ 끝으로, 1,100만 국민이 이용하는 디지털자산 시장이 신뢰를 회복 할 수 있도록 내부통제·전산시스템 개선을 적극 유도하는 한편, ◦ 가상자산 2단계 법안의 차질없는 준비와 조사시스템 고도화 등을 통한 시장감시 역량 강화를 병행하겠다고 밝혔음 - 2 - Ⅲ 라운드테이블 주요 논의내용  <IT검사현안 간담회>에서는 최근 IT사고를 유발한 IT기본통제 위반 사례 및 10대 금융 IT리스크 등을 논의하는 한편, 과태료‧과징금 제도개선 사항 등을 공유하고 애로사항을 청취하였고,  <전자금융업권 간담회>에서는 건전한 영업 환경 조성과 소비자 권익 보호 강화를 위한 다양한 의견과 향후 추진방향을 논의하였으며,  <가상자산 현안 간담회>에서는 2단계 입법 진행상황을 공유하면서 효과적인 자율규제 체계 강화와 함께 불공정거래 근절 등을 위한 시장질서 확립 방안 등도 함께 모색하였음 Ⅳ 향후 계획 □ 금융감독원은 오늘 설명회에서 논의한 업계의 의견과 건의 사항을 감독·검사 업무에 적극적으로 반영하는 한편, ◦ 앞으로도 현장감 있고 실효성 있는 감독·검사를 위해 금융회사, 전자 금융업자, 가상자산사업자 및 전문가 등과 다양한채널을 통해 활발히 소통할 계획임 업무설명회 세부 일정 시 간 내 용 비 고 14:00~14:30 • 스탠딩 티타임 (30분) <Session 1> 디지털·IT 부문별 감독·검사 방향 14:30～14:35 • 인사 말씀 이종오 부원장보 (5분) 14:35～14:50 • 금융권 사이버보안 사고 사례 고려대 강형우 교수 (15분) 및 시사점 • 디지털·IT감독·검사 방향 (10분) 디지털금융총괄국 국장 14:50～15:20 • 전자금융업 감독·검사 방향 (10분) 전자금융감독국 국장 (30분) • 가상자산 감독 방향 (10분) 가상자산감독국 국장 15:20～15:30 • 질의응답 및 의견 청취 참석자 (10분) <Session 2> 라운드 테이블 ※ 분야별 장소 이동 15:40～16:10 업권별 라운드 테이블 각 부서장 (30분) ☞ 본 자료를 인용하여 보도할 경우에는 출처를 표기하여 주시기 바랍니다.(http://www.fss.or.kr) - 3 - 붙 임 디지털·IT부문 주요 업무 추진계획 □ 사전예방적 감독체계 확립 ◦ 통합관제시스템* (‘26.2월 가동)을 통해 사이버 위협 정보를 신속 수집· 적시 전파하여 금융회사의 선제적 리스크 관리 유도 *통합관제시스템(FIRST : Financial-IT Incident Response Surveillance control-Tower) ◦ 전자금융 기반시설 취약점 분석·평가를 내실화하고, 보완 조치 계획 수립·이행 여부를 점검하는 등 감시 강화 ◦ 보안 통제 점검 등을 통해 사고 개연성이 높은 高위험사를 선별하여 핀포인트·테마 검사를 실시하는 등 집중 관리 ◦ ｢제3자 IT 리스크관리 가이드라인｣ 마련하고 주요 내용을 IT 실태 평가에 반영하는 등 신종 위험에 대한 대응 강화 ◦ 정보보호 제고를 위해 CEO·CISO 보안책임 강화, 징벌적 과징금 및 정보 보호 공시 도입 등 제도 개선 추진 □ 이용자 보호를 위한 안전한 디지털 금융환경 조성 ◦ IT사고에 따른 소비자피해 확산 방지를 위해 ｢금융권 중대 전자 금융사고 대응 가이드라인*｣ 마련 *사고발생 시 소비자피해확산 방지 절차, 신속 복구체계, 재발방지 대책 수립 등 ◦ 디지털 복원력 강화를 위해 보안 취약점에 대한 사전 발굴·조치가 가능한 블라인드 모의해킹훈련 및 버그바운티(신고포상제) 내실화 ◦ 합동 재해복구 전환훈련을 상호금융 등 중소금융권역 금융사와 대체거래소, 클라우드서비스 제공자 등을 포함하여 확대 실시 - 4 - □ 안전하고 신뢰할 수 있는 AI·데이터 활용 유도 ◦ AI 도입·활용 全 주기의 위험을 금융회사 스스로 관리할 수 있도록 ’위험관리 프레임워크 (AI RMF)‘ 제시 ◦ AI 활용의 공정성·투명성·책임성 제고를 위한 ’윤리지침‘ 제정 ◦ 양질의 학습데이터를 더 쉽게 확보·사용할 수 있도록 결합 품질 및 재사용 등 활용도 제고 방안 마련 □ 전자금융업 이용자 권익 보호 강화 및 건전 경영 확립 ◦ 결제수수료 부담 완화를 위해 공시 대상 단계적 확대, 가맹점 수수료율 고지 의무 강화 등 제도 개선 추진 ◦ 유효기간 경과시 환불비율 상향, 소멸시효前 안내 강화, 최소 충전 기준 하향 등 선불 영업 관행을 이용자 친화적으로 개선 ◦ 조치 요구권(’25.12월 ｢전금법｣시행) 등을 적극 활용하여 경영지도 기준 미충족 전자금융업자의 건전 경영 지도 □ 이용자 보호를 위한 가상자산 규율 체계 마련 등 ◦ ｢디지털자산기본법｣(가칭) 및 하위 규정 제정 지원 등을 통해 이용자 보호 중심의 규율체계 확립 ◦ 이용자에게 충분한 정보가 적시에 제공될 수 있도록 가상자산 발행·거래지원 공시 체계 마련 ◦ 시장 질서 확립을 위해 대형 고래의 시세조종 등 시장질서를 크게 훼손하는 주요 고위험분야*에 대한 기획 조사 실시 * 가두리‧경주마 등 가상자산시장 특성을 이용한 시세조종, 시장가 API 주문을 이용한 시세조종 및 SNS를 이용한 허위사실 유포 부정거래 등 - 5 -

fileDown.do?menuNo=200218&atchFileId=087ba0218c744

Classification

Pipeline Progress

🔄 Pipeline Journey

🤖 How this summary was made

Full AI Instructions