<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//TaxonX//DTD Taxonomic Treatment Publishing DTD v0 20100105//EN" "../../nlm/tax-treatment-NS0.dtd">
<article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:tp="http://www.plazi.org/taxpub" article-type="research-article" dtd-version="3.0" xml:lang="en">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">109</journal-id>
      <journal-id journal-id-type="index">urn:lsid:arphahub.com:pub:3dc5f44e-8666-58db-bc76-a455210e8891</journal-id>
      <journal-title-group>
        <journal-title xml:lang="en">JUCS - Journal of Universal Computer Science</journal-title>
        <abbrev-journal-title xml:lang="en">jucs</abbrev-journal-title>
      </journal-title-group>
      <issn pub-type="ppub">0948-695X</issn>
      <issn pub-type="epub">0948-6968</issn>
      <publisher>
        <publisher-name>Journal of Universal Computer Science</publisher-name>
      </publisher>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="doi">10.3217/jucs-025-09-1174</article-id>
      <article-id pub-id-type="publisher-id">22651</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Research Article</subject>
        </subj-group>
        <subj-group subj-group-type="scientific_subject">
          <subject>H.2 - DATABASE MANAGEMENT</subject>
          <subject>H.3.7 - Digital Libraries</subject>
          <subject>H.5.4 - Hypertext/Hypermedia</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>The Effects of Platforms and Languages on the Memory Footprint of the Executable Program: A Memory Forensic Approach</article-title>
      </title-group>
      <contrib-group content-type="authors">
        <contrib contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Al-Sharif</surname>
            <given-names>Ziad A.</given-names>
          </name>
          <email xlink:type="simple">fzasharif@just.edu.jo</email>
          <xref ref-type="aff" rid="A1">1</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Al-Saleh</surname>
            <given-names>Mohammed I.</given-names>
          </name>
          <xref ref-type="aff" rid="A1">1</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Jararweh</surname>
            <given-names>Yaser</given-names>
          </name>
          <xref ref-type="aff" rid="A1">1</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Shatnawi</surname>
            <given-names>Ahmed S.</given-names>
          </name>
          <xref ref-type="aff" rid="A1">1</xref>
        </contrib>
      </contrib-group>
      <aff id="A1">
        <label>1</label>
        <addr-line content-type="verbatim">Jordan University of Science and Technology, Irbid, Jordan</addr-line>
        <institution>Jordan University of Science and Technology</institution>
        <addr-line content-type="city">Irbid</addr-line>
        <country>Jordan</country>
      </aff>
      <author-notes>
        <fn fn-type="corresp">
          <p>Corresponding author: Ziad A. Al-Sharif (<email xlink:type="simple">fzasharif@just.edu.jo</email>).</p>
        </fn>
        <fn fn-type="edited-by">
          <p>Academic editor: </p>
        </fn>
      </author-notes>
      <pub-date pub-type="collection">
        <year>2019</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>28</day>
        <month>09</month>
        <year>2019</year>
      </pub-date>
      <volume>25</volume>
      <issue>9</issue>
      <fpage>1174</fpage>
      <lpage>1198</lpage>
      <uri content-type="arpha" xlink:href="http://openbiodiv.net/D9888CB1-B651-5BA8-86EE-3104D45DA11E">D9888CB1-B651-5BA8-86EE-3104D45DA11E</uri>
      <uri content-type="zenodo_dep_id" xlink:href="https://zenodo.org/record/4840894">4840894</uri>
      <history>
        <date date-type="received">
          <day>22</day>
          <month>12</month>
          <year>2018</year>
        </date>
        <date date-type="accepted">
          <day>09</day>
          <month>07</month>
          <year>2019</year>
        </date>
      </history>
      <permissions>
        <copyright-statement>Ziad A. Al-Sharif, Mohammed I. Al-Saleh, Yaser Jararweh, Ahmed S. Shatnawi</copyright-statement>
        <license license-type="creative-commons-attribution" xlink:href="" xlink:type="simple">
          <license-p>This article is freely available under the J.UCS Open Content License.</license-p>
        </license>
      </permissions>
      <abstract>
        <label>Abstract</label>
        <p>Identifying the software used in a cybercrime can play a key role in establishing the evidence against the perpetrator in the court of law. This can be achieved by various means, one of which is to utilize the RAM contents. RAM comprises vital information about the current state of a system, including its running processes. Accordingly, the memory footprint of a process can be used as evidence about its United States of Americage. However, this evidence can be influenced by several factors. This paper evaluates three of these factors. First, it evaluates how the used programming language affects the evidence. Second, it evaluates how the used platform affects the evidence. Finally, it evaluates how the search for this evidence is influenced by the implicitly used encoding scheme. Our results should assist the investigator in its quest to identify the best amount of evidences about the used software based on its execution logic, host platform, language used, and the encoding of its string values. Results show that the amount of digital evidence is highly affected by these factors. For instance, the memory footprint of a Java based software is often more traceable than the footprints of languages such as C++ and C#. Moreover, the memory footprint of a C# program is more visible on Linux than it is on Windows or Mac OS. Hence, often software related values are successfully identified in RAM memory dumps even after the program is stopped.</p>
      </abstract>
    </article-meta>
  </front>
</article>
