<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="24458" public="1" featured="0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://omeka.org/schemas/omeka-xml/v5 http://omeka.org/schemas/omeka-xml/v5/omeka-xml-5-0.xsd" uri="https://archives.christuniversity.in/items/show/24458?output=omeka-xml" accessDate="2026-06-18T08:54:18+00:00">
  <collection collectionId="7">
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3139">
                <text>Faculty Publications</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </collection>
  <itemType itemTypeId="27">
    <name>Book Chapter</name>
    <description>Faculty Publications- Book Chapter</description>
  </itemType>
  <elementSetContainer>
    <elementSet elementSetId="1">
      <name>Dublin Core</name>
      <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
      <elementContainer>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="237220">
              <text>Logeswaran, K.; Savitha, S.; Suresh, P.; Prasanna Kumar, K.R.; Ponselva Kumar, A.P.; Jayasurya, A.S.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="50">
          <name>Title</name>
          <description>A name given to the resource</description>
          <elementTextContainer>
            <elementText elementTextId="237221">
              <text>Regulatory challenges and compliance in federated learning (FL) for financial applications</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="40">
          <name>Date</name>
          <description>A point or period of time associated with an event in the lifecycle of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="237222">
              <text>01-01-2026</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="48">
          <name>Source</name>
          <description>A related resource from which the described resource is derived</description>
          <elementTextContainer>
            <elementText elementTextId="237223">
              <text>Federated Learning in Finance: Unlocking Privacy-Preserving and Cyber Resilience using AI;pp.1-18</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="43">
          <name>Identifier</name>
          <description>An unambiguous reference to the resource within a given context</description>
          <elementTextContainer>
            <elementText elementTextId="237224">
              <text>&lt;a href="https://doi.org/10.1201/9781003660330-1" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1201/9781003660330-1&lt;/a&gt; &lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/pages/publications/105035271798?origin=resultslist" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/pages/publications/105035271798?origin=resultslist&lt;/a&gt;</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="38">
          <name>Coverage</name>
          <description>The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant</description>
          <elementTextContainer>
            <elementText elementTextId="237225">
              <text>Logeswaran K., Department of AI and Data Science Engineering, School of Engineering and Technology, CHRIST University, Bangalore, India; Savitha S., Department of Computer Science and Engineering, K.S.R. College of Engineering, Tamil Nadu, India; Suresh P., Department of Database System, School of CSE, Vellore Institute of Technology, Vellore, India; Prasanna Kumar K.R., Department of Computer Science and Design, Kongu Engineering College, Tamil Nadu, India; Ponselva Kumar A.P., Department of Information Technology, Kongu Engineering College, Tamil Nadu, India; Jayasurya A.S., Department of Electrical and electronics, University Teknoloi Petronas, Petronas, Malaysia</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="237226">
              <text>The financial sector is increasingly turning toward artificial intelligence (AI) for applications such as fraud detection, credit scoring, and risk management. But that makes it contrary to the regulatory environment. New data protection laws such as the General Data Protection Regulation (GDPR) in Europe and the Digital Personal Data Protection Act (DPDPA) in India impose stringent conditions on data residency, minimization, and sovereignty. This chapter argues that traditional centralized AI systems which require sensitive data to be collected for processing at one site simply do not sit well with these legal requirements, thereby creating massive compliance risks for financial institutions. By way of an extensive architectural study and practical application, this chapter demonstrates that the very basic functions of a traditional AI system tend to contravene prohibitions on cross-border transfers of data. Instead, we propose Federated Learning (FL) as a compliance-by-design solution that solves this sticking point. In other words, by inverting the discredited approachand bringing the algorithm to the data rather than the other way aroundFL ensures that practitioners in different institutions and jurisdictions collaborate on model training without sharing raw data. Only aggregated and anonymized updates on the model are sentinherently complying with certain data residency and data minimization principles. Besides advocating for FL as a core compliant innovation pathway, this chapter also touches on a number of regulatory uncertainties and other potential issues arising from this technology, such as liability, model security, and a need for industry-wide standards. To this end, the chapter clearly states that the adoption of privacy-preserving technologies such as FL has become integral.  2026 selection and editorial matter, Swati Sah, Rejwan Bin Sulaieman, and Aditya Dayal Tyagi; individual chapters, the contributors.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="237227">
              <text>CRC Press</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="46">
          <name>Relation</name>
          <description>A related resource</description>
          <elementTextContainer>
            <elementText elementTextId="237228">
              <text>ISBN: 978-104086966-6; 978-104111510-6;</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="237229">
              <text>English</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="237230">
              <text>Book chapter</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="47">
          <name>Rights</name>
          <description>Information about rights held in and over the resource</description>
          <elementTextContainer>
            <elementText elementTextId="237231">
              <text>Restricted Access; Hardcopy may be available in the library</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="42">
          <name>Format</name>
          <description>The file format, physical medium, or dimensions of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="237232">
              <text>online</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
