<?xml version='1.0' encoding='utf-8'?>
<?xml-stylesheet type="text/xsl" href="/v2/static/oai2.xsl"?>
<OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/ http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd">
  <responseDate>2026-10-14T05:50:01Z</responseDate>
  <request identifier="oai:figshare.com:article/34021953" metadataPrefix="oai_dc" verb="GetRecord">https://api.figshare.com/v2/oai</request>
  <GetRecord>
    <record>
      <header>
        <identifier>oai:figshare.com:article/34021953</identifier>
        <datestamp>2026-10-06T03:22:27Z</datestamp>
        <setSpec>category_28990</setSpec>
        <setSpec>category_28924</setSpec>
        <setSpec>portal_947</setSpec>
        <setSpec>item_type_14</setSpec>
        <setSpec>month_year_10_2026</setSpec>
      </header>
      <metadata>
        <oai_dc:dc xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"  xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/" xmlns:dc="http://purl.org/dc/elements/1.1/" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/ http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
          <dc:title>Chameleon Forensics (Android): Assume Adversarial Logical Extraction Forensic Tool</dc:title>
          <dc:creator>Joseph Lim (6188483)</dc:creator>
          <dc:creator>Vivek Balachandran (10758771)</dc:creator>
          <dc:subject>Mobile computing</dc:subject>
          <dc:subject>Cybersecurity and privacy not elsewhere classified</dc:subject>
          <dc:subject>mobile security</dc:subject>
          <dc:description>&lt;p dir="ltr"&gt;Existing Android forensic acquisition tools perform well at gaining access to devices and acquiring forensic data when the device behaves as expected. However, what if the device is intentionally modified to detect and disrupt forensic extraction attempts? Anti-forensic techniques can interfere with commonly implemented acquisition methods such as ADB-based extraction or forensic agent deployment, potentially preventing investigators from successfully collecting forensic data.&lt;br&gt;&lt;br&gt;This work builds upon the mobile device forensic acquisition process outlined in NIST SP 800-101 Revision 1. Extending this framework, the proposed approach introduces two additional considerations for Android forensic acquisition in potentially adversarial environments. First, it incorporates a pre-acquisition triage step aimed at helping examiners quickly identify suspicious applications on the device that may interfere with forensic acquisition. Second, it proposes that acquisition workflows should be adversarial-aware, designed in a manner to improve the reliability of forensic evidence collection when anti-forensic mechanisms may be present on the device.&lt;br&gt;&lt;br&gt;The resulting tool introduces an Android logical acquisition tool that assumes the target device may be adversarially modified to disrupt forensic acquisition through known anti-forensic mechanisms. By integrating pre-acquisition triage with adversarial-aware acquisition strategies, Chameleon Forensics aims to support more reliable forensic evidence collection in environments where traditional acquisition assumptions may not hold.&lt;/p&gt;</dc:description>
          <dc:date>2026-08-01T00:00:00Z</dc:date>
          <dc:type>Text</dc:type>
          <dc:type>Conference contribution</dc:type>
          <dc:identifier>10.25447/sit.34021953.v1</dc:identifier>
          <dc:relation>https://figshare.com/articles/conference_contribution/Chameleon_Forensics_Android_Assume_Adversarial_Logical_Extraction_Forensic_Tool/34021953</dc:relation>
          <dc:rights>In Copyright</dc:rights>
        </oai_dc:dc>
      </metadata>
    </record>
  </GetRecord>
</OAI-PMH>
