"בכל אדם מתקנא, חוץ מבנו ותלמידו" [גמרא, סנהדרין כה ב]
My students: 
  • Graduated PhD students: Haya Shulman, Moti Geva, Yossi GiladNethanel Gelernter [founded Cyberpion]
  • Current PhD student:  Yehonatan Kfir and Mai Ben Adar - Bessos. 
  • Current MSc students: Hod Bin-Noon, Michael Goberman,  Ariel Bruckman, Hai Rozencwajg, Hemi Leibowitz, Roee Shlomo, Yoel Grinstein.  
  • Graduated (MSc):  Michael Sudkovitch, Shay Nachmani, Boaz Catane, Raz Abramov, Ronen Margulis, Yossi Gilad, Haya Shulman, Michael Sedletsky, Alex Dvorkin, Ahmad Jabra, Igal Yoffe, Yitchak Gertner.

Prospective students:

  • My advising style involves a lot of interaction and involvement. Therefore, regrettably, I must strictly limit the number of students I advise.  Currently (Jan'17) I'm at almost full capacity. I am only able to take one more student (until others graduate), and only in one of my main current areas: routing-security, Cyber-Physical systems security, privacy/anonymity, DoS.    
  • I prefer students that study full-time (or near so); I make rare exceptions, mostly to students still in Israeli mandatory military service (I studied this way too, so it seems fair). 
  • I try to help students financially via grants; this depends on availability, and sometimes on specific research direction taken by student. [I currently have funding for the next few years already secured]
  • Before we begin thesis-research and before I 'commit' to advising a student, we begin with a 'project'. This project allows us both to check if we want to continue to full advising 'relationship'. Usually, things go well and we move to thesis, using the project either as basis to the thesis or just for academic credit (i.e., a course); I usually am also happy to pay for the hours spent on the project, or give some grant to compensate the candidate for not being able to work during these hours. When things don't go so well, student still has the academic credit (assuming project is completed), and we part as friends - not every student is compatible with every adviser. 
  • Interested students should contact me by email. Include CV, grades, recommendations, explanation of your availability and preferred areas. It is best to take at least one of my classes before beginning.  
  • Before we meet, it is surely a good idea to read some of my recent publications - and feedback (bugs, questions, etc.) are very very welcome, indeed, providing good, harsh, constructive feedback is a great way to get into research!

Tips and guidelines for graduate students:

  1. Search and read - a lot... use keywords and previous articles to find new works. In particular use Google ScholarCiteseerx, and ACM Portal. Use Citeseer and Scholar to find citations, crucial for searching an area. Once you identify important author, look for other publications in her homepage and in DBLP. Many articles are available online. University provides online access to many sources When all fails, ask authors by email - most researchers will help you (also with questions). My students are welcome to consult with me on such emails. 

  2. Improve your (English) writing style. Two (of the many) great online sources: Lynch's guide to grammar and style, and the very concise Strunk's `The Elements of Style` (this online version is 1st edition; I use 3rd edition, by Strunk and White - you can loan it). Here are my own notations rules:

     Rule Meaning
     More (notations) is Less (readable) Avoid duplicate and unnecessary notations. Two notations for same term? Penalty!
     Undefined is Unacceptable An undefined term or notation is high treason. Double penalty!
     Never overbook symbols! Using the same notation for two different purposes is ultimate crime. Triple penalty!!
     Relatives are similar Use similar (related) notations for similar (related) purposes
     Only relatives are similar Don't use similar notations for unrelated purposes (weak form of overbooking)
     Consistency Use consistency among notations, e.g., same font type for all (and only) sets, and for all probabilities, ... 

  3. Write using LaTeX, e.g. with TeXnicCenter.  I use, and recommend, the Algorithm2e package for writing algorithms and protocols, and TikZ package for figures. Two cute tools (sites): Detextify (find LaTeX macros for symbols by scribbling them) and EqnEditor (online equation editor).  For figures and presentations, I recommend either to use LaTeX's Beamer package, or Open-Office. Another handy site counts words in a latex documents. I recommend (and use) cloud-based editing, mainly

  4. Citations are important and could be surprisingly painful... but LaTeX makes life easier with BiBTeX citations, available from the Collection of Computer Science BibliographiesDBLP orACM PortalScholar also provides BibTex citations (if you set preference), but less reliable (i.e.: use only as last resort, and fix as needed). We have a great bibtex file for our entire group (in our SVN), use it! For managing citations, I use and recommend JabRef. 

  5. Consider carefully where and when to publish, don't leave it as afterthought. To find conferences: use confsearch or, for security CFPs, see collections UCL and IEEE. I also maintain (sometimes...) a small document of conferences which I can share with you. Discuss preferences and plans with me and others.

  6. Read a lot, review a lot (when requested :-) ), discuss and present your work, and cooperate with others. Just be cautious to avoid misunderstandings when you discuss your work, some people will expect to become coauthors when you thought it was just friendly discussion. Also, people often (innocently) forget they heard some problem/solution in a discussion, and `reinvent` it... common problem and usually not intentional.