index.xml

<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Thomas Pasquier</title>
    <link>https://tfjmp.org/</link>
      <atom:link href="https://tfjmp.org/index.xml" rel="self" type="application/rss+xml" />
    <description>Thomas Pasquier</description>
    <generator>Wowchemy (https://wowchemy.com)</generator><language>en-us</language><lastBuildDate>Mon, 02 Feb 2026 00:00:00 +0000</lastBuildDate>
    <image>
      <url>https://tfjmp.org/media/icon_hu08a0612ece3264b0c60a561067d923a4_34621_512x512_fill_lanczos_center_3.png</url>
      <title>Thomas Pasquier</title>
      <link>https://tfjmp.org/</link>
    </image>
    
    <item>
      <title>RegTrack: Uncovering Global Disparities in Third-party Advertising and Tracking</title>
      <link>https://tfjmp.org/publication/2026-madweb/</link>
      <pubDate>Mon, 02 Feb 2026 00:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/publication/2026-madweb/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Toward Practical and Usable Provenance-based Intrusion Detection Systems</title>
      <link>https://tfjmp.org/publication/2025-usenix-login/</link>
      <pubDate>Fri, 05 Sep 2025 00:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/publication/2025-usenix-login/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Sometimes Simpler is Better: A Comprehensive Analysis of State-of-the-Art Provenance-Based Intrusion Detection Systems</title>
      <link>https://tfjmp.org/publication/2025-usenixsec-2/</link>
      <pubDate>Tue, 20 May 2025 00:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/publication/2025-usenixsec-2/</guid>
      <description>&lt;div align=&#34;center&#34;&gt;
&lt;iframe width=&#34;560&#34; height=&#34;315&#34; src=&#34;https://www.youtube.com/embed/Or_iAucWqT4?si=E1OlKsDU3fAZRM8p&#34; title=&#34;YouTube video player&#34; frameborder=&#34;0&#34; allow=&#34;accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share&#34; referrerpolicy=&#34;strict-origin-when-cross-origin&#34; allowfullscreen&gt;&lt;/iframe&gt;
&lt;/div&gt;
</description>
    </item>
    
    <item>
      <title>ORTHRUS: Achieving High Quality of Attribution in Provenance-based Intrusion Detection Systems</title>
      <link>https://tfjmp.org/publication/2025-usenixsec/</link>
      <pubDate>Sun, 12 Jan 2025 00:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/publication/2025-usenixsec/</guid>
      <description>&lt;div align=&#34;center&#34;&gt;
&lt;iframe width=&#34;560&#34; height=&#34;315&#34; src=&#34;https://www.youtube.com/embed/_FpCefZeObw?si=sXcdMnS2nWki-uJF&#34; title=&#34;YouTube video player&#34; frameborder=&#34;0&#34; allow=&#34;accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share&#34; referrerpolicy=&#34;strict-origin-when-cross-origin&#34; allowfullscreen&gt;&lt;/iframe&gt;
&lt;/div&gt;
</description>
    </item>
    
    <item>
      <title>On the Reproducibility of Provenance-based Intrusion Detection that uses Deep Learning</title>
      <link>https://tfjmp.org/publication/2025-rep/</link>
      <pubDate>Sat, 11 Jan 2025 00:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/publication/2025-rep/</guid>
      <description></description>
    </item>
    
    <item>
      <title>SafeBPF: Hardware-assisted Defense-in-depth for eBPF Kernel Extensions</title>
      <link>https://tfjmp.org/publication/2024-ccsw/</link>
      <pubDate>Fri, 18 Oct 2024 00:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/publication/2024-ccsw/</guid>
      <description>&lt;div align=&#34;center&#34;&gt;
&lt;iframe width=&#34;560&#34; height=&#34;315&#34; src=&#34;https://www.youtube.com/embed/PQNDsdP27Hw?si=opo-XDNivz1HDLXl&amp;amp;start=15045&#34; title=&#34;YouTube video player&#34; frameborder=&#34;0&#34; allow=&#34;accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share&#34; referrerpolicy=&#34;strict-origin-when-cross-origin&#34; allowfullscreen&gt;&lt;/iframe&gt;
&lt;/div&gt;
</description>
    </item>
    
    <item>
      <title>FetchBPF: Customizable Prefetching Policies in Linux with eBPF</title>
      <link>https://tfjmp.org/publication/2024-atc/</link>
      <pubDate>Wed, 10 Jul 2024 00:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/publication/2024-atc/</guid>
      <description>&lt;div align=&#34;center&#34;&gt;
&lt;iframe width=&#34;560&#34; height=&#34;315&#34; src=&#34;https://www.youtube.com/embed/0lo-7dDVFB0?si=qU5yN_IyrVtE_GTP&#34; title=&#34;YouTube video player&#34; frameborder=&#34;0&#34; allow=&#34;accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share&#34; referrerpolicy=&#34;strict-origin-when-cross-origin&#34; allowfullscreen&gt;&lt;/iframe&gt;
&lt;/div&gt;
</description>
    </item>
    
    <item>
      <title>Computational Experiment Comprehension using Provenance Summarization</title>
      <link>https://tfjmp.org/publication/2024-rep/</link>
      <pubDate>Tue, 18 Jun 2024 00:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/publication/2024-rep/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Kairos: Practical Intrusion Detection and Investigation using Whole-system Provenance</title>
      <link>https://tfjmp.org/publication/2024-sp/</link>
      <pubDate>Mon, 20 May 2024 00:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/publication/2024-sp/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Kairos: Practical Intrusion Detection and Investigation using Whole-system Provenance (Supplementary Material)</title>
      <link>https://tfjmp.org/publication/2024-sp-supp/</link>
      <pubDate>Sun, 19 May 2024 00:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/publication/2024-sp-supp/</guid>
      <description></description>
    </item>
    
    <item>
      <title>The Thesis Proposal</title>
      <link>https://tfjmp.org/post/phd-proposal/</link>
      <pubDate>Thu, 09 May 2024 00:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/post/phd-proposal/</guid>
      <description>&lt;p&gt;The submission of your thesis proposal should normally occur in the second year
of the PhD program and before the end of the third year.
You can find more information about the process on the &lt;a href=&#34;https://www.cs.ubc.ca/students/grad/policies/grad-handbook/phd-program/thesis-proposal&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;department website&lt;/a&gt;.
The process itself is clearly detailed, but the expected content of the thesis
proposal itself is underspecified.
This page describes my expectations for the students I supervise.&lt;/p&gt;
&lt;h1 id=&#34;formatting-and-length&#34;&gt;Formatting and Length&lt;/h1&gt;
&lt;p&gt;I strongly recommend to use the following &lt;a href=&#34;https://github.com/tfjmp/ubcdiss&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;latex template&lt;/a&gt;.
Remember, that as per department rules, your thesis proposal &lt;strong&gt;must not&lt;/strong&gt; exceed
50 pages (excluding appendices).
You should also update and remove part of the front matter from the template (e.g., list of figures, chapter list etc.).
The page limit is a maximum; it is not a target.
Successful Thesis Proposal documents can be shorter than the limit.
Writing within the page limit is important.
You should add all submissions and accepted publications since the start of your PhD
in the appendix.&lt;/p&gt;
&lt;h1 id=&#34;content&#34;&gt;Content&lt;/h1&gt;
&lt;h2 id=&#34;summary&#34;&gt;Summary&lt;/h2&gt;
&lt;p&gt;This should be 1 or 2 pages long and give a brief summary of the research you are
intending to pursue.
The early part of your summary, should contain your &lt;a href=&#34;https://cs.uwaterloo.ca/~brecht/thesis-stmt-new.html&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;thesis statement&lt;/a&gt;
(more examples &lt;a href=&#34;https://depts.washington.edu/acelab/theses.html&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;here&lt;/a&gt;).
The thesis statement is central to the proposal and you should build the rest of
the document around it.
Your goal is to demonstrate that your proposed thesis is non-trivial, novel,
plausible and, importantly, useful.&lt;/p&gt;
&lt;p&gt;You can later subdivide your thesis statement into multiple research questions, but you
must ensure that they are clearly interconnected, and that they will lead
to a coherent narrative throughout your thesis.
You should also discuss why answering those questions is important.&lt;/p&gt;
&lt;h2 id=&#34;literature-review&#34;&gt;Literature review&lt;/h2&gt;
&lt;p&gt;The goal in this section is to demonstrate your understanding of the literature,
and to show the limitations of previous work.
This should be the basis to your claim of novelty,
and it should be clear how the proposed work fits within the existing literature.
The literature review should provide a &lt;strong&gt;critical&lt;/strong&gt; assessment of past work, including:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;the identification of foundational work in the topic area;&lt;/li&gt;
&lt;li&gt;the most closely related prior work;&lt;/li&gt;
&lt;li&gt;a clear discussion of their strengths and limitations.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;You should consider that this part of the proposal will be used as a chapter in
your thesis.&lt;/p&gt;
&lt;h2 id=&#34;progress-report&#34;&gt;Progress Report&lt;/h2&gt;
&lt;p&gt;You should have done preliminary research by the time you are submitting your
proposal and, ideally, have published some work based on your &lt;a href=&#34;https://tfjmp.org/post/rpe/&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;RPE&lt;/a&gt;.
The goal is to show the committee what you are capable of.
This helps the committee assess the plausibility of the thesis and of your proposed plan.
Published papers should be available in the appendix, and you do not need to
reproduce their content.
You should summarize them briefly in a self-contained way.&lt;/p&gt;
&lt;p&gt;You should also consider listing talks you have given, internships or any other
relevant activities.&lt;/p&gt;
&lt;h2 id=&#34;research-proposal&#34;&gt;Research Proposal&lt;/h2&gt;
&lt;p&gt;You should build from your proposal summary and discuss how you are planning to
tackle your thesis and your research questions over the next few years.
It may be useful to think of this in term of planned publications.
You could subdivide the planned research into multiple chunks.
Each chunk could be summarized into 3 or 4 paragraphs and corresponds to an
academic paper.
Those papers will form the basis for your thesis chapters.
At this stage you should plan for at least 3 full academic papers.&lt;/p&gt;
&lt;h2 id=&#34;plan-and-timeline&#34;&gt;Plan and Timeline&lt;/h2&gt;
&lt;p&gt;While your proposal should give the impression that failure of your research is
unlikely, in reality this possibility exists.
Indeed, it would not be research if failure was not possible.
Consequently, your plan must account for possible setbacks and failures, and
must discuss what you plan to do if something does not work out.
Your plan must also contain milestones as well as there completion and success
criteria.
A milestone, can be, for example, the submission of a paper,
the release of a dataset, the completion of some software development task etc.
You may also discuss the evaluation strategies you will adopt to measure success
(e.g., your system successfully prevent vulnerability X while adding less than Y% overhead.)
This list of milestones should clearly and ultimately lead to the submission and defense of
your thesis.&lt;/p&gt;
&lt;p&gt;The milestones you present are your best guesses at the time of your proposal.
You will not be held to them, but you should periodically refer to your schedule,
update it as necessary, and become better at estimating how long it will take to complete your work.
They are mostly there to demonstrate that you understand the timescale involved
in overcoming different research challenges (e.g., paper submissions must be
scheduled at a reasonable and plausible pace).&lt;/p&gt;
&lt;p&gt;Finally, if you need specialized hardware or specific software resources to
complete your research, this must be discussed in advance and clearly stated
in your thesis.&lt;/p&gt;
&lt;h1 id=&#34;proposal-submission&#34;&gt;Proposal Submission&lt;/h1&gt;
&lt;p&gt;You should plan a couple of months to work on your proposal. You should be ready
to send and discuss regular updates with me during those months. Once we are in agreement that the
proposal is converging towards an acceptable output, you should contact the
&lt;a href=&#34;https://www.cs.ubc.ca/students/grad/policies/grad-handbook/phd-program/phd-supervisory-committee&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;members of the committee&lt;/a&gt; and schedule a date for your defense.
You should send your proposal at least two weeks in advance as to leave sufficient time for the
committee members to carefully review it (you should discuss this explicitly with the committee members).
It is also your responsibility to identify and make sure you fulfil all the department&amp;rsquo;s
administrative requirements.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Unleashing Unprivileged eBPF Potential with Dynamic Sandboxing</title>
      <link>https://tfjmp.org/publication/2023-sigcomm-ebpf/</link>
      <pubDate>Sun, 10 Sep 2023 00:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/publication/2023-sigcomm-ebpf/</guid>
      <description></description>
    </item>
    
    <item>
      <title>[538P] Topic in Computer Systems: Systems Security (2022-2023)</title>
      <link>https://tfjmp.org/post/2022-538p/</link>
      <pubDate>Thu, 02 Jun 2022 00:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/post/2022-538p/</guid>
      <description>&lt;h2 id=&#34;course-description&#34;&gt;Course Description&lt;/h2&gt;
&lt;p&gt;The goal of this course is to expose students to a variety of topics in Systems Security.
Security inherently touches on all areas of computer science.
Therefore, this course was designed as a &lt;em&gt;breadth&lt;/em&gt; course, addressed to all students in the department.
The core idea underlying the course is to bring together a diversity of viewpoints to generate interesting discussions.
On the other hand, we could also easily design a &lt;em&gt;depth&lt;/em&gt; course focused on any of the topics we will discuss.
The project component is the opportunity for students to explore one of those topics in more depth.
Students are free (and encouraged) to apply their expertise (ML, PL, HCI, architecture etc.) to solve a specific Security problem.
Some of the papers have been selected explicitly to highlight the interdisciplinary nature of Systems Security and to showcase
how diverse perspectives are welcomed and appreciated.&lt;/p&gt;
&lt;h2 id=&#34;course-requirements&#34;&gt;Course Requirements&lt;/h2&gt;
&lt;p&gt;There is no specific pre-requisite for this course outside of an undergraduate degree in Computer Science or closely related topics.&lt;/p&gt;
&lt;h2 id=&#34;course-objectives&#34;&gt;Course Objectives&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;reason about security problems;&lt;/li&gt;
&lt;li&gt;learn to read, critique, and write security papers;&lt;/li&gt;
&lt;li&gt;better understand the review process;&lt;/li&gt;
&lt;li&gt;implement and evaluate a security prototype.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;class-format&#34;&gt;Class format&lt;/h2&gt;
&lt;p&gt;This is a seminar-type class.
Every class we will discuss a different paper.
I have selected a mix of recent and older papers.
There will be two presenters during each class.
Each presenter will play a different role: the role of the Advocate and the role of the Critic.
The Advocate should play a role similar to that of the original authors and try to sell the work to the audience.
On the other hand, the Critic while remaining objective should towards the end of the presentation highlight the flaw of the paper and convince the audience that the paper is not good.
The Advocate presentation will last 20-25 minutes, you should motivate the work,
summarize the paper, and present the results.
The Critic presentation will last 10 minutes, you do not need to cover motivation
or summarization, instead you should focus on the shortcomings of the paper.
While shorter, the critical presentation is probably harder to prepare.&lt;/p&gt;
&lt;p&gt;In order to do well during your presentation, you should remember to stick to your role (Advocate or Critic).
Further, you do not need to spend too much time explaining the basics of the paper, everyone in the class will have already read it.
What add value to the presentation is your opinion and the insights you can extract from the paper! This is what you should focus on.&lt;/p&gt;
&lt;p&gt;You should expect to present at least 2 or 3 times during the term depending on the number of students registered.
After the presentation, we will take a 10 minutes break and discuss the paper.
You should come prepared for those discussions and be ready to engage.
Submissions are to be made on &lt;a href=&#34;https://canvas.ubc.ca/courses/106406&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;canvas&lt;/a&gt;, unless specified otherwise.&lt;/p&gt;
&lt;h2 id=&#34;paper-reports&#34;&gt;Paper reports&lt;/h2&gt;
&lt;p&gt;For each assigned paper you must write a report. You are to use the &lt;a href=&#34;https://www.usenix.org/conferences/author-resources/paper-templates&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;USENIX latex template&lt;/a&gt;
for formatting.
You must submit your reports on &lt;a href=&#34;https://canvas.ubc.ca/courses/106406&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;Canvas&lt;/a&gt;.
In your report, please, follow this structure:&lt;/p&gt;
&lt;div class=&#34;alert alert-note&#34;&gt;
  &lt;div&gt;
    &lt;h3 id=&#34;paper-summary-no-more-than-250-words&#34;&gt;Paper Summary (no more than 250 words)&lt;/h3&gt;
&lt;p&gt;Provide a brief summary of the paper (3-5 sentences is usually enough). The aim is to demonstrate
that you’ve read (and understood) the paper, so try to paraphrase and extract the essentials. At this
stage you should aim to be objective; later sections allow for your own opinion.&lt;/p&gt;
&lt;h3 id=&#34;answer-the-following-no-more-than-750-words-in-total&#34;&gt;Answer the following (no more than 750 words in total)&lt;/h3&gt;
&lt;h4 id=&#34;the-problem&#34;&gt;The Problem&lt;/h4&gt;
&lt;p&gt;What is the problem? Why is it important? Why is previous work insufficient (or Why has the
problem not been solved before, e.g. it’s a new problem the authors have identified). This is your take
on what the authors say in the paper (so again should be fairly objective). If the paper doesn’t seem
to tackle a particular problem, then focus on the primary motivation for the work. 1-2 sentences for
each of the three questions is probably sufficient.&lt;/p&gt;
&lt;h4 id=&#34;the-solution-or-approach&#34;&gt;The Solution (or Approach)&lt;/h4&gt;
&lt;p&gt;What is their approach/solution? How does it solve the problem? How is the solution unique and/or
innovative (if it is)? What are the details? Once more you should use the paper itself as the source to
help you answer these questions– but, as in previous parts, please do not just copy sections from the
paper. Instead, you should focus on paraphrasing/synopsizing, and extracting the essential details.
Depending on the paper, you’ll probably need 5-10 sentences here.&lt;/p&gt;
&lt;h4 id=&#34;evaluation&#34;&gt;Evaluation&lt;/h4&gt;
&lt;p&gt;How do they evaluate their solution? What questions do they set out to answer? What does the
evaluation say about the strengths and weaknesses of their system? What are the strengths and weaknesses of the evaluation itself do you think? A total of 3-4 sentences should suffice here – we’re
looking for highlights, not a point-by-point reproduction of the evaluation section(s).
In the rare case that there is no evaluation section, skip this part of the report.&lt;/p&gt;
&lt;h4 id=&#34;questions-for-the-authors&#34;&gt;Questions for the Authors&lt;/h4&gt;
&lt;p&gt;Imagine you’re attending a talk about this paper given by one of the authors. List at least 2 questions
that you would like to ask. These should ideally be specific to the paper/research.&lt;/p&gt;
  &lt;/div&gt;
&lt;/div&gt;
&lt;p&gt;You should submit 23 paper reports (subject to change). Each report done properly is equivalent to
1% of your final grade for a total of 20%. The 5 worst report score will be ignored (this gives
you 5 effective jokers).&lt;/p&gt;
&lt;h2 id=&#34;project&#34;&gt;Project&lt;/h2&gt;
&lt;p&gt;The project must address a non-trivial problem relevant to systems security. The project can resolve the problem by building a system, collecting data/carrying out experiments, developing algorithms and proving them correct, etc. I strongly prefer that you do your project in a team of 2-4 people.
You are encouraged to apply techniques from your main area of expertise to the topic of security (e.g., perform intrusion detection using ML techniques).&lt;/p&gt;
&lt;p&gt;You should plan to schedule some time to chat about your project idea with me.
Please, do not hesitate to send me an e-mail as soon as you want to discuss it.&lt;/p&gt;
&lt;p&gt;The required project deliverables are listed below.
Written submissions will be made through &lt;a href=&#34;https://ubc-syssec23.hotcrp.com/&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;hotcrp&lt;/a&gt; and must be formatted using the &lt;a href=&#34;https://www.usenix.org/conferences/author-resources/paper-templates&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;USENIX latex template&lt;/a&gt;.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Project Proposal Draft:&lt;/strong&gt; You are to submit the draft of your proposal on &lt;a href=&#34;https://ubc-syssec23.hotcrp.com/&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;hotcrp&lt;/a&gt;. It will not be directly graded but will receive reviews from your peers.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Proposal Presentation:&lt;/strong&gt; You will prepare a short presentation describing the project you intend to work on. Each presentation will be followed by a Q&amp;amp;A session. Presentation timing and details TBD.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Proposal Peer Review:&lt;/strong&gt; each student will review proposals from other groups and give feedback. You should take this task seriously. Please, check the CCS-inspired guidelines &lt;a href=&#34;https://tfjmp.org/files/guidelines.pdf&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;online&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Project Proposal:&lt;/strong&gt; you should incorporate feedback from the peer review process. I also strongly encourage you to schedule time to chat with me.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Project Report Draft:&lt;/strong&gt; You are to submit the draft of your report on &lt;a href=&#34;https://ubc-syssec23.hotcrp.com/&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;hotcrp&lt;/a&gt;. It will not be directly graded but will receive reviews from your peers.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Project Presentation:&lt;/strong&gt; You will prepare a presentation describing your project. I encourage you to demo your project during your talk. Each presentation will be followed by a Q&amp;amp;A session. Presentation timing and details TBD.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Report Peer Review:&lt;/strong&gt; as per the proposal stage, you will be asked to review the report from other teams. Please, check the CCS-inspired guidelines &lt;a href=&#34;https://tfjmp.org/files/guidelines.pdf&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;online&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Project Report:&lt;/strong&gt; you should incorporate feedback from the peer review process. I also strongly encourage you to schedule time to chat with me.&lt;/li&gt;
&lt;/ul&gt;
&lt;div class=&#34;alert alert-note&#34;&gt;
  &lt;div&gt;
    &lt;h3 id=&#34;proposal-instuction&#34;&gt;Proposal Instuction&lt;/h3&gt;
&lt;p&gt;Your proposal should be short (~4 pages). The main objective is to
assess the viability of the proposed project. You are expected to have
completed a limited amount of work at this stage.&lt;/p&gt;
&lt;p&gt;It must contain the following element:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Problem statement&lt;/strong&gt; (4 paragraphs): &lt;em&gt;Paragraph 1)&lt;/em&gt;  At a high level, what is the
problem area you are working on, and why is it important? It is important
to set the larger context here. Why is the problem of interest and
importance to the larger community? &lt;em&gt;Paragraph 2)&lt;/em&gt; What is the specific problem
considered in this paper? This paragraph narrows down the topic area of the
paper. In the first paragraph, you have established general context and
importance. Here you describe a specific context and background.
&lt;em&gt;Paragraph 3)&lt;/em&gt; What general approach are you planning to take?
Why do you expect significant results? You won&amp;rsquo;t have done the work at this
stage, but you should think about the results you expect to obtain.
&lt;em&gt;Paragraph 4)&lt;/em&gt; At a high level, what are the differences between what you are doing
and what others have done?&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Related Work&lt;/strong&gt; (1 page): There are two types of related work: background work
and contextual work. Background work includes contributions that are required to
understand your work. They must be described in sufficient detail so that any
of your classmates can understand what you are doing and why. Contextual work
is necessary to help the readers place your work and identify your
contributions. This includes past contributions you build upon in your own solution,
work that solves the same problem but in different ways, and contributions from
adjacent areas (solving a similar problem in a different domain). It is important
to remember that doing something differently is not a contribution. It must be
clear why you are taking an alternative approach (e.g., you exercise different trades-off,
improve performance, etc.). You may have yet to perform
an exhaustive literature review when submitting the proposal. Still, you need to have identified important work,
know where to look for more, and clearly understand how your proposal differs
from previous work. If you identify flaws in past work that you aim to address,
identify and state them clearly. If you have yet to read all the papers you intend
to read; you should list all those you have identified and plan to read. You
should also identify areas/domains where you plan to look for relevant
work. However, you should explicitly compare your proposed solution to some
previous work (a few sentences per publication are enough).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Experimental setup&lt;/strong&gt; (1 page): What experiments will you conduct? Why? What
question is each experiment designed to answer? What do you hope to learn from
each experiment? What measurement tools will you use? How will you determine if
your measurements are accurate? What tests will you conduct conditionally?
(For example, if we learn X from experiment 1, then we must
do A else do B.) What problems do you expect?
This part is essential to receive meaningful feedback and plan your
research. This is where most of the proposal effort should go.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Resources Needed&lt;/strong&gt; (&amp;lt;1 page): What equipment/software/tool will you need?
Do you have access to it? How could you get access? You do not want to find out,
midway through the project, you need access to resources that are not available.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Schedule&lt;/strong&gt; (&amp;lt;1 page): You should be as precise as you can, identify important
milestones, and make sure you allocate time to write the report and incorporate
peers feedback.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Distinction from Thesis&lt;/strong&gt; (1-2 paragraphs): You can and you are encouraged to work
on a topic related to your thesis. However, your project &lt;strong&gt;must&lt;/strong&gt; be
distinct from your main research. You must explicit this distinction (in some
cases, a single sentence is enough).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;report-instruction&#34;&gt;Report Instruction&lt;/h3&gt;
&lt;p&gt;You should write your final report as you would write a research paper. Your
report should be at most 13 pages, including figures and tables, but excluding
references. Be sure to highlight your work&amp;rsquo;s limitations honestly
and discuss when your results did not meet your expectations/hypothesis. Try to explain why this happens. I expect some of the reports you submit to
be suitable to be turned into conference submissions. I am more than happy to
work with you to make it happen.
&lt;strong&gt;You MUST include a link to the software artifact(s) backing your paper.&lt;/strong&gt;&lt;/p&gt;
  &lt;/div&gt;
