Availability constraints for avionic data buses
The three traditional objectives of computer security are confidentiality, integrity and availability. Availability can be defined as the prevention of denial of service. Confidentiality and integrity have been addressed in several theoretical works whereas the concept of availability has not been m...
Gespeichert in:
| Hauptverfasser: | , |
|---|---|
| Format: | Tagungsbericht |
| Sprache: | eng |
| Schlagworte: | |
| Online-Zugang: | Volltext bestellen |
| Tags: |
Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
|
| container_end_page | 131 |
|---|---|
| container_issue | |
| container_start_page | 7 pp. |
| container_title | |
| container_volume | |
| creator | Gabillon, A. Gallon, L. |
| description | The three traditional objectives of computer security are confidentiality, integrity and availability. Availability can be defined as the prevention of denial of service. Confidentiality and integrity have been addressed in several theoretical works whereas the concept of availability has not been much investigated by the scientific community. This paper is an attempt to define through a case study the concept of availability. We first define a set of availability constraints that avionic data bus protocols should enforce. Then, we consider the ARINC 629 basic protocol (BP) which was implemented on the Boeing 777, and we check whether that ARINC 629 BP respects our availability constraints or not. |
| doi_str_mv | 10.1109/ARES.2006.35 |
| format | Conference Proceeding |
| fullrecord | <record><control><sourceid>ieee_6IE</sourceid><recordid>TN_cdi_ieee_primary_1625302</recordid><sourceformat>XML</sourceformat><sourcesystem>PC</sourcesystem><ieee_id>1625302</ieee_id><sourcerecordid>1625302</sourcerecordid><originalsourceid>FETCH-LOGICAL-i213t-6a0cbcc1491788b9df0afe2cc4b8a9fefbc5cefca0f531e9cfd6389acc06862f3</originalsourceid><addsrcrecordid>eNotzE9LwzAYgPGACMrsbTcv_QLt3uRd0uRYxvwDA0Hdebx5m0CkttLEwb69gj6X3-0RYi2hlRLcpn_dv7UKwLSor0TlOgudcVpp07kbUeX8Ab-hQ4vqVmz6M6WRfBpTudQ8T7kslKaS6zgvNZ3TPCWuBypU--8c8p24jjTmUP27EseH_fvuqTm8PD7v-kOTlMTSGAL2zHLrZGetd0MEikExb70lF0P0rDlEJogaZXAcB4PWETMYa1TElbj_-6YQwulrSZ-0XE7SKI2g8AfT-UMi</addsrcrecordid><sourcetype>Publisher</sourcetype><iscdi>true</iscdi><recordtype>conference_proceeding</recordtype></control><display><type>conference_proceeding</type><title>Availability constraints for avionic data buses</title><source>IEEE Electronic Library (IEL) Conference Proceedings</source><creator>Gabillon, A. ; Gallon, L.</creator><creatorcontrib>Gabillon, A. ; Gallon, L.</creatorcontrib><description>The three traditional objectives of computer security are confidentiality, integrity and availability. Availability can be defined as the prevention of denial of service. Confidentiality and integrity have been addressed in several theoretical works whereas the concept of availability has not been much investigated by the scientific community. This paper is an attempt to define through a case study the concept of availability. We first define a set of availability constraints that avionic data bus protocols should enforce. Then, we consider the ARINC 629 basic protocol (BP) which was implemented on the Boeing 777, and we check whether that ARINC 629 BP respects our availability constraints or not.</description><identifier>ISBN: 9780769525679</identifier><identifier>ISBN: 0769525679</identifier><identifier>DOI: 10.1109/ARES.2006.35</identifier><language>eng</language><publisher>IEEE</publisher><subject>Aerospace electronics ; Availability ; Computer crime ; Computer security ; Data buses ; Data security ; Protocols</subject><ispartof>First International Conference on Availability, Reliability and Security (ARES'06), 2006, p.7 pp.-131</ispartof><oa>free_for_read</oa><woscitedreferencessubscribed>false</woscitedreferencessubscribed></display><links><openurl>$$Topenurl_article</openurl><openurlfulltext>$$Topenurlfull_article</openurlfulltext><thumbnail>$$Tsyndetics_thumb_exl</thumbnail><linktohtml>$$Uhttps://ieeexplore.ieee.org/document/1625302$$EHTML$$P50$$Gieee$$H</linktohtml><link.rule.ids>309,310,780,784,789,790,2056,4048,4049,27923,54918</link.rule.ids><linktorsrc>$$Uhttps://ieeexplore.ieee.org/document/1625302$$EView_record_in_IEEE$$FView_record_in_$$GIEEE</linktorsrc></links><search><creatorcontrib>Gabillon, A.</creatorcontrib><creatorcontrib>Gallon, L.</creatorcontrib><title>Availability constraints for avionic data buses</title><title>First International Conference on Availability, Reliability and Security (ARES'06)</title><addtitle>ARES</addtitle><description>The three traditional objectives of computer security are confidentiality, integrity and availability. Availability can be defined as the prevention of denial of service. Confidentiality and integrity have been addressed in several theoretical works whereas the concept of availability has not been much investigated by the scientific community. This paper is an attempt to define through a case study the concept of availability. We first define a set of availability constraints that avionic data bus protocols should enforce. Then, we consider the ARINC 629 basic protocol (BP) which was implemented on the Boeing 777, and we check whether that ARINC 629 BP respects our availability constraints or not.</description><subject>Aerospace electronics</subject><subject>Availability</subject><subject>Computer crime</subject><subject>Computer security</subject><subject>Data buses</subject><subject>Data security</subject><subject>Protocols</subject><isbn>9780769525679</isbn><isbn>0769525679</isbn><fulltext>true</fulltext><rsrctype>conference_proceeding</rsrctype><creationdate>2006</creationdate><recordtype>conference_proceeding</recordtype><sourceid>6IE</sourceid><sourceid>RIE</sourceid><recordid>eNotzE9LwzAYgPGACMrsbTcv_QLt3uRd0uRYxvwDA0Hdebx5m0CkttLEwb69gj6X3-0RYi2hlRLcpn_dv7UKwLSor0TlOgudcVpp07kbUeX8Ab-hQ4vqVmz6M6WRfBpTudQ8T7kslKaS6zgvNZ3TPCWuBypU--8c8p24jjTmUP27EseH_fvuqTm8PD7v-kOTlMTSGAL2zHLrZGetd0MEikExb70lF0P0rDlEJogaZXAcB4PWETMYa1TElbj_-6YQwulrSZ-0XE7SKI2g8AfT-UMi</recordid><startdate>2006</startdate><enddate>2006</enddate><creator>Gabillon, A.</creator><creator>Gallon, L.</creator><general>IEEE</general><scope>6IE</scope><scope>6IL</scope><scope>CBEJK</scope><scope>RIE</scope><scope>RIL</scope></search><sort><creationdate>2006</creationdate><title>Availability constraints for avionic data buses</title><author>Gabillon, A. ; Gallon, L.</author></sort><facets><frbrtype>5</frbrtype><frbrgroupid>cdi_FETCH-LOGICAL-i213t-6a0cbcc1491788b9df0afe2cc4b8a9fefbc5cefca0f531e9cfd6389acc06862f3</frbrgroupid><rsrctype>conference_proceedings</rsrctype><prefilter>conference_proceedings</prefilter><language>eng</language><creationdate>2006</creationdate><topic>Aerospace electronics</topic><topic>Availability</topic><topic>Computer crime</topic><topic>Computer security</topic><topic>Data buses</topic><topic>Data security</topic><topic>Protocols</topic><toplevel>online_resources</toplevel><creatorcontrib>Gabillon, A.</creatorcontrib><creatorcontrib>Gallon, L.</creatorcontrib><collection>IEEE Electronic Library (IEL) Conference Proceedings</collection><collection>IEEE Proceedings Order Plan All Online (POP All Online) 1998-present by volume</collection><collection>IEEE Xplore All Conference Proceedings</collection><collection>IEEE Electronic Library (IEL)</collection><collection>IEEE Proceedings Order Plans (POP All) 1998-Present</collection></facets><delivery><delcategory>Remote Search Resource</delcategory><fulltext>fulltext_linktorsrc</fulltext></delivery><addata><au>Gabillon, A.</au><au>Gallon, L.</au><format>book</format><genre>proceeding</genre><ristype>CONF</ristype><atitle>Availability constraints for avionic data buses</atitle><btitle>First International Conference on Availability, Reliability and Security (ARES'06)</btitle><stitle>ARES</stitle><date>2006</date><risdate>2006</risdate><spage>7 pp.</spage><epage>131</epage><pages>7 pp.-131</pages><isbn>9780769525679</isbn><isbn>0769525679</isbn><abstract>The three traditional objectives of computer security are confidentiality, integrity and availability. Availability can be defined as the prevention of denial of service. Confidentiality and integrity have been addressed in several theoretical works whereas the concept of availability has not been much investigated by the scientific community. This paper is an attempt to define through a case study the concept of availability. We first define a set of availability constraints that avionic data bus protocols should enforce. Then, we consider the ARINC 629 basic protocol (BP) which was implemented on the Boeing 777, and we check whether that ARINC 629 BP respects our availability constraints or not.</abstract><pub>IEEE</pub><doi>10.1109/ARES.2006.35</doi><oa>free_for_read</oa></addata></record> |
| fulltext | fulltext_linktorsrc |
| identifier | ISBN: 9780769525679 |
| ispartof | First International Conference on Availability, Reliability and Security (ARES'06), 2006, p.7 pp.-131 |
| issn | |
| language | eng |
| recordid | cdi_ieee_primary_1625302 |
| source | IEEE Electronic Library (IEL) Conference Proceedings |
| subjects | Aerospace electronics Availability Computer crime Computer security Data buses Data security Protocols |
| title | Availability constraints for avionic data buses |
| url | https://sfx.bib-bvb.de/sfx_tum?ctx_ver=Z39.88-2004&ctx_enc=info:ofi/enc:UTF-8&ctx_tim=2025-01-09T13%3A20%3A56IST&url_ver=Z39.88-2004&url_ctx_fmt=infofi/fmt:kev:mtx:ctx&rfr_id=info:sid/primo.exlibrisgroup.com:primo3-Article-ieee_6IE&rft_val_fmt=info:ofi/fmt:kev:mtx:book&rft.genre=proceeding&rft.atitle=Availability%20constraints%20for%20avionic%20data%20buses&rft.btitle=First%20International%20Conference%20on%20Availability,%20Reliability%20and%20Security%20(ARES'06)&rft.au=Gabillon,%20A.&rft.date=2006&rft.spage=7%20pp.&rft.epage=131&rft.pages=7%20pp.-131&rft.isbn=9780769525679&rft.isbn_list=0769525679&rft_id=info:doi/10.1109/ARES.2006.35&rft_dat=%3Cieee_6IE%3E1625302%3C/ieee_6IE%3E%3Curl%3E%3C/url%3E&disable_directlink=true&sfx.directlink=off&sfx.report_link=0&rft_id=info:oai/&rft_id=info:pmid/&rft_ieee_id=1625302&rfr_iscdi=true |