1 Ocak 2022 Dergi makalesi Açık Erişim

Soykan, Elif Ustundag; Karacay, Leyli; Karakoc, Ferhat; Tomur, Emrah

MARC21 XML

<?xml version='1.0' encoding='UTF-8'?>
<record xmlns="http://www.loc.gov/MARC21/slim">
  <leader>00000nam##2200000uu#4500</leader>
  <controlfield tag="001">253833</controlfield>
  <datafield tag="540" ind1=" " ind2=" ">
    <subfield code="a">Creative Commons Attribution</subfield>
    <subfield code="u">http://www.opendefinition.org/licenses/cc-by</subfield>
  </datafield>
  <datafield tag="909" ind1="C" ind2="4">
    <subfield code="v">10</subfield>
    <subfield code="p">IEEE ACCESS</subfield>
    <subfield code="c">97495-97519</subfield>
  </datafield>
  <controlfield tag="005">20230728195059.0</controlfield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">As machine learning and artificial intelligence (ML/AI) are becoming more popular and advanced, there is a wish to turn sensitive data into valuable information via ML/AI techniques revealing only data that is allowed by concerned parties or without revealing any information about the data to third parties. Collaborative ML approaches like federated learning (FL) help tackle these needs and concerns, bringing a way to use sensitive data without disclosing critically sensitive features of that data. In this paper, we provide a detailed analysis of state of the art for collaborative ML approaches from a privacy perspective. A detailed threat model and security and privacy considerations are given for each collaborative method. We deeply analyze Privacy Enhancing Technologies (PETs), covering secure multi-party computation (SMPC), homomorphic encryption (HE), differential privacy (DP), and confidential computing (CC) in the context of collaborative ML. We introduce a guideline on the selection of the privacy preserving technologies for collaborative ML and privacy practitioners. This study constitutes the first survey to provide an in-depth focus on collaborative ML requirements and constraints for privacy solutions while also providing guidelines on the selection of PETs.</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">A Survey and Guideline on Privacy Enhancing Technologies for Collaborative Machine Learning</subfield>
  </datafield>
  <datafield tag="909" ind1="C" ind2="O">
    <subfield code="p">user-tubitak-destekli-proje-yayinlari</subfield>
    <subfield code="o">oai:aperta.ulakbim.gov.tr:253833</subfield>
  </datafield>
  <datafield tag="542" ind1=" " ind2=" ">
    <subfield code="l">open</subfield>
  </datafield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="u">Ericsson Res, TR-34390 Istanbul, Turkey</subfield>
    <subfield code="a">Soykan, Elif Ustundag</subfield>
  </datafield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">user-tubitak-destekli-proje-yayinlari</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="z">md5:560f5e9bfc627d21237d57d647955f2a</subfield>
    <subfield code="s">185</subfield>
    <subfield code="u">https://aperta.ulakbim.gov.trrecord/253833/files/bib-b87f5fe6-336a-43f6-bc2a-eacdcdc9919a.txt</subfield>
  </datafield>
  <datafield tag="024" ind1=" " ind2=" ">
    <subfield code="2">doi</subfield>
    <subfield code="a">10.1109/ACCESS.2022.3204037</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">Ericsson Res, TR-34390 Istanbul, Turkey</subfield>
    <subfield code="a">Karacay, Leyli</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">Ericsson Res, TR-34390 Istanbul, Turkey</subfield>
    <subfield code="a">Karakoc, Ferhat</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">Ericsson Res, TR-34390 Istanbul, Turkey</subfield>
    <subfield code="a">Tomur, Emrah</subfield>
  </datafield>
  <datafield tag="650" ind1="1" ind2="7">
    <subfield code="a">cc-by</subfield>
    <subfield code="2">opendefinition.org</subfield>
  </datafield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">publication</subfield>
    <subfield code="b">article</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="c">2022-01-01</subfield>
  </datafield>
</record>