2 # Security configuration
5 menu "Security options"
7 source security/keys/Kconfig
9 config SECURITY_DMESG_RESTRICT
10 bool "Restrict unprivileged access to the kernel syslog"
13 This enforces restrictions on unprivileged users reading the kernel
16 If this option is not selected, no restrictions will be enforced
17 unless the dmesg_restrict sysctl is explicitly set to (1).
19 If you are unsure how to answer this question, answer N.
22 bool "Enable different security models"
26 This allows you to choose different security modules to be
27 configured into your kernel.
29 If this option is not selected, the default Linux security
32 If you are unsure how to answer this question, answer N.
35 bool "Remove the kernel mapping in user mode"
37 depends on X86_64 && SMP && !PARAVIRT
39 This enforces a strict kernel and user space isolation, in order
40 to close hardware side channels on kernel address information.
42 If you are unsure how to answer this question, answer Y.
44 config KAISER_REAL_SWITCH
45 bool "KAISER: actually switch page tables"
49 bool "Enable the securityfs filesystem"
51 This will build the securityfs filesystem. It is currently used by
52 the TPM bios character driver and IMA, an integrity provider. It is
53 not used by SELinux or SMACK.
55 If you are unsure how to answer this question, answer N.
57 config SECURITY_NETWORK
58 bool "Socket and Networking Security Hooks"
61 This enables the socket and networking security hooks.
62 If enabled, a security module can use these hooks to
63 implement socket and networking access controls.
64 If you are unsure how to answer this question, answer N.
66 config SECURITY_NETWORK_XFRM
67 bool "XFRM (IPSec) Networking Security Hooks"
68 depends on XFRM && SECURITY_NETWORK
70 This enables the XFRM (IPSec) networking security hooks.
71 If enabled, a security module can use these hooks to
72 implement per-packet access controls based on labels
73 derived from IPSec policy. Non-IPSec communications are
74 designated as unlabelled, and only sockets authorized
75 to communicate unlabelled data can send without using
77 If you are unsure how to answer this question, answer N.
80 bool "Security hooks for pathname based access control"
83 This enables the security hooks for pathname based access control.
84 If enabled, a security module can use these hooks to
85 implement pathname based access controls.
86 If you are unsure how to answer this question, answer N.
89 bool "Enable Intel(R) Trusted Execution Technology (Intel(R) TXT)"
90 depends on HAVE_INTEL_TXT
92 This option enables support for booting the kernel with the
93 Trusted Boot (tboot) module. This will utilize
94 Intel(R) Trusted Execution Technology to perform a measured launch
95 of the kernel. If the system does not support Intel(R) TXT, this
98 Intel TXT will provide higher assurance of system configuration and
99 initial state as well as data reset protection. This is used to
100 create a robust initial kernel measurement and verification, which
101 helps to ensure that kernel security mechanisms are functioning
102 correctly. This level of protection requires a root of trust outside
103 of the kernel itself.
105 Intel TXT also helps solve real end user concerns about having
106 confidence that their hardware is running the VMM or kernel that
107 it was configured with, especially since they may be responsible for
108 providing such assurances to VMs and services running on it.
110 See <http://www.intel.com/technology/security/> for more information
112 See <http://tboot.sourceforge.net> for more information about tboot.
113 See Documentation/intel_txt.txt for a description of how to enable
114 Intel TXT support in a kernel boot.
116 If you are unsure as to whether this is required, answer N.
118 config LSM_MMAP_MIN_ADDR
119 int "Low address space for LSM to protect from user allocation"
120 depends on SECURITY && SECURITY_SELINUX
121 default 32768 if ARM || (ARM64 && COMPAT)
124 This is the portion of low virtual memory which should be protected
125 from userspace allocation. Keeping a user from writing to low pages
126 can help reduce the impact of kernel NULL pointer bugs.
128 For most ia64, ppc64 and x86 users with lots of address space
129 a value of 65536 is reasonable and should cause no problems.
130 On arm and other archs it should not be higher than 32768.
131 Programs which use vm86 functionality or have some need to map
132 this low address space will need the permission specific to the
135 source security/selinux/Kconfig
136 source security/smack/Kconfig
137 source security/tomoyo/Kconfig
138 source security/apparmor/Kconfig
139 source security/yama/Kconfig
141 source security/integrity/Kconfig
144 prompt "Default security module"
145 default DEFAULT_SECURITY_SELINUX if SECURITY_SELINUX
146 default DEFAULT_SECURITY_SMACK if SECURITY_SMACK
147 default DEFAULT_SECURITY_TOMOYO if SECURITY_TOMOYO
148 default DEFAULT_SECURITY_APPARMOR if SECURITY_APPARMOR
149 default DEFAULT_SECURITY_DAC
152 Select the security module that will be used by default if the
153 kernel parameter security= is not specified.
155 config DEFAULT_SECURITY_SELINUX
156 bool "SELinux" if SECURITY_SELINUX=y
158 config DEFAULT_SECURITY_SMACK
159 bool "Simplified Mandatory Access Control" if SECURITY_SMACK=y
161 config DEFAULT_SECURITY_TOMOYO
162 bool "TOMOYO" if SECURITY_TOMOYO=y
164 config DEFAULT_SECURITY_APPARMOR
165 bool "AppArmor" if SECURITY_APPARMOR=y
167 config DEFAULT_SECURITY_DAC
168 bool "Unix Discretionary Access Controls"
172 config DEFAULT_SECURITY
174 default "selinux" if DEFAULT_SECURITY_SELINUX
175 default "smack" if DEFAULT_SECURITY_SMACK
176 default "tomoyo" if DEFAULT_SECURITY_TOMOYO
177 default "apparmor" if DEFAULT_SECURITY_APPARMOR
178 default "" if DEFAULT_SECURITY_DAC