The schedule for the 2019 Linux Security Summit North America (LSS-NA) is published.

This year, there are some changes to the format of LSS-NA. The summit runs for three days instead of two, which allows us to relax the schedule somewhat while also adding new session types.  In addition to refereed talks, short topics, BoF sessions, and subsystem updates, there are now also tutorials (one each day), unconference sessions, and lightning talks.

The tutorial sessions are:

• The How and Why of libseccomp, by Paul Moore (Cisco) and Tom Hromatka (Oracle);
• Complete Platform Attestation, by Monty Wiseman and Avani Dave (General Electric); and
  
• How to Write a Linux Security Module, by Casey Schaufler (Intel), Paul Moore (Cisco), and John Johansen (Canonical).

These tutorials will be 90 minutes in length, and they’ll run in parallel with unconference sessions on the first two days (when the space is available at the venue).

The refereed presentations and short topics cover a range of Linux security topics including platform boot security, integrity, container security, kernel self protection, fuzzing, and eBPF+LSM.

Some of the talks I’m personally excited about include:

• TrenchBoot – How to Nicely Boot System with Intel TXT and AMD SVM, by Daniel Kiper (Oracle) and Daniel Smith (Apertus);
• Kernel Runtime Security Instrumentation, by KP Singh (Google);
• Writing Linux Kernel Modules in Safe Rust, by Geoffrey Thomas (Two Sigma) and Alex Gaynor (Alloy); and
  
• Retrospective: 26 Years of Flexible MAC, keynote by Stephen Smalley (NSA).
  

The schedule last year was pretty crammed, so with the addition of the third day we’ve been able to avoid starting early, and we’ve also added five minute transitions between talks. We’re hoping to maximize collaboration via the more relaxed schedule and the addition of more types of sessions (unconference, tutorials, lightning talks).  This is not a conference for simply consuming talks, but to also participate and to get things done (or started).

Thank you to all who submitted proposals.  As usual, we had many more submissions than can be accommodated in the available time.

Also thanks to the program committee, who spent considerable time reviewing and discussing proposals, and working out the details of the schedule. The committee for 2019 is: