<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>VeSiTRUST | COMSYS | RWTH Aachen University</title><link>https://www.comsys.rwth-aachen.de/tags/vesitrust/</link><atom:link href="https://www.comsys.rwth-aachen.de/tags/vesitrust/index.xml" rel="self" type="application/rss+xml"/><description>VeSiTRUST</description><generator>Hugo Blox Builder (https://hugoblox.com)</generator><language>en-us</language><lastBuildDate>Wed, 19 Aug 2026 00:00:00 +0000</lastBuildDate><image><url>https://www.comsys.rwth-aachen.de/media/logo.svg</url><title>VeSiTRUST</title><link>https://www.comsys.rwth-aachen.de/tags/vesitrust/</link></image><item><title>Confidential Observability for Confidential Virtual Machines</title><link>https://www.comsys.rwth-aachen.de/openings/2026/2026-08-security-cvm-obserability/</link><pubDate>Wed, 19 Aug 2026 00:00:00 +0000</pubDate><guid>https://www.comsys.rwth-aachen.de/openings/2026/2026-08-security-cvm-obserability/</guid><description>&lt;h2 id="background"&gt;Background&lt;/h2&gt;
&lt;p&gt;Confidential Virtual Machines (CVMs), such as AMD SEV-SNP VMs, are designed to protect guest memory and execution state even from a potentially untrusted hypervisor or cloud infrastructure provider.
While these technologies significantly strengthen workload isolation, they also make traditional monitoring and debugging more challenging.
Conventional observability often rely on the hypervisor or host infrastructure and may expose sensitive information outside the trusted boundary of the CVM.
Existing systems such as &lt;a href="https://github.com/coconut-svsm/svsm" target="_blank" rel="noopener"&gt;COCONUT-SVSM&lt;/a&gt; introduce a trusted execution layer inside the CVM and are beginning to explore observability-related services.
However, it remains unclear how telemetry can be collected and exported securely without reintroducing the information leakage that confidential computing is intended to prevent.
This thesis explores how useful operational visibility can be preserved while maintaining the confidentiality and integrity guarantees of CVMs.&lt;/p&gt;
&lt;h2 id="your-approach"&gt;Your Approach&lt;/h2&gt;
&lt;p&gt;The goal of this thesis is to investigate how confidential virtual machines can remain observable without weakening the security guarantees provided by technologies such as AMD SEV-SNP (or other VM-based TEEs).
In particular, the thesis will study how operational information such as logs, metrics, and diagnostic data can be made available for monitoring, debugging, and performance analysis while minimizing unnecessary exposure to the untrusted host infrastructure.
A central objective is to determine how much visibility can be provided to operators without reintroducing the same trust assumptions that confidential computing is designed to remove.
Based on this investigation, you will design and implement a prototype that demonstrates a practical approach to confidential observability.
The work will also examine the security and systems-level trade-offs introduced by different observability mechanisms and trust boundaries.
Finally, the prototype will be evaluated in terms of its security properties, performance overhead, and usefulness for operating and debugging confidential workloads.&lt;/p&gt;
&lt;h2 id="what-we-offer"&gt;What We Offer&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Opportunity to work with low-level systems software and trusted computing technologies&lt;/li&gt;
&lt;li&gt;Access to state-of-the-art hardware and software platforms for confidential computing research&lt;/li&gt;
&lt;li&gt;Hands-on experience in designing and implementing secure systems&lt;/li&gt;
&lt;li&gt;A collaborative and supportive research environment&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="what-we-expect"&gt;What We Expect&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Interest in systems security, trusted computing, and virtualization&lt;/li&gt;
&lt;li&gt;Strong programming skills, &lt;strong&gt;preferably in Rust and C&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Knowledge of Linux kernel&lt;/strong&gt; and hypervisor internals is a plus&lt;/li&gt;
&lt;li&gt;Ability to work independently and regular (and effective) communication&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="contact-and-application"&gt;Contact and Application&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;This topic is intended as a Master thesis only, given the scope and complexity of the topic.&lt;/strong&gt;
If you are interested in this topic area, please approach Hajeong.
Please include a &lt;strong&gt;short motivation&lt;/strong&gt; and a &lt;strong&gt;transcript of records&lt;/strong&gt;.
We are looking forward to your application!&lt;/p&gt;</description></item></channel></rss>