January 20, 2015 Conference paper Open Access

Pol, Kevin; Noll, Thomas

JSON Export

{
  "conceptrecid": "631413", 
  "created": "2016-03-21T09:00:44+00:00", 
  "doi": "10.5281/zenodo.47989", 
  "files": [
    {
      "bucket": "1895d105-d0af-48f2-ba70-8b27e00e3c54", 
      "checksum": "md5:98f0246ba2e0648954648b5c9435283f", 
      "key": "05-mils15_submission_8.pdf", 
      "links": {
        "self": "https://zenodo.org/api/files/1895d105-d0af-48f2-ba70-8b27e00e3c54/05-mils15_submission_8.pdf"
      }, 
      "size": 405707, 
      "type": "pdf"
    }
  ], 
  "id": 47989, 
  "links": {
    "badge": "https://zenodo.org/badge/doi/10.5281/zenodo.47989.svg", 
    "bucket": "https://zenodo.org/api/files/1895d105-d0af-48f2-ba70-8b27e00e3c54", 
    "doi": "https://doi.org/10.5281/zenodo.47989", 
    "html": "https://zenodo.org/record/47989", 
    "latest": "https://zenodo.org/api/records/47989", 
    "latest_html": "https://zenodo.org/record/47989"
  }, 
  "metadata": {
    "access_right": "open", 
    "access_right_category": "success", 
    "communities": [
      {
        "id": "mils"
      }
    ], 
    "creators": [
      {
        "affiliation": "Software Modelling and Verification Group, Aachen University", 
        "name": "Pol, Kevin"
      }, 
      {
        "affiliation": "Software Modelling and Verification Group, Aachen University", 
        "name": "Noll, Thomas"
      }
    ], 
    "description": "<p>Information flow policies are widely used for specifying confidentiality and integrity requirements of security-critical\u00a0systems. In contrast to access control policies and security\u00a0protocols, they impose global\u00a0constraints on the information flow and thus provide end-to-end security guarantees.\u00a0The information flow policy that is usually adopted is non-interference. It postulates that con dential data must not\u00a0affect the publicly visible behavior of a system. However,\u00a0this requirement is usually broken in the presence of cryptographic operations.\u00a0</p>\n\n<p>In this paper, we provide an extended definition of non-interference for systems that are specified in a MILS variant\u00a0of the Architecture Analysis and Design Language (AADL).\u00a0More concretely, we propose a type system for MILS-AADL\u00a0component definitions that distinguishes between breaking\u00a0non-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;</p>", 
    "doi": "10.5281/zenodo.47989", 
    "keywords": [
      "Security", 
      "MILS components", 
      "information  flow", 
      "type system"
    ], 
    "license": {
      "id": "CC-BY-4.0"
    }, 
    "meeting": {
      "dates": "20 January 2015", 
      "place": "Amsterdam", 
      "title": "International Workshop on MILS: Architecture and Assurance for Secure Systems"
    }, 
    "publication_date": "2015-01-20", 
    "relations": {
      "version": [
        {
          "count": 1, 
          "index": 0, 
          "is_last": true, 
          "last_child": {
            "pid_type": "recid", 
            "pid_value": "47989"
          }, 
          "parent": {
            "pid_type": "recid", 
            "pid_value": "631413"
          }
        }
      ]
    }, 
    "resource_type": {
      "subtype": "conferencepaper", 
      "title": "Conference paper", 
      "type": "publication"
    }, 
    "title": "Security Type Checking for MILS-AADL Specifications"
  }, 
  "owners": [
    20034
  ], 
  "revision": 9, 
  "stats": {
    "downloads": 3.0, 
    "unique_downloads": 2.0, 
    "unique_views": 5.0, 
    "version_downloads": 3.0, 
    "version_unique_downloads": 2.0, 
    "version_unique_views": 5.0, 
    "version_views": 5.0, 
    "version_volume": 1217121.0, 
    "views": 5.0, 
    "volume": 1217121.0
  }, 
  "updated": "2017-09-08T07:53:21.509819+00:00"
}