&lt;/div&gt;
&lt;div class=&#34;alert alert-note&#34;&gt;
  &lt;div&gt;
    &lt;h2 id=&#34;project-presentations&#34;&gt;Project Presentations&lt;/h2&gt;
&lt;h3 id=&#34;proposal-presentation&#34;&gt;Proposal Presentation&lt;/h3&gt;
&lt;p&gt;The proposal presentation should last no more than 20 minutes. You should expect
questions at the end of the presentation and may allow questions during the
presentation. You should clearly explain what problem you are planning to explore
and why it is an important problem. You should walk your audience through your
research plan and how you are planning to evaluate the outcome of your project.
The presentation should be accessible to a knowledgeable but non-expert audience.
The presentation is graded as a group, how you want to present is the responsibility
of the group members.&lt;/p&gt;
&lt;p&gt;Audience should read through the proposal they have been assigned to review
beforehand and be ready to ask some questions. This should be non-adversarial and
with the intent of helping your classmates.&lt;/p&gt;
&lt;h3 id=&#34;final-presentation&#34;&gt;Final Presentation&lt;/h3&gt;
&lt;p&gt;The final presentation should not last more than 15 minutes. You should expect
5/10 minutes of questions at the end of the presentation. You presentation must
discuss the motivation behind your work, the design of your solution, the
evaluation you have performed, and discuss explicitly any limitations of your
work. The presentation should be accessible to a knowledgeable but non-expert audience.
The presentation is graded as a group, how you want to present is the responsibility
of the group members.&lt;/p&gt;
&lt;p&gt;Audience should read through the proposal they have been assigned to review
beforehand and be ready to ask some questions. This should be non-adversarial and
with the intent of helping your classmates.&lt;/p&gt;
  &lt;/div&gt;
