<node id="686128">
  <nid>686128</nid>
  <type>event</type>
  <uid>
    <user id="28475"><![CDATA[28475]]></user>
  </uid>
  <created>1761945562</created>
  <changed>1761945642</changed>
  <title><![CDATA[Ph.D. Proposal Oral Exam - Athanasios Moschos]]></title>
  <body><![CDATA[<p><strong>Title:&nbsp; </strong><em>From Ideal To Real: Evolving CPU Hardware Trojan Attacks</em></p><p><strong>Committee:&nbsp;</strong></p><p>Dr.&nbsp;Keromytis, Advisor&nbsp;&nbsp;</p><p>Dr. Monrose, Chair</p><p>Dr. Prvulovic</p><p>Dr. Antonakakis</p><p>Dr. Stavrou</p>]]></body>
  <field_summary_sentence>
    <item>
      <value><![CDATA[From Ideal To Real: Evolving CPU Hardware Trojan Attacks]]></value>
    </item>
  </field_summary_sentence>
  <field_summary>
    <item>
      <value><![CDATA[<p>The objective of the proposed research is to chart the design space of realistic CPU hardware trojan attacks, focusing on control reliability and post-deployment survivability rather than merely minimizing a trojan’s footprint. We first show that OS-driven context switches inhibit CPU-aimed hardware trojan atacks; to mitigate this we introduce IRT, a trojan design resilient to asynchronous interrupts and suitable for insertion during the fabrication stage. Next, we relax the common but restrictive assumption that attackers require arbitrary code execution (RCE) to control trojans on victim devices; instead we propose SURF, which leverages the hardware manifestation of JavaScript memory indexing operations to reliably activate payloads via runtime engines. SURF demonstrates, for the first time, that CPU trojans can be controlled through ubiquitous runtime systems, increasing the trojan attack generality and scalability on commercial devices. Finally, we outline ongoing research on parametric trojans with distinct trigger sequences that allow attacker-side identification, while protecting the deployed CPU trojans even after one trojan instance is discovered. Together, these contributions advance a more practical understanding of how CPU hardware trojans can persist and operate in real-world systems.</p>]]></value>
    </item>
  </field_summary>
  <field_time>
    <item>
      <value><![CDATA[2025-11-10T14:30:00-05:00]]></value>
      <value2><![CDATA[2025-11-10T16:30:00-05:00]]></value2>
      <rrule><![CDATA[]]></rrule>
      <timezone><![CDATA[America/New_York]]></timezone>
    </item>
  </field_time>
  <field_fee>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_fee>
  <field_extras>
      </field_extras>
  <field_audience>
          <item>
        <value><![CDATA[Public]]></value>
      </item>
      </field_audience>
  <field_media>
      </field_media>
  <field_contact>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_contact>
  <field_location>
    <item>
      <value><![CDATA[Room 3402, Klaus]]></value>
    </item>
  </field_location>
  <field_sidebar>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_sidebar>
  <field_phone>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_phone>
  <field_url>
    <item>
      <url><![CDATA[]]></url>
      <title><![CDATA[]]></title>
            <attributes><![CDATA[]]></attributes>
    </item>
  </field_url>
  <field_email>
    <item>
      <email><![CDATA[]]></email>
    </item>
  </field_email>
  <field_boilerplate>
    <item>
      <nid><![CDATA[]]></nid>
    </item>
  </field_boilerplate>
  <links_related>
      </links_related>
  <files>
      </files>
  <og_groups>
          <item>434371</item>
      </og_groups>
  <og_groups_both>
          <item><![CDATA[ECE Ph.D. Proposal Oral Exams]]></item>
      </og_groups_both>
  <field_categories>
          <item>
        <tid>1788</tid>
        <value><![CDATA[Other/Miscellaneous]]></value>
      </item>
      </field_categories>
  <field_keywords>
          <item>
        <tid>102851</tid>
        <value><![CDATA[Phd proposal]]></value>
      </item>
          <item>
        <tid>1808</tid>
        <value><![CDATA[graduate students]]></value>
      </item>
      </field_keywords>
  <field_userdata><![CDATA[]]></field_userdata>
</node>
