Lines Matching refs:security
5 Xen provides a security framework called XSM, and FLASK is an implementation of
6 a security model using this framework (at the time of writing, it is the only
29 dom0, and have not been reviewed for security when exposed to
35 Until the interfaces have been properly reviewed for security against
36 hostile callers, the Xen.org security team intends (subject of course
39 normal non-security-related bugs.
41 This applies only to bugs which do no more than reduce the security of
42 a radically disaggregated system to the security of a
49 than reduce the security of such a system to one whose device models,
55 not listed here are considered safe for disaggregation, security
57 to the normal security problem response policy
58 https://www.xenproject.org/security-policy.html.
88 Xen must be compiled with XSM and FLASK enabled; by default, the security
94 full security label of the newly created domain. If using the example policy,
107 The FLASK security framework is mostly configured using a security policy file.
110 built-in policy is enabled ("Compile Xen with a built-in security policy"), the
114 changes to security policy will involve creating or modifying modules found in
247 policy. Static labeling will make security policy machine-specific and may