Conference paper Open Access

MILS Compliant Software Architecture for Satellites

Herpel, H.J.; Kerep, M.; Montano, G.; Eckstein, K.; Schön, M.; Krutak, A.


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="653" ind1=" " ind2=" ">
    <subfield code="a">MILS</subfield>
  </datafield>
  <controlfield tag="005">20200120170215.0</controlfield>
  <controlfield tag="001">47973</controlfield>
  <datafield tag="711" ind1=" " ind2=" ">
    <subfield code="d">19 January 2016</subfield>
    <subfield code="a">International Workshop on MILS: Architecture and Assurance for Secure Systems</subfield>
    <subfield code="c">Prague</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">Airbus DS GmbH</subfield>
    <subfield code="a">Kerep, M.</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">Airbus DS GmbH</subfield>
    <subfield code="a">Montano, G.</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">ESA ESTEC</subfield>
    <subfield code="a">Eckstein, K.</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">ESA ESTEC</subfield>
    <subfield code="a">Schön, M.</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">SYSGO AG</subfield>
    <subfield code="a">Krutak, A.</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="s">4640246</subfield>
    <subfield code="z">md5:202a7afcb940bce67eae2e2b774a5df7</subfield>
    <subfield code="u">https://zenodo.org/record/47973/files/04_Herpel_ASI_SPCC_TN-2649.pdf</subfield>
  </datafield>
  <datafield tag="542" ind1=" " ind2=" ">
    <subfield code="l">open</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="c">2016-01-19</subfield>
  </datafield>
  <datafield tag="909" ind1="C" ind2="O">
    <subfield code="p">openaire</subfield>
    <subfield code="p">user-mils</subfield>
    <subfield code="o">oai:zenodo.org:47973</subfield>
  </datafield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="u">Airbus DS GmbH</subfield>
    <subfield code="a">Herpel, H.J.</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">MILS Compliant Software Architecture for Satellites</subfield>
  </datafield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">user-mils</subfield>
  </datafield>
  <datafield tag="540" ind1=" " ind2=" ">
    <subfield code="u">https://creativecommons.org/licenses/by/4.0/legalcode</subfield>
    <subfield code="a">Creative Commons Attribution 4.0 International</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;Future satellite missions like Earth Observation, Telecommunication or any other kind are likely to be exposed to various threats aiming at exploiting vulnerabilities of the involved systems and communications. Moreover, the growing complexity of systems coupled with more ambitious types of operational scenarios imply increased security vulnerabilities in the future. In the paper we will describe an architecture and&lt;br&gt;
software elements to ensure high level of security on-board a spacecraft. First the threats to the Security Partition Communication Controller (SPCC) will be addressed including the identification of specific vulnerabilities to the SPCC. Furthermore, appropriate security objectives and security requirements are identified to be counter the identified threats. The security evaluation of the SPCC will be done in accordance to the Common Criteria (CC). The Software Elements for SPCC has been&lt;br&gt;
implemented on flight representative hardware which consists of two major elements: the I/O board and the SPCC board. The SPCC board provides the interfaces with ground while the I/O board interfaces with typical spacecraft equipment busses. Both boards are physically interconnected by a high speed spacewire (SpW) link.&lt;/p&gt;</subfield>
  </datafield>
  <datafield tag="024" ind1=" " ind2=" ">
    <subfield code="a">10.5281/zenodo.47973</subfield>
    <subfield code="2">doi</subfield>
  </datafield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">publication</subfield>
    <subfield code="b">conferencepaper</subfield>
  </datafield>
</record>
128
67
views
downloads
All versions This version
Views 128128
Downloads 6767
Data volume 310.9 MB310.9 MB
Unique views 115115
Unique downloads 6161

Share

Cite as