Safe Systems with Linux MC Wrap up and next steps
summary
Group recap stresses concrete next steps: build tooling to identify code snippets and link tests to code, add machine-readable metadata so each change has traceability for 10, 20, 30 years, and collect meaningful documentation formats and test artifacts so compliance with international security regulations is provable. Goal is a low‑ or no‑impact workflow for maintainers that automates linking, trace collection, and test execution so the work scales and survives turnover.
AI-written summary · about
related talks
45mLooking at Linux as a SEooC
38mSafe Systems with Linux
01h 07mPanel Discussion: What is Lacking in Linux Security and What Are or Should We be Doing about This
01h 00mPanel Discussion: What is Lacking in Linux Security and What Are or Should We be Doing about This
42mEnabling Linux in Safety-Critical Applications
47mWhy keeping your system secure is a bit like decluttering
43mHow Do You Know You're Done - After a Security Fix?
05mHow To Automate Compliance If You Aren't Chuck Norris