&lt;/div&gt;
&lt;h3 id=&#34;deadlines&#34;&gt;Deadlines&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Project Proposal Draft:&lt;/strong&gt; Friday, February 10th&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Proposal Presentation:&lt;/strong&gt; Wednesday, February 15th&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Proposal Peer Review:&lt;/strong&gt; Friday, February 17th&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Project Proposal:&lt;/strong&gt; Monday, February 27th&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Project Report Draft:&lt;/strong&gt; Friday, April 7th&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Project Presentation:&lt;/strong&gt; Wednesday, April 12th&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Report Peer Review:&lt;/strong&gt; Friday, April 14th&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Project Report:&lt;/strong&gt; Friday, April 28th&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;grading&#34;&gt;Grading&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Paper reports 20%&lt;/li&gt;
&lt;li&gt;Presentation(s) 10%&lt;/li&gt;
&lt;li&gt;Project (group) 50%&lt;/li&gt;
&lt;li&gt;Peer Review 15%&lt;/li&gt;
&lt;li&gt;Participation (in-class discussion) 5%&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;schedule--reading-list-subject-to-change&#34;&gt;Schedule &amp;amp; Reading List (subject to change)&lt;/h2&gt;
&lt;p&gt;Classes take place in &lt;a href=&#34;https://learningspaces.ubc.ca/classrooms/dmp-101&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;DMP 101&lt;/a&gt;.&lt;/p&gt;
&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Day&lt;/th&gt;
&lt;th&gt;Paper&lt;/th&gt;
&lt;th&gt;Presenters&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Jan 9 Mon&lt;/td&gt;
&lt;td&gt;Introduction - Course Overview - Reading a Paper &lt;br/&gt; Reading (no report): &lt;a href=&#34;https://cseweb.ucsd.edu/~dstefan/cse227-spring19/papers/keshav:how.pdf&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;How to read a paper&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Jan 11 Wed&lt;/td&gt;
&lt;td&gt;&lt;a href=&#34;https://ieeexplore.ieee.org/document/8523802&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;A Study on the Security Implications of Information Leakages in Container Clouds&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Jan 16 Mon&lt;/td&gt;
&lt;td&gt;&lt;a href=&#34;https://gzs715.github.io/pubs/HOUDINI_CCS19.pdf&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;Houdini&amp;rsquo;s Escape: Breaking the Resource Rein of Linux Control Groups&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Jan 18 Wed&lt;/td&gt;
&lt;td&gt;&lt;a href=&#34;https://www.usenix.org/system/files/conference/osdi16/osdi16-arnautov.pdf&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;SCONE: Secure Linux Containers with Intel SGX&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Jan 23 Mon&lt;/td&gt;
&lt;td&gt;&lt;a href=&#34;https://web.dse.in.tum.de/wp-content/uploads/2021/11/rkt-io-eurosys21.pdf&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;rkt-io: a direct I/O stack for shielded execution&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Jan 25 Wed&lt;/td&gt;
&lt;td&gt;&lt;a href=&#34;https://www.usenix.org/system/files/conference/usenixsecurity18/sec18-sun.pdf&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;Security Namespace: Making Linux Security Frameworks Available to Containers&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Jan 30 Mon&lt;/td&gt;
&lt;td&gt;&lt;a href=&#34;https://www-users.cse.umn.edu/~kjlu/papers/kara.pdf&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;Demons in the Shared Kernel: Abstract Resource Attacks Against OS-level Virtualization&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Feb 1 Wed&lt;/td&gt;
&lt;td&gt;&lt;a href=&#34;https://ieeexplore.ieee.org/abstract/document/1199328&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;Anomaly detection using call stack information&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Feb 6 Mon&lt;/td&gt;
&lt;td&gt;&lt;a href=&#34;https://ieeexplore.ieee.org/abstract/document/924295&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;A fast automaton-based method for detecting anomalous program behaviors&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Feb 8 Wed&lt;/td&gt;
&lt;td&gt;&lt;a href=&#34;https://dl.acm.org/doi/pdf/10.1145/2939672.2939783&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;Fast Memory-efficient Anomaly Detection in Streaming Heterogeneous Graphs&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Feb 13 Mon&lt;/td&gt;
&lt;td&gt;&lt;a href=&#34;https://dl.acm.org/doi/pdf/10.1145/3460120.3484589&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;DeepAID: Interpreting and Improving Deep Learning-based Anomaly Detection in Security Applications&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Feb 15 Wed&lt;/td&gt;
&lt;td&gt;Proposal Presentation&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Feb 20 Mon&lt;/td&gt;
&lt;td&gt;Midterm Break&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Feb 22 Wed&lt;/td&gt;
&lt;td&gt;Midterm Break&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Feb 27 Mon&lt;/td&gt;
&lt;td&gt;&lt;a href=&#34;https://users.cs.northwestern.edu/~robby/courses/395-495-2017-winter/ndss2008.pdf&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;Automated whitebox fuzz testing&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Mar 1 Wed&lt;/td&gt;
&lt;td&gt;&lt;a href=&#34;https://www.usenix.org/system/files/woot20-paper-fioraldi.pdf&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;AFL++: Combining Incremental Steps of Fuzzing Research&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Mar 6 Mon&lt;/td&gt;
&lt;td&gt;&lt;a href=&#34;https://www.usenix.org/system/files/conference/usenixsecurity17/sec17-schumilo.pdf&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;kAFL: Hardware-assisted feedback fuzzing for OS kernels&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Mar 8 Wed&lt;/td&gt;
&lt;td&gt;&lt;a href=&#34;http://web.cse.ohio-state.edu/~zhao.2708/assets/ndss18/NDSS18.pdf&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;IoTFuzzer: Discovering Memory Corruptions in IoT Through App-based Fuzzing&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Mar 13 Mon&lt;/td&gt;
&lt;td&gt;&lt;a href=&#34;https://www.usenix.org/system/files/conference/usenixsecurity18/sec18-he.pdf&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;Rethinking Access Control and Authentication for the Home Internet of Things (IoT)&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Mar 15 Wed&lt;/td&gt;
&lt;td&gt;&lt;a href=&#34;https://spiral.imperial.ac.uk/bitstream/10044/1/77847/5/ren-imc19.pdf&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;Information Exposure From Consumer IoT Devices: A Multidimensional, Network-Informed Measurement Approach&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Mar 20 Mon&lt;/td&gt;
&lt;td&gt;&lt;a href=&#34;https://cs.uwaterloo.ca/~brecht/courses/854-Scalable-Systems-Software-2011/Possible-Readings/virtualization/secure-virtual-arch-sosp-2007-criswell.pdf&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;Secure Virtual Architecture: A Safe Execution Environment for Commodity Operating Systems&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Mar 22 Wed&lt;/td&gt;
&lt;td&gt;&lt;a href=&#34;https://pdos.csail.mit.edu/papers/lxfi:sosp11.pdf&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;Software fault isolation with API integrity and multi-principal modules&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Mar 27 Mon&lt;/td&gt;
&lt;td&gt;&lt;a href=&#34;https://www.usenix.net/system/files/atc19-narayanan.pdf&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;LXDs: Towards isolation of kernel subsystems&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Mar 29 Wed&lt;/td&gt;
&lt;td&gt;&lt;a href=&#34;http://nebelwelt.net/publications/files/22NDSS2.pdf&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;Preventing Kernel Hacks with HAKC&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Apr 3 Mon&lt;/td&gt;
&lt;td&gt;&lt;a href=&#34;https://www.usenix.org/system/files/osdi20-narayanan_vikram.pdf&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;RedLeaf: Isolation and Communication in a Safe Operating System&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Apr 5 Wed&lt;/td&gt;
&lt;td&gt;&lt;a href=&#34;https://dl.acm.org/doi/abs/10.1145/319151.319163&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;EROS: a fast capability system&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Apr 10 Mon&lt;/td&gt;
&lt;td&gt;&lt;a href=&#34;https://www.cl.cam.ac.uk/~dc552/papers/201505-oakland2015-cheri-compartmentalization.pdf&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;Cheri: A hybrid capability-system architecture for scalable software compartmentalization&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;Optional reading: &lt;a href=&#34;https://www.cl.cam.ac.uk/techreports/UCAM-CL-TR-941.pdf&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;Introduction to CHERI&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Apr 12 Wed&lt;/td&gt;
&lt;td&gt;Project Presentation&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h2 id=&#34;late-policy&#34;&gt;Late Policy&lt;/h2&gt;
&lt;p&gt;You will receive a 0 for late work unless you have an approved extension.&lt;/p&gt;
&lt;p&gt;For individual assignments, the deadline for one assignment can be extended by 24 hours with no penalty to the mark. Extension requests must be made explicitly through e-mail. Extension requests must be made no later than 24 hours past the deadline.&lt;/p&gt;
&lt;p&gt;For group tasks, you can request an extension of 24 hours as long as someone in your group has an unused extension. You cannot receive an extension of more than 24 hours for a group deliverable.&lt;/p&gt;
&lt;h2 id=&#34;academic-honesty-and-collaboration-guidelines&#34;&gt;Academic honesty and collaboration guidelines&lt;/h2&gt;
&lt;p&gt;The department has a detailed policy regarding &lt;a href=&#34;https://my.cs.ubc.ca/docs/collaboration-plagiarism&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;collaboration and plagiarism&lt;/a&gt;. You must familiarize yourself with this policy.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Paper reports:&lt;/strong&gt; You should write your reports individually. You are free to discuss with others,
but you must write the reports on your own. You should clearly reference any resources you have used.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Projects:&lt;/strong&gt; you are free to use any code you find in your project. However, a non-trivial fraction of functionality in your prototype must be constructed by your team. You must cite and attribute sources of the code that you borrow/utilize in your project. When writing the project reports, you should follow the same citation standard as expected from conference papers.&lt;/p&gt;
&lt;h2 id=&#34;extra-reading-material&#34;&gt;Extra Reading Material&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://cseweb.ucsd.edu/~dstefan/cse227-spring19/papers/keshav:how.pdf&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;How to read a paper&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://www.microsoft.com/en-us/research/academic-program/write-great-research-paper/&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;How to write a great research paper&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://www.microsoft.com/en-us/research/publication/how-to-give-a-good-research-talk/&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;How to give a good research talk&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://www.sigarch.org/reviewing-system-security-papers/&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;Reviewing System Security Papers&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://www.cl.cam.ac.uk/teaching/1011/R01/review-writing.pdf&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;Writing reviews for systems conferences&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://andreas-zeller.info/2021/07/27/Reviewing-across-fields-ICSE-PLDI-CCS.html&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;How do different fields review papers? Experiences from ICSE, PLDI, and CCS&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</description>
    </item>
    
    <item>
      <title>The Research Proficiency Evaluation process</title>
      <link>https://tfjmp.org/post/rpe/</link>
      <pubDate>Sun, 15 May 2022 00:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/post/rpe/</guid>
      <description>&lt;p&gt;The official guidelines are provided on the &lt;a href=&#34;https://www.cs.ubc.ca/students/grad/policies/grad-handbook/research-proficiency-evaluation-rpe/rpe-process&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;department website&lt;/a&gt;.
On this page, I give my take on the process and provide some pointers.&lt;/p&gt;
&lt;h2 id=&#34;the-goal-of-the-rpe&#34;&gt;The goal of the RPE&lt;/h2&gt;
&lt;p&gt;The purpose of the RPE is to 1) make sure you are ready for research; and
2) that the supervisory relationship is working. It is best to identify problems
early, and the goal is not to fail you but to ensure you are ready to succeed.
In my opinion, the RPE should be a well-defined, reasonably scoped, and
self-contained project. The RPE is not your Ph.D., you should think of it as
starting to work on your first paper (at UBC) and it should be scoped
consequently. You may have a grand ambition for your Ph.D.,
but you need to wrap the RPE project in only a few months.
Consequently, you need to identify a set of clear and meaningful objectives where
you can make significant progress within the available time frame.
There is an expectation that your RPE will lead to a publication, but this is
not expected to happen before your defense. However, you need to show you are
working in that direction (e.g., by showing preliminary results and a prototype).
Finally, The self-contained aspect is important if you are working as part
of a larger project, the RPE must be based on your work and your contribution
must be clearly identifiable.
My role is to work with you, support you, and make sure things go smoothly.&lt;/p&gt;
&lt;h2 id=&#34;deliverable&#34;&gt;Deliverable&lt;/h2&gt;
&lt;p&gt;For written reports, I suggest using the &lt;a href=&#34;https://www.usenix.org/conferences/author-resources/paper-templates&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;USENIX template&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;RPE proposal&lt;/strong&gt;: expected length is around two pages. This should focus on the problem
definition. However, from experience, most students submit slightly longer proposals (5-6 pages)
including an expanded related work section and a description of their proposed solution.
This is not necessary, but you should feel free to include this if you want feedback on those aspects.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;RPE report&lt;/strong&gt;: expected length is around twelve pages. Your report should be
written and organized like a conference paper. You may consider including a long
discussion section containing: 1) limitations of your current prototype/proof of concept; 2) work
you are planning to do over the next few months to turn your RPE work into a publication.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;RPE presentation&lt;/strong&gt;: expected length is around twenty minutes. You should present
your work as you would at a conference. You should cover the following topics: 1) context and problem;
2) solution; 3) evaluation; and 4) future work. You should
rehearse your presentation (you can ask me and your peers).&lt;/p&gt;
&lt;p&gt;You should not hesitate to discuss with other students in the lab, and ask for examples
of their submissions. Further, I am expecting to see several drafts of your
written work/presentation. I will normally ask for it, but you should feel free
to send it to me as soon as you want feedback. Unlike work you do for a joint paper submission, I will avoid rewriting your text. However, I am more than happy to (and will) comment.
I also encourage you to share drafts with some of your peers working on
different projects (forming a writing group with other students taking their RPE at the same time can be a very positive experience). Sharing your work with peers help you gauge how accessible your writings are.&lt;/p&gt;
&lt;h2 id=&#34;deadlines&#34;&gt;Deadlines&lt;/h2&gt;
&lt;p&gt;Assume a student starting in September (if you start in January, tweak the timeline accordingly).
Here is my vision of how you should approach the RPE process.
Remember, as your advisor/supervisor it is my job to get you through this process
successfully. This means you should talk to me and seek help and support.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;September&lt;/strong&gt;, you hopefully have an idea of why you came to UBC and what you want to work on.
You should spend your first few months getting familiar with the relevant literature,
writing an annotated bibliography/notes about your reading, and start designing and implementing prototypes to test your ideas.
In addition, you may also decide to join an existing project, get up to speed with the project, and participate actively.
During our 1-1 meeting I would expect to discuss your growing understanding of
the field, and your ideas. Part of my job is to challenge your ideas
and force you to think critically about the problems you propose to investigate and potential solutions.
Defining research problems is one of the most important skills to acquire early on.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;December&lt;/strong&gt;, you should start crystalizing the research problem you want to
tackle during your RPE. Identify, the relevant literature and what is the state
of the art in that space.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;January&lt;/strong&gt;, this is the time to start working on the proposal. In addition to formalizing and writing down your proposal, you should consider doing some preliminary technical experimentation. My advice is to take only a single course during this term. You want to ensure you have enough
time dedicated to research.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;March&lt;/strong&gt;, we select together your RPE committee. This is relatively simple,
we need to identify two faculties such that their interests overlap with your RPE project
and who have time to seat on your committee.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;April&lt;/strong&gt;, you submit your proposal and get feedback from the committee. You should
expect again your ideas to be challenged in a supportive way. The goal is to help
you formulate a clear problem. You should digest the feedback and make corrections
accordingly.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;May&lt;/strong&gt;, you can now start working on your project in earnest. At this point,
you should be done with courses and you should be able to focus on your research
full-time. You are strongly encouraged to do so. I am expecting to get messages
from students several times a week at this point. Don&amp;rsquo;t be shy, if you need to
discuss your struggles and/or design decisions do so! You may also want to chat
with other students in the lab, especially those working on related topics.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;August&lt;/strong&gt;, you have hopefully been taking notes on your implementation, design,
and the literature you have read. It is time to write your RPE report. Remember,
the goal is to show you are able to perform research at a level expected from a
Ph.D. student. You may not have finished everything you wanted to do, but you need
to show at least an early prototype and some early evaluation results. You should also
demonstrate that you understand how to move from what you have to a publication
(i.e., clearly articulate the work you are planning to do over the next few months).&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;September&lt;/strong&gt;, it is time to submit the report and organize the defense. Do not
be overly concerned with the defense. You will be told before the presentation is scheduled if there are
any concerns about the quality of the report.&lt;/p&gt;
&lt;h2 id=&#34;failing-the-rpe&#34;&gt;Failing the RPE&lt;/h2&gt;
&lt;p&gt;In my opinion, a student failing during the public defense should be avoided and
in most circumstances would be the supervisor&amp;rsquo;s responsibility.
There are multiple deadlines within the RPE that are opportunities to give
feedback and to have a difficult conversation if things are not going as they
should.
Your proposal and report are read by your supervisor and the committee members, you
should be told if there are concerns about their standard.
If that is the case, you should work with your supervisor on a positive outcome.
This outcome will depend on why things are not working well and can include
solutions such as an extension, looking for a new supervisor, or continuing in
the MSc program if you are a Ph.D. track student.
I also strongly encourage you to talk with other faculties or your peers in such
circumstances and to seek support to decide on your next steps.
In short, the process is designed to avoid failure.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Calendar</title>
      <link>https://tfjmp.org/post/calendar/</link>
      <pubDate>Mon, 04 Apr 2022 00:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/post/calendar/</guid>
      <description>&lt;iframe src=&#34;https://calendar.google.com/calendar/embed?height=600&amp;wkst=2&amp;bgcolor=%23EF6C00&amp;ctz=America%2FVancouver&amp;mode=WEEK&amp;showCalendars=0&amp;showDate=1&amp;showTitle=0&amp;showPrint=1&amp;showTabs=0&amp;src=dGhvbWFzLmZyYW5jaXMucGFzcXVpZXJAZ21haWwuY29t&amp;color=%23F09300&#34; style=&#34;border:solid 1px #777&#34; width=&#34;800&#34; height=&#34;600&#34; frameborder=&#34;0&#34; scrolling=&#34;no&#34;&gt;&lt;/iframe&gt;
