Conference paper Open Access

Security Type Checking for MILS-AADL Specifications

Pol, Kevin; Noll, Thomas


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">Security</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">MILS components</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">information  flow</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">type system</subfield>
  </datafield>
  <controlfield tag="005">20170908075321.0</controlfield>
  <controlfield tag="001">47989</controlfield>
  <datafield tag="711" ind1=" " ind2=" ">
    <subfield code="d">20 January 2015</subfield>
    <subfield code="a">International Workshop on MILS: Architecture and Assurance for Secure Systems</subfield>
    <subfield code="c">Amsterdam</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">Software Modelling and Verification Group, Aachen University</subfield>
    <subfield code="a">Noll, Thomas</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="s">405707</subfield>
    <subfield code="z">md5:98f0246ba2e0648954648b5c9435283f</subfield>
    <subfield code="u">https://zenodo.org/record/47989/files/05-mils15_submission_8.pdf</subfield>
  </datafield>
  <datafield tag="542" ind1=" " ind2=" ">
    <subfield code="l">open</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="c">2015-01-20</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:47989</subfield>
  </datafield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="u">Software Modelling and Verification Group, Aachen University</subfield>
    <subfield code="a">Pol, Kevin</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">Security Type Checking for MILS-AADL Specifications</subfield>
  </datafield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">user-mils</subfield>
  </datafield>
  <datafield tag="540" ind1=" " ind2=" ">
    <subfield code="u">http://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;Information flow policies are widely used for specifying confidentiality and integrity requirements of security-critical systems. In contrast to access control policies and security protocols, they impose global constraints on the information flow and thus provide end-to-end security guarantees. The information flow policy that is usually adopted is non-interference. It postulates that con dential data must not affect the publicly visible behavior of a system. However, this requirement is usually broken in the presence of cryptographic operations. &lt;/p&gt;

&lt;p&gt;In this paper, we provide an extended definition of non-interference for systems that are specified in a MILS variant of the Architecture Analysis and Design Language (AADL). More concretely, we propose a type system for MILS-AADL component definitions that distinguishes between breaking non-interference because of legitimate use of sufficientlynbsp;strong encryption and breaking non-interference due to annbsp;unintended information leak. To this aim, it tracks bothnbsp;intra- and inter-component information flow and considersbr /&amp;gt; both data- and event-flow security./p&amp;gt;&lt;/p&gt;</subfield>
  </datafield>
  <datafield tag="024" ind1=" " ind2=" ">
    <subfield code="a">10.5281/zenodo.47989</subfield>
    <subfield code="2">doi</subfield>
  </datafield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">publication</subfield>
    <subfield code="b">conferencepaper</subfield>
  </datafield>
</record>
12
8
views
downloads
All versions This version
Views 1212
Downloads 88
Data volume 3.2 MB3.2 MB
Unique views 1212
Unique downloads 77

Share

Cite as