<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>http://kernsec.org/wiki/index.php?action=history&amp;feed=atom&amp;title=Linux_Security_Summit_2014%2FAbstracts%2FKurmus</id>
	<title>Linux Security Summit 2014/Abstracts/Kurmus - Revision history</title>
	<link rel="self" type="application/atom+xml" href="http://kernsec.org/wiki/index.php?action=history&amp;feed=atom&amp;title=Linux_Security_Summit_2014%2FAbstracts%2FKurmus"/>
	<link rel="alternate" type="text/html" href="http://kernsec.org/wiki/index.php?title=Linux_Security_Summit_2014/Abstracts/Kurmus&amp;action=history"/>
	<updated>2026-04-18T08:18:27Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.36.1</generator>
	<entry>
		<id>http://kernsec.org/wiki/index.php?title=Linux_Security_Summit_2014/Abstracts/Kurmus&amp;diff=3507&amp;oldid=prev</id>
		<title>JamesMorris: New page: == Title ==  Quantifying and Reducing the Kernel Attack Surface  == Presenter ==  Anil Kurmus  == Abstract ==  The Linux kernel ships with many features which can be, and are, exploited by...</title>
		<link rel="alternate" type="text/html" href="http://kernsec.org/wiki/index.php?title=Linux_Security_Summit_2014/Abstracts/Kurmus&amp;diff=3507&amp;oldid=prev"/>
		<updated>2014-07-15T16:16:26Z</updated>

		<summary type="html">&lt;p&gt;New page: == Title ==  Quantifying and Reducing the Kernel Attack Surface  == Presenter ==  Anil Kurmus  == Abstract ==  The Linux kernel ships with many features which can be, and are, exploited by...&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;== Title ==&lt;br /&gt;
&lt;br /&gt;
Quantifying and Reducing the Kernel Attack Surface&lt;br /&gt;
&lt;br /&gt;
== Presenter ==&lt;br /&gt;
&lt;br /&gt;
Anil Kurmus&lt;br /&gt;
&lt;br /&gt;
== Abstract ==&lt;br /&gt;
&lt;br /&gt;
The Linux kernel ships with many features which can be, and are, exploited&lt;br /&gt;
by attackers. In this talk, we explore two different approaches to reduce the&lt;br /&gt;
kernel attack surface.  One at compile-time, whereby execution traces of&lt;br /&gt;
the kernel are taken into account to automatically generate a tailored kernel&lt;br /&gt;
configuration. Another at run-time, whereby traces are directly used at&lt;br /&gt;
run-time to detect the use of unnecessary functions by a subset of applications.&lt;br /&gt;
Prior to that, we will give a precise definition of the attack surface and&lt;br /&gt;
propose ways of measuring it, to be able to objectively evaluate the benefits of&lt;br /&gt;
such approaches. Evaluation results show that attack surface reduction is an&lt;br /&gt;
effective approach, whether we quantify attack surface in terms of CVEs&lt;br /&gt;
that would have prevented, or reduction of the amount of reachable code under&lt;br /&gt;
reasonable threat models.&lt;/div&gt;</summary>
		<author><name>JamesMorris</name></author>
	</entry>
</feed>