</description>
    </item>
    
    <item>
      <title>Supervisory expectations</title>
      <link>https://tfjmp.org/post/working-with-me/</link>
      <pubDate>Mon, 04 Apr 2022 00:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/post/working-with-me/</guid>
      <description>&lt;style&gt;body {text-align: justify}&lt;/style&gt;
&lt;p&gt;The goal of this document is to set mutual expectations on our collaboration.
We collaboratively update this document once a year.&lt;/p&gt;
&lt;h2 id=&#34;advisory-goals&#34;&gt;Advisory goals&lt;/h2&gt;
&lt;p&gt;My goal in advising graduate students is to help train them to become independent researchers.
This encompasses both the general scientific and research process, from identifying a compelling research question to communicating results through papers and presentations, as well as discipline-specific skills.&lt;/p&gt;
&lt;p&gt;While these skills are particularly useful in academia, they are also useful in other contexts as well.
Some students will pursue careers as research-track academics, while others may become teaching-oriented professors, industry researchers, or entrepeneurs.
I am happy to work with students with any of these goals; students should discuss these types of goals with me on occasion, particularly as their thinking changes about future plans or leading up to relevant milestones in their degree.&lt;/p&gt;
&lt;h2 id=&#34;working-environment-and-relationship&#34;&gt;Working environment and relationship&lt;/h2&gt;
&lt;h3 id=&#34;meetings-and-other-regular-communication&#34;&gt;Meetings and other regular communication&lt;/h3&gt;
&lt;p&gt;I structure my regular meetings with students on a per-project basis, which may mean that a given group of students typically meet me together.
We typically meet weekly, during which each student shares updates on their recent progress.
We have also have lab-wide meeting once a week.
I expect to meet, even if you don&amp;rsquo;t expect to have substantial topics to talk about.&lt;/p&gt;
&lt;p&gt;Before the meeting send me anything you&amp;rsquo;d like to discuss (e.g. a paper draft) the day before the meeting.
Take notes during the meeting, and keep them in a location we can both have access to.
Not having substantial updates for a regular meeting should be rare.
Doing it more than once in a while is an indication that you&amp;rsquo;re regularly having unproductive stretches, and we should discuss why this is and what to do about it.&lt;/p&gt;
&lt;p&gt;Outside of these regularly arranged times, I am often available for impromptu discussion as it would be helpful. Feel free to ask for my time whenever it would be helpful, and allow me to say no if I can&amp;rsquo;t.
To arrange additional discussions, get in touch with me via Slack to schedule a time to meet.&lt;/p&gt;
&lt;p&gt;Communication from me to you outside of meetings:
I may message you via Slack at any time, but I do not expect you to reply outside of your typical working hours except if otherwise agreed to for a particular reason, e.g., an imminent conference deadline.
I do expect a response within 1 day (not including weekends), even if it is only to acknowledge the note and say that a more complete response is forthcoming.
And likewise, from you to me:
Feel free to message me at any time; I likewise may not respond until my typical working hours.
I prefer that you contact me via Slack except in exceptional situations.&lt;/p&gt;
&lt;h3 id=&#34;lab-meetings-and-events&#34;&gt;Lab meetings and events&lt;/h3&gt;
&lt;p&gt;In addition to regular meetings with me, you are also expected to generally attend and contribute to Systopia&amp;rsquo;s reading group.
This is valuable both to you and to others.
While you will have much of your own work to do, being a member of the lab is about more than just writing your own papers.
Attending talks by your labmates, giving feedback, discussing other research areas, ideas, and process, and even just talking about academia over a coffee all contributes indirectly to your training, and the training of others in the lab. I expect you to participate in such events regularly.&lt;/p&gt;
&lt;h3 id=&#34;working-hours&#34;&gt;Working hours&lt;/h3&gt;
&lt;p&gt;During periods for which you are doing research with me, you should treat your degree as a full-time job.
Some time will be spent on taking courses, or serving as a TA as part of your funding; the remainder of your time should be spent on research.
It doesn&amp;rsquo;t matter to me when you work, outside of our mutually arranged meetings and other responsibilities, as long as you are making good progress.
To maximize overlap with your labmates, I&amp;rsquo;d like you to be generally available Monday-Friday (except on holidays) in the core hours between &lt;strong&gt;10am-3pm&lt;/strong&gt;, but whether you typically start earlier, or work later I leave up to your personal preference.&lt;/p&gt;
&lt;p&gt;Physical space:
It is valuable for you to interact with others in the group and the department; these are benefits not just to you but also to your labmates.
I therefore expect you to typically work from the lab space at least two days a week.
I encourage that you try to be in the lab at least between 10am - 3pm, when most of the lab members will be around.
The rest of time, I don&amp;rsquo;t mind if you prefer to work from home or elsewhere, but try to respond promptly by Slack during your typical working hours.
If you will be working from home or otherwise away from the lab for more than a week then you should let me know.&lt;/p&gt;
&lt;p&gt;If you need to work remotely for personal or medical reason, please discuss with me.
You should not do so during your first year.&lt;/p&gt;
&lt;h3 id=&#34;vacation&#34;&gt;Vacation&lt;/h3&gt;
&lt;p&gt;It&amp;rsquo;s important to take a break from time to time. The &lt;a href=&#34;https://vancouver.calendar.ubc.ca/faculties-colleges-and-schools/faculty-graduate-and-postdoctoral-studies/academic-regulations/graduate-student-vacation-policy&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;UBC policy&lt;/a&gt; is that graduate students have three weeks of vacation time (15 days), in addition to the week the university is closed between Christmas and New Year&amp;rsquo;s Day.
Let me know when you plan to take vacation in advance and coordinate with me in advance about any planned vacations.
There may be some constraints on when you can reasonably take vacation time:
If you are an author on a paper, you should expect to be available to work on that paper for the four weeks leading up to the submission deadline.
If you have a TA position, you need to discuss with the course staff about when vacation will be reasonable for that position as well as with me.&lt;/p&gt;
&lt;h2 id=&#34;research&#34;&gt;Research&lt;/h2&gt;
&lt;h3 id=&#34;choosing-a-research-topic&#34;&gt;Choosing a research topic&lt;/h3&gt;
&lt;p&gt;In deciding what projects you work on,
I will assign you a research topic to work on, at least at first.
Then we will typically come to a research topic of mutual interest through a process of joint brainstorming.&lt;/p&gt;
&lt;h3 id=&#34;publication-norms&#34;&gt;Publication norms&lt;/h3&gt;
&lt;p&gt;While there can be exceptions for many reasons, I typically expect that most MSc students will have &lt;strong&gt;one&lt;/strong&gt; first-author paper submitted/accepted by the end of their degree.
PhD students will have at least &lt;strong&gt;three&lt;/strong&gt; first-author papers by the end of their degree.
These numbers may vary dramatically depending on how much work various projects end up being, and how lucky you are, among many other factors.
Some typical venues to target for publication are USENIX Security, IEEE S&amp;amp;P, ACM CCS, NDSS, ASPLOS, EuroSys, OSDI, etc.&lt;/p&gt;
&lt;h3 id=&#34;collaboration-and-side-projects&#34;&gt;Collaboration and side projects&lt;/h3&gt;
&lt;p&gt;I am supportive of you joining projects outside the lab as a supporting contributor.
Confirm with me before joining a research project outside the lab.
Confirm with me before inviting anyone to join an ongoing research project to help out.&lt;/p&gt;
&lt;h3 id=&#34;paper-submissions&#34;&gt;Paper submissions&lt;/h3&gt;
&lt;p&gt;I typically plan paper deadlines well in advance (e.g., half a year or more). This gives us ample time to prepare and improve the paper draft.
We should aim for a draft version of the paper two weeks in advance of any deadline, but we can be flexible in exactly what happens.
Make sure to be aware of upcoming paper deadlines (e.g., add them to your calendar, create timelines, etc.).&lt;/p&gt;
&lt;p&gt;I expect to know about all paper submissions you make during your program, even if we have agreed that I am not a co-author.
If you are unsure about co-authorship, order of authors, etc., please discuss with me as soon as possible.
Never add anyone as a co-author on a paper without their knowledge; for co-authors outside of our immediate group, bear in mind that they might have their own expectations and requirements about timelines for giving feedback.&lt;/p&gt;
&lt;h3 id=&#34;conference-attendance&#34;&gt;Conference attendance&lt;/h3&gt;
&lt;p&gt;In general, the first authors of conference publications will be sent to present the work.
If additional funding is available, then other authors may be sent, too. However, please make sure that you check about funding for a particular venue before submitting, since, for example, attending a workshop without a good reason for attending the associated conference may be too expensive a trip.
My general philosophy on conference support is that, funds permitting, I aim to provide close to full travel support.&lt;/p&gt;
&lt;p&gt;Preparing for a conference:
schedule a practice talk for any conference presentation at least 3 weeks in advance of the actual presentation during a group meeting.
You should also schedule a presentation during Systopia&amp;rsquo;s reading group.
We should discuss a poster draft at least two weeks in advance of the conference date.&lt;/p&gt;
&lt;h2 id=&#34;degree-progress&#34;&gt;Degree progress&lt;/h2&gt;
&lt;p&gt;While you should raise concerns or similar with me at any point, there are various points throughout your degree at which we should explicitly ensure that everything is &amp;ldquo;on track.&amp;rdquo;&lt;/p&gt;
&lt;h3 id=&#34;early-msc-students&#34;&gt;Early MSc students&lt;/h3&gt;
&lt;p&gt;MSc students in their first two terms, by departmental default, have an &amp;ldquo;advisor&amp;rdquo; rather than a &amp;ldquo;supervisor,&amp;rdquo; and are not expected to do research.
Students who expect to work with me should strongly consider a &lt;a href=&#34;https://www.cs.ubc.ca/students/undergrad/courses/specialty#cpsc-448-directed-studies-in-computer-science&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;directed studies course&lt;/a&gt; to trial research with me.&lt;/p&gt;
&lt;h3 id=&#34;annual-progress-check-ins&#34;&gt;Annual progress check-ins&lt;/h3&gt;
&lt;p&gt;The department requires &lt;a href=&#34;https://my.cs.ubc.ca/docs/annual-progress-report&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;an annual progress report form&lt;/a&gt; from PhD students each summer.
In advance of filing that form, we will also have an annual explicit &amp;ldquo;check-in&amp;rdquo; meeting about how we each think things are going and what we could do better/differently.
In advance of filling out this form, PhD students who have a supervisory committee (typically after their proposal) should meet with that committee at least once a year, per UBC/department guidelines.
You should check in with each member of your committee at least once a year, but this can be done separately.
For MSc students, while the department doesn&amp;rsquo;t require it, I also do an annual &amp;ldquo;check-in&amp;rdquo; meeting with MSc students.&lt;/p&gt;
&lt;h3 id=&#34;program-milestones&#34;&gt;Program milestones&lt;/h3&gt;
&lt;p&gt;We should make sure that any program milestones you haven&amp;rsquo;t yet completed are on your mind.&lt;/p&gt;
&lt;p&gt;For the &lt;a href=&#34;https://www.cs.ubc.ca/students/grad/graduate-programs/research-proficiency-evaluation-rpe&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;RPE&lt;/a&gt;:
I typically expect PhD students to complete the RPE at the conclusion of their first independent research project, which may come at a different time than the department guidelines suggest.&lt;/p&gt;
&lt;p&gt;For the &lt;a href=&#34;https://www.cs.ubc.ca/students/grad/policies/grad-handbook/phd-program/thesis-proposal&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;thesis proposal&lt;/a&gt;:
I typically expect my PhD students to complete a thesis proposal once they have completed a few research projects and have a reasonable idea towards how the rest of their PhD will go.&lt;/p&gt;
&lt;h2 id=&#34;stipends-and-funding&#34;&gt;Stipends and funding&lt;/h2&gt;
&lt;p&gt;Funding in the department is provided by a mixture of research assistantships, teaching assistantships, and occasionally administrative positions, as well as awards, fellowships, and so on.&lt;/p&gt;
&lt;p&gt;It is worth mentioning that RA stipends are not taxed and also, per &lt;a href=&#34;https://lrb.my.salesforce.com/sfc/p/#f40000022yYB/a/Mm000003qn4X/K52YyjzQ.vYWjxyRP_dm6ZX07Za4QJzjDIwfHRgBOfc&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;a BC Labour Relations Board ruling in March 2025&lt;/a&gt;, can only be used to fund work towards your own research and closely related incidental work.
TAships and administrative positions&amp;rsquo; salaries are taxed; TAs are members of the &lt;a href=&#34;https://www.cupe2278.ca/&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;CUPE 2278&lt;/a&gt; union.&lt;/p&gt;
&lt;h3 id=&#34;lab-funding-overview&#34;&gt;Lab funding overview&lt;/h3&gt;
&lt;p&gt;The lab receives most of its funding from &lt;strong&gt;NSERC&lt;/strong&gt; and industry.
Most funding tends to come with only minor restrictions on what you work on.
However, some sources of funding tend to come with specific requirements and deliverables for the lab&amp;rsquo;s research, which may affect which projects you can work on or how you work on them.&lt;/p&gt;
&lt;h3 id=&#34;expected-funding-levels&#34;&gt;Expected funding levels&lt;/h3&gt;
&lt;p&gt;The department requires students in their guaranteed funding periods to receieve at least &lt;a href=&#34;https://my.cs.ubc.ca/docs/cs-support-policy-breakdown&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;a certain minimum funding level&lt;/a&gt;, which increases annually with inflation.
Note that you will be required to pay certain fees and potentially tuition, which vary depending on your position (type of degree, year in program, international/domestic); a breakdown from the department for current rates is available &lt;a href=&#34;https://docs.google.com/spreadsheets/d/1v7IdXInOMBx1QvwpstJD2KTXWBQIxsbMXvdB_FyS2e8/edit?gid=275015393#gid=275015393&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;here&lt;/a&gt;.
My students typically receive these minimum funding levels.
After the point where tuition is no longer covered by the university (fifth or later year of PhD, second year or later of MSc), I typically provide additional RAship to cover this difference.&lt;/p&gt;
&lt;h3 id=&#34;length-of-funding&#34;&gt;Length of funding&lt;/h3&gt;
&lt;p&gt;The departmental minimums apply to MSc (Thesis) students for 2 years, MSc (Essay) students for 20 months, and PhDs for 5 years.
I typically fund students beyond the department guaranteed period, as long as (1) there is continued strong progress on the student’s part, and (2) sufficient research funding (grant money) on my part.&lt;/p&gt;
&lt;h3 id=&#34;ta-positions&#34;&gt;TA positions&lt;/h3&gt;
&lt;p&gt;TA positions can be used either as a part of the minimum funding level, or &amp;ldquo;on top&amp;rdquo; of the usual funding for extra money.
I typically ask MSc students who anticipate working with me, as part of their funding, to TA in their first two terms, and once in their second year.
For PhD students&amp;rsquo; usual stipends, I usually request my students to TA once per year.&lt;/p&gt;
&lt;p&gt;In terms where students are not TAing for funding purposes:
I prefer my students have as much time to work on research as possible, and so I prefer not to use more TA positions than necessary.
However, do let me know if you are concerned about funding and we can discuss options.&lt;/p&gt;
&lt;p&gt;Note that, per TA union rules, it is generally not possible to TA more than a standard 12 hour contract.&lt;/p&gt;
&lt;h3 id=&#34;awards&#34;&gt;Awards&lt;/h3&gt;
&lt;p&gt;I encourage you to apply for awards for which you are eligible; receiving this are good for both you and me.
To make it explicit, here&amp;rsquo;s what happens if you get one of these awards:&lt;/p&gt;
&lt;h4 id=&#34;tri-agency-fellowships-cgrs-d-cgrs-m&#34;&gt;Tri-Agency Fellowships (CGRS D, CGRS M)&lt;/h4&gt;
&lt;p&gt;Departmental policy is that you receieve at least $5,000 over the departmental annual minimum funding, and also at least the full award amount. If necessary, the department covers the gap between the award amount and $5,000 over the departmental annual minimum; you will also not be required to TA as part of your funding while receiving this award.&lt;/p&gt;
&lt;h4 id=&#34;other-fellowshipsscholarships-at-least-15000-eg-ubc-4yf&#34;&gt;Other fellowships/scholarships at least $15,000 (e.g. UBC 4YF)&lt;/h4&gt;
&lt;p&gt;Departmental policy is that you receieve at least $2,000 over the departmental annual minimum funding, and also at least the full award amount.
You will also not be required to TA as part of your funding while receiving this award.
For an award that includes specific funding for travel, equipment, etc., this is not included in &amp;ldquo;the full award amount&amp;rdquo; above.&lt;/p&gt;
&lt;h4 id=&#34;smaller-one-off-under-10000-or-admissions-awards&#34;&gt;Smaller one-off (under $10,000) or admissions awards&lt;/h4&gt;
&lt;p&gt;Departmental expectation is that you receieve this amount in full, in addition to the usual stipend, without affecting any expectation to TA or similar.
You may optionally use such an award to &amp;ldquo;buy out&amp;rdquo; of a time you would otherwise be expected  to TA, reducing the additional amount you receive by &lt;strong&gt;the TA salary&lt;/strong&gt;.&lt;/p&gt;
&lt;h3 id=&#34;internships-course-instruction-etc&#34;&gt;Internships, course instruction, etc&lt;/h3&gt;
&lt;p&gt;I encourage students to seek out internships which will be relevant to their career progress. Discuss potential plans about this with me in advance.
Students should consider the &lt;a href=&#34;https://www.cs.ubc.ca/students/undergrad/careers/computer-science-co-op-program&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;co-op program&lt;/a&gt; for any possible internships.
Students who are interested can apply to be sessional lecturers for a course.
Discuss this possibility with me.&lt;/p&gt;
&lt;p&gt;When a student is on an internship or a sessional lecturer,
that pay (assuming it is at least the amount of the relevant minimum) constitutes your funding for that term.
This has no bearing on other terms, and so will likely result in an increase in your annual take-home income.
I count these positions towards times when you would otherwise TA for funding.&lt;/p&gt;
&lt;p&gt;For part-time internships and consulting:
A 50%-time internship means I will still fund you at 50% of the rate I would have otherwise (first going towards &amp;ldquo;buying out&amp;rdquo; any expected TAship).
Working part-time or consulting during your degree is normally not effective; we should talk about this explicitly before embarking on this kind of path.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>A large-scale study on research code quality and execution</title>
      <link>https://tfjmp.org/publication/2022-scidata/</link>
      <pubDate>Mon, 21 Feb 2022 00:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/publication/2022-scidata/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Graduate Admission Interview (Season 2022)</title>
      <link>https://tfjmp.org/post/2022-interview/</link>
      <pubDate>Fri, 10 Dec 2021 00:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/post/2022-interview/</guid>
      <description>&lt;h3 id=&#34;candidate-presentation-15min&#34;&gt;Candidate presentation (15min)&lt;/h3&gt;
&lt;p&gt;We will start the interview with a brief presentation to give you an opportunity to give voice to your application material.
Use this presentation to explain who you are, what you have done, and what you want to do.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Introduce yourself (~1min)&lt;/li&gt;
&lt;li&gt;Discuss a research project you worked on, clearly focusing on your contribution (~10min)&lt;/li&gt;
&lt;li&gt;Discuss why you want to go to UBC/work with X supervisor/advisor (~4min)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;We are aware that there are systemic barriers that prevent students from realizing their full potential.
For example, you may not have been able to engage in as many research projects you would have liked to for a number of different reasons such as the fact that your home institution is not a research intensive university, you needed to work to pay your tuition, you had family responsibilities etc.
We understand this, and we want to consider each student&amp;rsquo;s potential and help them realize that potential.
You should feel free to point this out during your presentation if you feel comfortable doing so and as you judge it to be appropriate.&lt;/p&gt;
&lt;h3 id=&#34;questions-to-the-applicant-10min&#34;&gt;Questions to the applicant (10min)&lt;/h3&gt;
&lt;p&gt;Following your presentation, we will undoubtedly want to ask you questions about your work as well as questions to assess how well your research interests fit into our lab.&lt;/p&gt;
&lt;h3 id=&#34;paper-reading-10min&#34;&gt;Paper reading (10min)&lt;/h3&gt;
&lt;p&gt;Please pick &lt;strong&gt;one&lt;/strong&gt; paper from the following list:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://dl.acm.org/doi/pdf/10.1145/3448016.3457568&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;Negi, Parimarjan, et al. &amp;ldquo;Steering Query Optimizers: A Practical Take on Big Data Workloads.&amp;rdquo; Proceedings of the 2021 International Conference on Management of Data (SIGMOD). 2021&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://www.ndss-symposium.org/wp-content/uploads/2020/02/24065-paper.pdf&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;Paccagnella, Riccardo, et al. &amp;ldquo;Custos: Practical tamper-evident auditing of operating systems using trusted execution.&amp;rdquo; Network and Distributed System Security Symposium (NDSS). 2020&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://www.usenix.org/system/files/sec21-alsaheel.pdf&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;Alsaheel, Abdulellah, et al. &amp;ldquo;ATLAS: A Sequence-based Learning Approach for Attack Investigation.&amp;rdquo; 30th Security Symposium (USENIX Security). 2021&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://www.usenix.org/system/files/sec21-bahmani.pdf&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;Bahmani, Raad, et al. &amp;ldquo;CURE: A Security Architecture with CUstomizable and Resilient Enclaves.&amp;rdquo; 30th Security Symposium (USENIX Security). 2021&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;You should pick a paper that appears to be the most relevant to the research you are thinking of pursuing.
Reading academic papers is difficult; learning to do so will be an important skill you will acquire in graduate school.
This part of the interview is intended to gauge your ability to engage with the literature and how you think about the research literature.
Do not be intimidated, you will be assessed based on reasonable expectations for someone at your stage.&lt;/p&gt;
&lt;p&gt;You may prepare some slides to discuss the following:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Summarize key points/insights of the paper/what surprised you? [no need to explain the whole thing] (~5min)&lt;/li&gt;
&lt;li&gt;How would you extend/build on the paper? (~5min)&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;discussion-about-research-10min&#34;&gt;Discussion about research (10min)&lt;/h3&gt;
&lt;p&gt;Building on your presentation, we will discuss research directions you could explore during your degree.
The goal is for all parties to gauge the fit between our interests and discuss the general area of research you will pursue during your time at UBC.&lt;/p&gt;
&lt;h3 id=&#34;questions-from-the-applicant-15min&#34;&gt;Questions from the applicant (15min)&lt;/h3&gt;
&lt;p&gt;This is the time for you to ask questions about the lab, UBC, Vancouver or anything you would like to know.
I am also more than happy to put you in touch with my students if you want to hear first hand about students&amp;rsquo; experience.&lt;/p&gt;
&lt;h3 id=&#34;after-the-interview&#34;&gt;After the interview&lt;/h3&gt;
&lt;p&gt;The time between the interview and a decision may vary.
There are multiple factors at play: progress on interviewing other candidates on the shortlist, how busy the committee is, administrative aspects etc.
We try to give offers as early as possible, but the department continues to make offers all the way into April.
Consequently, do not worry if you don&amp;rsquo;t hear back immediately.
On the other hand, if you get another offer and you need to make a decision, do not hesitate to get in touch.&lt;/p&gt;
&lt;p&gt;Once you get an offer, it is important for us to make sure you feel welcomed to the lab and prepare the support you will need.
It is the right time to bring up issues you felt were not appropriate to discuss during the interview, but that you are legitimately concerned about.
This might include questions around finance, accommodations (e.g., childcare, accessibility, etc.), immigration and many more.
I may not be able to help with all those aspects, but I can ask or point you towards appropriate resources.
We want to support our students not only as future researches, but also as individuals, so please, do not hesitate to bring up any concerns you have.
This is also a time for you to ask questions to help you decide which offer to accept (and we hope it will be UBC)!
We recruit bright students, most students will have multiple offers so you should feel free to discuss this openly.&lt;/p&gt;
&lt;h3 id=&#34;acknowledgement&#34;&gt;Acknowledgement&lt;/h3&gt;
&lt;p&gt;Thanks to &lt;a href=&#34;https://www.seltzer.com/margo/&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;Margo&lt;/a&gt; and &lt;a href=&#34;https://aasthakm.github.io/&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;Aastha&lt;/a&gt; for their feedback!&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Tracking and Analyzing Provenance</title>
      <link>https://tfjmp.org/talk/tracking-and-analyzing-provenance/</link>
      <pubDate>Wed, 01 Dec 2021 13:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/talk/tracking-and-analyzing-provenance/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Secure Namespaced Kernel Audit for Containers</title>
      <link>https://tfjmp.org/publication/2021-socc/</link>
      <pubDate>Mon, 01 Nov 2021 00:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/publication/2021-socc/</guid>
      <description>&lt;div align=&#34;center&#34;&gt;
