Other Open Access

MILS Security Architecture Templates

Tverdyshev, Sergey; Caracuel, Benito; Álvarez, Amelia; Ortaga, Alvaro; Rico, Jose Emilio; Hametner, Reinhard; Blasum, Holger; Kertis, Tomáš; Schulz, Thorsten


MARC21 XML Export

<?xml version='1.0' encoding='UTF-8'?>
<record xmlns="http://www.loc.gov/MARC21/slim">
  <leader>00000nam##2200000uu#4500</leader>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="a">2018-10-15</subfield>
  </datafield>
  <datafield tag="041" ind1=" " ind2=" ">
    <subfield code="a">eng</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">MILS</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">safety</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">securtiy</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">system</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">Common Criteria</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">IEC 62443</subfield>
  </datafield>
  <controlfield tag="005">20191102191100.0</controlfield>
  <controlfield tag="001">1442773</controlfield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">SCHN</subfield>
    <subfield code="a">Caracuel, Benito</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">SCHN</subfield>
    <subfield code="a">Álvarez, Amelia</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">E&amp;E</subfield>
    <subfield code="a">Ortaga, Alvaro</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">E&amp;E</subfield>
    <subfield code="a">Rico,  Jose Emilio</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">THA</subfield>
    <subfield code="a">Hametner, Reinhard</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">SYSGO</subfield>
    <subfield code="a">Blasum, Holger</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">UCO</subfield>
    <subfield code="a">Kertis, Tomáš</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">UROS</subfield>
    <subfield code="a">Schulz, Thorsten</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">Schneider Electric</subfield>
    <subfield code="4">oth</subfield>
    <subfield code="a">Caracuel, Benito</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">Schneider Electric</subfield>
    <subfield code="4">oth</subfield>
    <subfield code="a">Alvarez, Amelia</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">Thales</subfield>
    <subfield code="4">oth</subfield>
    <subfield code="a">Hametner, Reinhard</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">SYSGO</subfield>
    <subfield code="4">oth</subfield>
    <subfield code="a">Blasum, Holger</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">UCO</subfield>
    <subfield code="4">oth</subfield>
    <subfield code="a">Kertis, Tomas</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">Institute of Applied Microelectronics and CE,,University of Rostock</subfield>
    <subfield code="4">oth</subfield>
    <subfield code="a">Schulz, Thorsten</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="s">2169071</subfield>
    <subfield code="z">md5:8e87f1f6438fa4f064a4effa1053999a</subfield>
    <subfield code="u">https://zenodo.org/record/1442773/files/White-Paper-MILS-Security-Architecture-Template.pdf</subfield>
  </datafield>
  <datafield tag="542" ind1=" " ind2=" ">
    <subfield code="l">open</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="c">2018-10-17</subfield>
  </datafield>
  <datafield tag="909" ind1="C" ind2="O">
    <subfield code="p">user-certmils</subfield>
    <subfield code="p">user-mils</subfield>
    <subfield code="o">oai:zenodo.org:1442773</subfield>
  </datafield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="u">SYSGO</subfield>
    <subfield code="a">Tverdyshev, Sergey</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">MILS Security Architecture Templates</subfield>
  </datafield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">user-certmils</subfield>
  </datafield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">user-mils</subfield>
  </datafield>
  <datafield tag="536" ind1=" " ind2=" ">
    <subfield code="c">731456</subfield>
    <subfield code="a">Compositional security certification for medium- to high-assurance COTS-based systems in environments with emerging threats</subfield>
  </datafield>
  <datafield tag="540" ind1=" " ind2=" ">
    <subfield code="u">http://creativecommons.org/publicdomain/zero/1.0/legalcode</subfield>
    <subfield code="a">Creative Commons Zero v1.0 Universal</subfield>
  </datafield>
  <datafield tag="650" ind1="1" ind2="7">
    <subfield code="a">cc-by</subfield>
    <subfield code="2">opendefinition.org</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">&lt;p&gt;The certMILS project (&lt;a href="http://www.certmils.eu/"&gt;http://www.certmils.eu/&lt;/a&gt;) aims at easing building and certification of complex critical systems by using a certain architecture for structuring these systems into partitions that run on a separation kernel, called MILS (Multiple Independent Levels of Security / Safety). Once a critical system is structured by use of a separation kernel, then this technical structuring should lend itself also to a similarly logically structured security and safety argument in certification.&lt;/p&gt;

&lt;p&gt;Analogous to the separation kernel that is to be used for &lt;em&gt;building&lt;/em&gt; a MILS system, this white paper provides a security architecture template that is to be used for the &lt;em&gt;certification&lt;/em&gt; of that MILS system.&lt;/p&gt;

&lt;p&gt;The target audience of this document is:&lt;/p&gt;

&lt;ul&gt;
	&lt;li&gt;Developers of systems, based on a MILS architecture, providing them a template about how to describe their MILS system.&lt;/li&gt;
	&lt;li&gt;Security evaluators of a MILS-based system, giving hints about how the developer description can be used to argue for compliance to Common Criteria (CC) and IEC 62443.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The assurance case made by the security architecture template in this document identifies as building blocks the security mechanisms implemented by a MILS separation kernel and a typical application payload in partitions and derives typical security architecture arguments for MILS-based systems.&lt;/p&gt;</subfield>
  </datafield>
  <datafield tag="773" ind1=" " ind2=" ">
    <subfield code="n">doi</subfield>
    <subfield code="i">isVersionOf</subfield>
    <subfield code="a">10.5281/zenodo.1442772</subfield>
  </datafield>
  <datafield tag="024" ind1=" " ind2=" ">
    <subfield code="a">10.5281/zenodo.1442773</subfield>
    <subfield code="2">doi</subfield>
  </datafield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">publication</subfield>
    <subfield code="b">other</subfield>
  </datafield>
</record>
241
209
views
downloads
All versions This version
Views 241241
Downloads 209209
Data volume 453.3 MB453.3 MB
Unique views 227227
Unique downloads 178178

Share

Cite as