Conference paper Open Access

An Architecture-Centric Process for MILS Development

Delange, Julien; Nam, Min-Young; Feiler, Peter; Klieber, Will


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">AADL</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">MILS</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">Security</subfield>
  </datafield>
  <controlfield tag="005">20200120172425.0</controlfield>
  <controlfield tag="001">47976</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">Carnegie Mellon Software Engineering Institute</subfield>
    <subfield code="a">Nam, Min-Young</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">Carnegie Mellon Software Engineering Institute</subfield>
    <subfield code="a">Feiler, Peter</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">Carnegie Mellon Software Engineering Institute</subfield>
    <subfield code="a">Klieber, Will</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="s">249023</subfield>
    <subfield code="z">md5:6a35ddf5daf6608e9f5b04dd2b20eddc</subfield>
    <subfield code="u">https://zenodo.org/record/47976/files/05-final-mils-paper-JulienDelange.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:47976</subfield>
  </datafield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="u">Carnegie Mellon Software Engineering Institute</subfield>
    <subfield code="a">Delange, Julien</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">An Architecture-Centric Process for MILS Development</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;Safety-critical embedded systems are now software-reliant and evolving at an incredible pace. With the emerging Internet of Things (IoT) ecosystem, these systems are now interconnected to several networks and exposed to potential attackers. This increases the potential surface of attack and, ultimately, the likelihood of a successful attack that would penetrate the system. Until recently, many security efforts were focused on code analysis, but studies have shown that security is also a matter of good software architecture design and practices. For example, MILS requires isolating security domains in partitions using appropriate security components. However, because embedded systems are evolving quickly, new design methods are now required to overcome the challenges of developing them.&lt;/p&gt;

&lt;p&gt;In this paper, we introduce a research agenda for a new architecturecentric development approach forMILS systems. This would leverage architecture models and augment them with security information in order to perform the different activities of the development process, including security policy validation, implementation, and testing. Using the same model throughout development improves the consistency of the development process by avoiding any translation between different—and potentially inconsistent—representations. In addition, automating the generation of implementation and tests avoids the traditional mistakes of manual code production, such as bugs and developers’ assumptions about ambiguous requirements.&lt;/p&gt;</subfield>
  </datafield>
  <datafield tag="024" ind1=" " ind2=" ">
    <subfield code="a">10.5281/zenodo.47976</subfield>
    <subfield code="2">doi</subfield>
  </datafield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">publication</subfield>
    <subfield code="b">conferencepaper</subfield>
  </datafield>
</record>
124
90
views
downloads
All versions This version
Views 124124
Downloads 9089
Data volume 22.4 MB22.2 MB
Unique views 111111
Unique downloads 7978

Share

Cite as