&lt;iframe width=&#34;560&#34; height=&#34;315&#34; src=&#34;https://www.youtube.com/embed/4S7dr4a_Da0&#34; title=&#34;YouTube video player&#34; frameborder=&#34;0&#34; allow=&#34;accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture&#34; allowfullscreen&gt;&lt;/iframe&gt;
&lt;/div&gt;
</description>
    </item>
    
    <item>
      <title>SIGL: Securing Software Installations Through Deep Graph Learning</title>
      <link>https://tfjmp.org/publication/2021-usenixsec/</link>
      <pubDate>Wed, 11 Aug 2021 00:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/publication/2021-usenixsec/</guid>
      <description>&lt;div align=&#34;center&#34;&gt;
&lt;iframe width=&#34;560&#34; height=&#34;315&#34; src=&#34;https://www.youtube.com/embed/iNaucHm7Z6w&#34; title=&#34;YouTube video player&#34; frameborder=&#34;0&#34; allow=&#34;accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture&#34; allowfullscreen&gt;&lt;/iframe&gt;
&lt;/div&gt;
</description>
    </item>
    
    <item>
      <title>Efficient Large-Scale Data Provenance Tracking and Analyzing: Intrusion Detection</title>
      <link>https://tfjmp.org/talk/efficient-large-scale-data-provenance-tracking-and-analyzing-intrusion-detection/</link>
      <pubDate>Thu, 28 Jan 2021 12:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/talk/efficient-large-scale-data-provenance-tracking-and-analyzing-intrusion-detection/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Building a provenance-based intrusion detection system</title>
      <link>https://tfjmp.org/talk/building-a-provenance-based-intrusion-detection-system/</link>
      <pubDate>Tue, 08 Dec 2020 07:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/talk/building-a-provenance-based-intrusion-detection-system/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Building a provenance-based intrusion detection system</title>
      <link>https://tfjmp.org/talk/building-a-provenance-based-intrusion-detection-system/</link>
      <pubDate>Thu, 26 Nov 2020 11:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/talk/building-a-provenance-based-intrusion-detection-system/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Provenance-based intrusion detection</title>
      <link>https://tfjmp.org/talk/provenance-based-intrusion-detection/</link>
      <pubDate>Thu, 12 Nov 2020 10:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/talk/provenance-based-intrusion-detection/</guid>
      <description></description>
    </item>
    
    <item>
      <title>To Tune or not To Tune</title>
      <link>https://tfjmp.org/talk/to-tune-or-not-to-tune/</link>
      <pubDate>Thu, 05 Nov 2020 20:15:00 +0000</pubDate>
      <guid>https://tfjmp.org/talk/to-tune-or-not-to-tune/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Accelerating the Configuration Tuning of Big Data Analytics with Similarity-aware Multitask Bayesian Optimization</title>
      <link>https://tfjmp.org/publication/2020-bigdata/</link>
      <pubDate>Tue, 20 Oct 2020 00:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/publication/2020-bigdata/</guid>
      <description></description>
    </item>
    
    <item>
      <title>To Tune or Not to Tune? In Search of Optimal Configurations for Data Analytics</title>
      <link>https://tfjmp.org/publication/2020-kdd/</link>
      <pubDate>Fri, 01 May 2020 00:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/publication/2020-kdd/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Xanthus: Push-button Orchestration of Host Provenance Data Collection</title>
      <link>https://tfjmp.org/publication/2020-precs/</link>
      <pubDate>Fri, 01 May 2020 00:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/publication/2020-precs/</guid>
      <description>&lt;div align=&#34;center&#34;&gt;
&lt;iframe width=&#34;560&#34; height=&#34;315&#34; src=&#34;https://www.youtube.com/embed/50PpVxcy5WM?start=4017&#34; frameborder=&#34;0&#34; allow=&#34;accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture&#34; allowfullscreen&gt;&lt;/iframe&gt;
&lt;/div&gt;
</description>
    </item>
    
    <item>
      <title>UNICORN: Runtime Provenance-Based Detector for Advanced Persistent Threats</title>
      <link>https://tfjmp.org/publication/2020-ndss/</link>
      <pubDate>Sun, 01 Mar 2020 00:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/publication/2020-ndss/</guid>
      <description>&lt;div align=&#34;center&#34;&gt;
