* xsm support for restrictive policy and dynamic modification
@ 2016-12-06 14:40 anshul makkar
0 siblings, 0 replies; only message in thread
From: anshul makkar @ 2016-12-06 14:40 UTC (permalink / raw)
To: xen-devel; +Cc: Daniel De Graaf, sds, christopher.w.clark
Hi,
In Xen-Summit, Toronto, I did a presentation on XSM where two
shortcomings with the present implementation were highlighted:
1) Allow more finer grain control. e.g all introspection domain doesn't
need to have pci-passthrough capability while few need to have and all
should have introspection capability.
2) Need for dynamic modification, loading/unloading of the policy.
In response to the above I got few suggestion from the community (Thanks
Daniel De Graf and Stephen Smalley and others) and after researching the
alternatives I found that already existent XSM support for MCS and MLS
and type bound can fit in for finer grain control.
Regarding dynamic support, its something that is still desired and not
implemented. Stephan shared few links related to these:
this:http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.129.7129&rep=rep1&type=pdf
http://oss.tresys.com/archive/policy-server.php
Going forward, I will be focusing towards dynamic implementation as I
believe currently existing infrastructure is sufficient enough to
provide finer level of control over domains.
Thanks
Anshul
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2016-12-06 14:40 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-12-06 14:40 xsm support for restrictive policy and dynamic modification anshul makkar
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).