Conference paper Open Access

# Security Type Checking for MILS-AADL Specifications

Pol, Kevin; Noll, Thomas

### Dublin Core Export

<?xml version='1.0' encoding='utf-8'?>
<oai_dc:dc xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/ http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
<dc:creator>Pol, Kevin</dc:creator>
<dc:creator>Noll, Thomas</dc:creator>
<dc:date>2015-01-20</dc:date>
<dc:description>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.

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 /&gt; both data- and event-flow security./p&gt;</dc:description>
<dc:identifier>https://zenodo.org/record/47989</dc:identifier>
<dc:identifier>10.5281/zenodo.47989</dc:identifier>
<dc:identifier>oai:zenodo.org:47989</dc:identifier>
<dc:relation>url:https://zenodo.org/communities/mils</dc:relation>
<dc:rights>info:eu-repo/semantics/openAccess</dc:rights>
<dc:subject>Security</dc:subject>
<dc:subject>MILS components</dc:subject>
<dc:subject>information  flow</dc:subject>
<dc:subject>type system</dc:subject>
<dc:title>Security Type Checking for MILS-AADL Specifications</dc:title>
<dc:type>info:eu-repo/semantics/conferencePaper</dc:type>
<dc:type>publication-conferencepaper</dc:type>
</oai_dc:dc>

12
8
views