&lt;iframe width=&#34;560&#34; height=&#34;315&#34; src=&#34;https://www.youtube.com/embed/B9ACkb320s0&#34; frameborder=&#34;0&#34; allow=&#34;accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture&#34; allowfullscreen&gt;&lt;/iframe&gt;
&lt;/div&gt;
</description>
    </item>
    
    <item>
      <title>Rclean: A Tool for Writing Cleaner, More Transparent Code</title>
      <link>https://tfjmp.org/publication/2020-joss/</link>
      <pubDate>Sun, 16 Feb 2020 00:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/publication/2020-joss/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Facilitating plausible deniability for cloud providers regarding tenants&#39; activities using trusted execution</title>
      <link>https://tfjmp.org/publication/2020-ic2e/</link>
      <pubDate>Wed, 05 Feb 2020 00:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/publication/2020-ic2e/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Provenance-based Intrusion Detection</title>
      <link>https://tfjmp.org/talk/provenance-based-intrusion-detection/</link>
      <pubDate>Wed, 15 Jan 2020 15:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/talk/provenance-based-intrusion-detection/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Demonstrating the Practicality of Unikernels to Build a Serverless Platform at the Edge</title>
      <link>https://tfjmp.org/publication/2020-cloudcom/</link>
      <pubDate>Wed, 01 Jan 2020 00:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/publication/2020-cloudcom/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Building a provenance-based IDS and the questions we ask ourselves</title>
      <link>https://tfjmp.org/talk/building-a-provenance-based-ids-and-the-questions-we-ask-ourselves/</link>
      <pubDate>Mon, 11 Nov 2019 09:45:00 +0000</pubDate>
      <guid>https://tfjmp.org/talk/building-a-provenance-based-ids-and-the-questions-we-ask-ourselves/</guid>
      <description></description>
    </item>
    
    <item>
      <title>ProvMark: A Provenance Expressiveness Benchmarking System</title>
      <link>https://tfjmp.org/publication/2019-middleware/</link>
      <pubDate>Thu, 05 Sep 2019 00:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/publication/2019-middleware/</guid>
      <description></description>
    </item>
    
    <item>
      <title>From Here to Provtopia</title>
      <link>https://tfjmp.org/publication/2019-poly/</link>
      <pubDate>Mon, 22 Jul 2019 00:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/publication/2019-poly/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Towards provenance-based intrusion detection</title>
      <link>https://tfjmp.org/talk/towards-provenance-based-intrusion-detection/</link>
      <pubDate>Thu, 06 Jun 2019 10:30:00 +0000</pubDate>
      <guid>https://tfjmp.org/talk/towards-provenance-based-intrusion-detection/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Towards Seamless Configuration Tuning of Big Data Analytics</title>
      <link>https://tfjmp.org/publication/2019-icdcs/</link>
      <pubDate>Sun, 19 May 2019 00:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/publication/2019-icdcs/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Viewpoint | Personal Data and the Internet of Things: It is time to care about digital provenance</title>
      <link>https://tfjmp.org/publication/2019-acm-com/</link>
      <pubDate>Thu, 28 Mar 2019 00:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/publication/2019-acm-com/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Towards provenance-based intrusion detection</title>
      <link>https://tfjmp.org/talk/towards-provenance-based-intrusion-detection/</link>
      <pubDate>Mon, 11 Mar 2019 10:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/talk/towards-provenance-based-intrusion-detection/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Building a provenance-based intrusion detection system</title>
      <link>https://tfjmp.org/talk/building-a-provenance-based-intrusion-detection-system/</link>
      <pubDate>Tue, 22 Jan 2019 15:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/talk/building-a-provenance-based-intrusion-detection-system/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Towards a provenance-based intrusion detection system</title>
      <link>https://tfjmp.org/talk/towards-a-provenance-based-intrusion-detection-system/</link>
      <pubDate>Wed, 05 Dec 2018 12:30:00 +0000</pubDate>
      <guid>https://tfjmp.org/talk/towards-a-provenance-based-intrusion-detection-system/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Runtime Analysis of Whole-System Provenance</title>
      <link>https://tfjmp.org/talk/runtime-analysis-of-whole-system-provenance/</link>
      <pubDate>Thu, 18 Oct 2018 11:30:00 +0000</pubDate>
      <guid>https://tfjmp.org/talk/runtime-analysis-of-whole-system-provenance/</guid>
      <description>&lt;div align=&#34;center&#34;&gt;
&lt;iframe width=&#34;560&#34; height=&#34;315&#34; src=&#34;https://www.youtube.com/embed/6VBVwH88o4Y&#34; frameborder=&#34;0&#34; allow=&#34;accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture&#34; allowfullscreen&gt;&lt;/iframe&gt;
&lt;/div&gt;
</description>
    </item>
    
    <item>
      <title>Runtime Analysis of Whole-System Provenance</title>
      <link>https://tfjmp.org/publication/2018-ccs/</link>
      <pubDate>Mon, 15 Oct 2018 00:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/publication/2018-ccs/</guid>
      <description>&lt;div align=&#34;center&#34;&gt;
&lt;iframe width=&#34;560&#34; height=&#34;315&#34; src=&#34;https://www.youtube.com/embed/6VBVwH88o4Y&#34; frameborder=&#34;0&#34; allow=&#34;accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture&#34; allowfullscreen&gt;&lt;/iframe&gt;
&lt;/div&gt;
</description>
    </item>
    
    <item>
      <title>Provenance-based Intrusion Detection: Opportunities and Challenges</title>
      <link>https://tfjmp.org/talk/provenance-based-intrusion-detection-opportunities-and-challenges/</link>
      <pubDate>Wed, 11 Jul 2018 12:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/talk/provenance-based-intrusion-detection-opportunities-and-challenges/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Provenance-based Intrusion Detection: Opportunities and Challenges</title>
      <link>https://tfjmp.org/publication/2018-tapp/</link>
      <pubDate>Tue, 10 Jul 2018 00:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/publication/2018-tapp/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Building a provenance capture mechanism</title>
      <link>https://tfjmp.org/talk/building-a-provenance-capture-mechanism/</link>
      <pubDate>Wed, 06 Jun 2018 15:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/talk/building-a-provenance-capture-mechanism/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Sharing and Preserving Computational Analyses for Posterity with encapsulator</title>
      <link>https://tfjmp.org/publication/2018-cise/</link>
      <pubDate>Tue, 01 May 2018 00:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/publication/2018-cise/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Data provenance to audit compliance with privacy policy in the Internet of Things</title>
      <link>https://tfjmp.org/publication/2018-ubi/</link>
      <pubDate>Sun, 01 Apr 2018 00:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/publication/2018-ubi/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Towards practical whole-system provenance</title>
      <link>https://tfjmp.org/talk/towards-practical-whole-system-provenance/</link>
      <pubDate>Mon, 08 Jan 2018 13:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/talk/towards-practical-whole-system-provenance/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Practical Whole-System Provenance Capture</title>
      <link>https://tfjmp.org/talk/practical-whole-system-provenance-capture/</link>
      <pubDate>Mon, 25 Sep 2017 10:20:00 +0000</pubDate>
      <guid>https://tfjmp.org/talk/practical-whole-system-provenance-capture/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Practical Whole-System Provenance Capture</title>
      <link>https://tfjmp.org/publication/2017-socc/</link>
      <pubDate>Mon, 25 Sep 2017 00:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/publication/2017-socc/</guid>
      <description></description>
    </item>
    
    <item>
      <title>If these data could talk</title>
      <link>https://tfjmp.org/publication/2017-scidata/</link>
      <pubDate>Tue, 05 Sep 2017 00:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/publication/2017-scidata/</guid>
      <description></description>
    </item>
    
    <item>
      <title>FRAPpuccino: Fault-detection through Runtime Analysis of Provenance</title>
      <link>https://tfjmp.org/publication/2017-hotcloud/</link>
      <pubDate>Mon, 10 Jul 2017 00:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/publication/2017-hotcloud/</guid>
      <description></description>
    </item>
    
    <item>
      <title>PHP2Uni: Building Unikernels using Scripting Language Transpilation</title>
      <link>https://tfjmp.org/publication/2017-ic2e/</link>
      <pubDate>Tue, 04 Apr 2017 00:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/publication/2017-ic2e/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Big Ideas paper: Policy-driven middleware for a legally-compliant Internet of Things</title>
      <link>https://tfjmp.org/publication/2016-mw/</link>
      <pubDate>Mon, 12 Dec 2016 00:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/publication/2016-mw/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;https://www.cl.cam.ac.uk/ring/awards.html&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;University of Cambridge Computer Laboratory Publication of the Year Award&lt;/a&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Data-Centric Access Control for Cloud Computing</title>
      <link>https://tfjmp.org/publication/2016-sacmat/</link>
      <pubDate>Mon, 06 Jun 2016 00:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/publication/2016-sacmat/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Twenty security considerations for cloud-supported Internet of Things</title>
      <link>https://tfjmp.org/publication/2016-iot/</link>
      <pubDate>Wed, 01 Jun 2016 00:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/publication/2016-iot/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Information Flow Audit for Transparency and Compliance in the Handling of Personal Data</title>
      <link>https://tfjmp.org/publication/2016-claw/</link>
      <pubDate>Thu, 07 Apr 2016 00:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/publication/2016-claw/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Information Flow Audit for PaaS clouds</title>
      <link>https://tfjmp.org/publication/2016-ic2e/</link>
      <pubDate>Mon, 04 Apr 2016 00:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/publication/2016-ic2e/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Clouds of Things Need Information Flow Control with Hardware Roots of Trust</title>
      <link>https://tfjmp.org/publication/2015-cloudcom/</link>
      <pubDate>Mon, 30 Nov 2015 00:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/publication/2015-cloudcom/</guid>
      <description></description>
    </item>
    
    <item>
      <title>CamFlow: Managed Data-Sharing for Cloud Services</title>
      <link>https://tfjmp.org/publication/2015-tcc/</link>
      <pubDate>Fri, 09 Oct 2015 00:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/publication/2015-tcc/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Data Flow Management and Compliance in Cloud Computing</title>
      <link>https://tfjmp.org/publication/2015-ccm/</link>
      <pubDate>Wed, 16 Sep 2015 00:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/publication/2015-ccm/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Managing Big Data with Information Flow Control</title>
      <link>https://tfjmp.org/publication/2015-cloud/</link>
      <pubDate>Sat, 27 Jun 2015 00:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/publication/2015-cloud/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Securing Tags to Control Information Flows within the Internet of Things</title>
      <link>https://tfjmp.org/publication/2015-riot/</link>
      <pubDate>Tue, 07 Apr 2015 00:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/publication/2015-riot/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Integrating Middleware with Information Flow Control</title>
      <link>https://tfjmp.org/publication/2015-ic2e/</link>
      <pubDate>Mon, 09 Mar 2015 00:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/publication/2015-ic2e/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Expressing and Enforcing Location Requirements in the Cloud using Information Flow Control</title>
      <link>https://tfjmp.org/publication/2015-claw/</link>
      <pubDate>Sun, 08 Mar 2015 00:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/publication/2015-claw/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Information Flow Control for Strong Protection with Flexible Sharing in PaaS</title>
      <link>https://tfjmp.org/publication/2015-fpaas/</link>
      <pubDate>Sun, 08 Mar 2015 00:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/publication/2015-fpaas/</guid>
      <description></description>
    </item>
    
    <item>
      <title>FlowK: Information Flow Control for the Cloud</title>
      <link>https://tfjmp.org/publication/2014-cloudcom/</link>
      <pubDate>Mon, 15 Dec 2014 00:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/publication/2014-cloudcom/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Regional clouds: technical considerations</title>
      <link>https://tfjmp.org/publication/2014-tr/</link>
      <pubDate>Sat, 01 Nov 2014 00:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/publication/2014-tr/</guid>
      <description></description>
    </item>
    
    <item>
      <title>FlowR: Aspect Oriented Programming for Information Flow Control in Ruby</title>
      <link>https://tfjmp.org/publication/2014-modularity/</link>
      <pubDate>Tue, 22 Apr 2014 00:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/publication/2014-modularity/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Information Flow Control for Secure Cloud Computing</title>
      <link>https://tfjmp.org/publication/2014-tnsm/</link>
      <pubDate>Mon, 06 Jan 2014 00:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/publication/2014-tnsm/</guid>
      <description></description>
    </item>
    
    <item>
      <title></title>
      <link>https://tfjmp.org/admin/config.yml</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://tfjmp.org/admin/config.yml</guid>
      <description></description>
    </item>
    
  </channel>
</rss>