Project deliverable Open Access
Tverdyshev, Sergey; Caracuel, Benito; Álvarez, Amelia; Ortega, Alvaro; Rico, Jose Emilio; Hametner, Reinhard; Blasum, Holger; Kertis, Tomáš; Schulz, Thorsten
<?xml version='1.0' encoding='UTF-8'?> <record xmlns="http://www.loc.gov/MARC21/slim"> <leader>00000nam##2200000uu#4500</leader> <datafield tag="041" ind1=" " ind2=" "> <subfield code="a">eng</subfield> </datafield> <datafield tag="653" ind1=" " ind2=" "> <subfield code="a">Domain separation</subfield> </datafield> <datafield tag="653" ind1=" " ind2=" "> <subfield code="a">non-bypassability</subfield> </datafield> <datafield tag="653" ind1=" " ind2=" "> <subfield code="a">anti-tamper</subfield> </datafield> <datafield tag="653" ind1=" " ind2=" "> <subfield code="a">secure initialisation</subfield> </datafield> <controlfield tag="005">20200120173345.0</controlfield> <controlfield tag="001">2586566</controlfield> <datafield tag="700" ind1=" " ind2=" "> <subfield code="u">Schneider Electric Espana SA</subfield> <subfield code="a">Caracuel, Benito</subfield> </datafield> <datafield tag="700" ind1=" " ind2=" "> <subfield code="u">Schneider Electric Espana SA</subfield> <subfield code="a">Álvarez, Amelia</subfield> </datafield> <datafield tag="700" ind1=" " ind2=" "> <subfield code="u">Epoche and Espri SLU</subfield> <subfield code="a">Ortega, Alvaro</subfield> </datafield> <datafield tag="700" ind1=" " ind2=" "> <subfield code="u">Epoche and Espri SLU</subfield> <subfield code="a">Rico, Jose Emilio</subfield> </datafield> <datafield tag="700" ind1=" " ind2=" "> <subfield code="u">Thales Austria GmbH</subfield> <subfield code="a">Hametner, Reinhard</subfield> </datafield> <datafield tag="700" ind1=" " ind2=" "> <subfield code="u">SYSGO AG</subfield> <subfield code="a">Blasum, Holger</subfield> </datafield> <datafield tag="700" ind1=" " ind2=" "> <subfield code="u">Unicontrols A.S.</subfield> <subfield code="a">Kertis, Tomáš</subfield> </datafield> <datafield tag="700" ind1=" " ind2=" "> <subfield code="u">Universität Rostock</subfield> <subfield code="a">Schulz, Thorsten</subfield> </datafield> <datafield tag="856" ind1="4" ind2=" "> <subfield code="s">961191</subfield> <subfield code="z">md5:c878d1d04d2fe48628ad361928d18475</subfield> <subfield code="u">https://zenodo.org/record/2586566/files/certMILS-D2.3-Security-Architecture-Template-PU-M16.pdf</subfield> </datafield> <datafield tag="542" ind1=" " ind2=" "> <subfield code="l">open</subfield> </datafield> <datafield tag="260" ind1=" " ind2=" "> <subfield code="c">2018-05-04</subfield> </datafield> <datafield tag="909" ind1="C" ind2="O"> <subfield code="p">openaire</subfield> <subfield code="p">user-certmils</subfield> <subfield code="p">user-mils</subfield> <subfield code="o">oai:zenodo.org:2586566</subfield> </datafield> <datafield tag="100" ind1=" " ind2=" "> <subfield code="u">SYSGO AG</subfield> <subfield code="a">Tverdyshev, Sergey</subfield> </datafield> <datafield tag="245" ind1=" " ind2=" "> <subfield code="a">Security Architecture Template</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">https://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"><p>The certMILS project (<a href="http://www.certmils.eu/">http://www.certmils.eu/</a>) 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. Analogous to the separation kernel that is to be used for building a MILS system, this deliverable provides a security architecture template that is to be used for the certification of that MILS system. The target audience of this document is:</p> <p>* Developers of systems,based on a MILS architecture, providing them a template about how to describe their MILS system.</p> <p>* 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.</p> <p>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.</p></subfield> </datafield> <datafield tag="773" ind1=" " ind2=" "> <subfield code="n">doi</subfield> <subfield code="i">isVersionOf</subfield> <subfield code="a">10.5281/zenodo.2586565</subfield> </datafield> <datafield tag="024" ind1=" " ind2=" "> <subfield code="a">10.5281/zenodo.2586566</subfield> <subfield code="2">doi</subfield> </datafield> <datafield tag="980" ind1=" " ind2=" "> <subfield code="a">publication</subfield> <subfield code="b">deliverable</subfield> </datafield> </record>
All versions | This version | |
---|---|---|
Views | 249 | 249 |
Downloads | 3,037 | 3,034 |
Data volume | 2.9 GB | 2.9 GB |
Unique views | 236 | 236 |
Unique downloads | 2,920 | 2,917 |