<?xml version="1.0" encoding="UTF-8"?>
<mods xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.loc.gov/mods/v3" version="3.1" xsi:schemaLocation="http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-1.xsd">
  <titleInfo>
    <title>Privacy Interpretation of Behavioural-based Anomaly Detection Approaches</title>
  </titleInfo>
  <name type="personal">
    <namePart>Muhammad Imran Khan</namePart>
    <role>
      <roleTerm authority="marcrelator" type="text">creator</roleTerm>
    </role>
  </name>
  <typeOfResource>text</typeOfResource>
  <originInfo>
    <place>
      <placeTerm type="code" authority="marccountry">xx</placeTerm>
    </place>
    <dateIssued encoding="marc">2020</dateIssued>
    <issuance>monographic</issuance>
  </originInfo>
  <language>
    <languageTerm authority="iso639-2b" type="code">ng </languageTerm>
  </language>
  <physicalDescription>
    <form authority="marcform">print</form>
  </physicalDescription>
  <abstract>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 </abstract>
  <note>Open access — freely available to read.</note>
  <identifier type="uri">https://arxiv.org/pdf/2012.11541v1</identifier>
  <location>
    <url displayLabel="Read the full paper (PDF)">https://arxiv.org/pdf/2012.11541v1</url>
  </location>
  <accessCondition type="restrictionOnAccess">Open access — freely available to read.</accessCondition>
  <recordInfo>
    <recordCreationDate encoding="marc">250101</recordCreationDate>
    <recordChangeDate encoding="iso8601">20260901030328.0</recordChangeDate>
  </recordInfo>
</mods>
