From: anshul makkar <anshul.makkar@citrix.com>
To: xen-devel@lists.xenproject.org
Cc: Daniel De Graaf <dgdegra@tycho.nsa.gov>,
sds@tycho.nsa.gov, christopher.w.clark@gmail.com
Subject: xsm support for restrictive policy and dynamic modification
Date: Tue, 6 Dec 2016 14:40:31 +0000 [thread overview]
Message-ID: <4986a089-be4f-7f74-2a1c-676eb337228b@citrix.com> (raw)
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
reply other threads:[~2016-12-06 14:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4986a089-be4f-7f74-2a1c-676eb337228b@citrix.com \
--to=anshul.makkar@citrix.com \
--cc=christopher.w.clark@gmail.com \
--cc=dgdegra@tycho.nsa.gov \
--cc=sds@tycho.nsa.gov \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).