<?xml version="1.0" encoding="UTF-8"?>
<record
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.loc.gov/MARC21/slim http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd"
    xmlns="http://www.loc.gov/MARC21/slim">

  <leader>01412nam a2200169 a 4500</leader>
  <controlfield tag="005">20260901030328.0</controlfield>
  <controlfield tag="008">250101s2020    xx     o     000 0 eng d</controlfield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Muhammad Imran Khan</subfield>
  </datafield>
  <datafield tag="245" ind1="1" ind2="0">
    <subfield code="a">Privacy Interpretation of Behavioural-based Anomaly Detection Approaches</subfield>
  </datafield>
  <datafield tag="264" ind1=" " ind2="1">
    <subfield code="b">arXiv</subfield>
    <subfield code="c">2020</subfield>
  </datafield>
  <datafield tag="336" ind1=" " ind2=" ">
    <subfield code="a">text</subfield>
  </datafield>
  <datafield tag="338" ind1=" " ind2=" ">
    <subfield code="a">online resource</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">This paper proposes the notion of 'Privacy-Anomaly Detection' and considers the question of whether behavioural-based anomaly detection approaches can have a privacy semantic interpretation and whether the detected anomalies can be related to the conventional (formal) definitions of privacy semantics such as k-anonymity. The idea is to learn the user's past querying behaviour in terms of privacy and then identifying deviations from past behaviour in order to detect privacy violations. Privacy attacks, violations of formal privacy definition, based on a sequence of SQL queries (query correlations) are also considered in the paper and it is shown that interactive querying settings are vulnerable to privacy attacks based on query sequences. Investigation on whether these types of privacy attacks can potentially manifest themselves as anomalies, specifically as privacy-anomalies was carried </subfield>
  </datafield>
  <datafield tag="506" ind1="0" ind2=" ">
    <subfield code="a">Open access &#x2014; freely available to read.</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2="0">
    <subfield code="u">https://arxiv.org/pdf/2012.11541v1</subfield>
    <subfield code="y">Read the full paper (PDF)</subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="c">ERES</subfield>
  </datafield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">639</subfield>
    <subfield code="d">639</subfield>
  </datafield>
  <datafield tag="952" ind1=" " ind2=" ">
    <subfield code="0">0</subfield>
    <subfield code="1">0</subfield>
    <subfield code="4">0</subfield>
    <subfield code="7">3</subfield>
    <subfield code="8">CYB</subfield>
    <subfield code="a">MAIN</subfield>
    <subfield code="b">MAIN</subfield>
    <subfield code="c">SCICOMP</subfield>
    <subfield code="d">2026-09-01</subfield>
    <subfield code="l">0</subfield>
    <subfield code="p">YGE000900</subfield>
    <subfield code="r">2026-09-01 03:03:28</subfield>
    <subfield code="u">https://arxiv.org/pdf/2012.11541v1</subfield>
    <subfield code="w">2026-09-01</subfield>
    <subfield code="y">PAPER</subfield>
  </datafield>
</record>
