<?xml version="1.0" encoding="UTF-8"?>
<collection xmlns="http://www.loc.gov/MARC21/slim">
    <record>
        <controlfield tag="001">79014</controlfield>
        <controlfield tag="005">20200925115926.0</controlfield>
        <datafield tag="024" ind1="7" ind2=" ">
            <subfield code="2">doi</subfield>
            <subfield code="a">10.1109/ACCESS.2019.2900939</subfield>
        </datafield>
        <datafield tag="024" ind1="8" ind2=" ">
            <subfield code="2">sideral</subfield>
            <subfield code="a">111512</subfield>
        </datafield>
        <datafield tag="037" ind1=" " ind2=" ">
            <subfield code="a">ART-2019-111512</subfield>
        </datafield>
        <datafield tag="041" ind1=" " ind2=" ">
            <subfield code="a">eng</subfield>
        </datafield>
        <datafield tag="100" ind1=" " ind2=" ">
            <subfield code="0">(orcid)0000-0001-7738-5517</subfield>
            <subfield code="a">De Hoz Diego, J.D.</subfield>
        </datafield>
        <datafield tag="245" ind1=" " ind2=" ">
            <subfield code="a">IoTsafe, Decoupling Security from Applications for a Safer IoT</subfield>
        </datafield>
        <datafield tag="260" ind1=" " ind2=" ">
            <subfield code="c">2019</subfield>
        </datafield>
        <datafield tag="506" ind1="0" ind2=" ">
            <subfield code="a">Access copy available to the general public</subfield>
            <subfield code="f">Unrestricted</subfield>
        </datafield>
        <datafield tag="520" ind1="3" ind2=" ">
            <subfield code="a">The use of robust security solutions is a must for the Internet of Things (IoT) devices and their applications: regulators in different countries are creating frameworks for certifying those devices with an acceptable security level. However, even for already certified devices, security protocols have to be updated when a breach is found or a certain version becomes obsolete. Many approaches for securing IoT applications are nowadays based on the integration of a security layer [e.g., using transport layer security, (TLS)], but this may result in difficulties when upgrading the security algorithms, as the whole application has to be updated. This fact may shorten the life of IoT devices. As a way to overcome these difficulties, this paper presents IoTsafe, a novel approach relying on secure socket shell (SSH), a feasible alternative to secure communications in IoT applications based on hypertext transfer protocol (HTTP and HTTP/2). In order to illustrate its advantages, a comparison between the traditional approach (HTTP with TLS) and our scheme (HTTP with SSH) is performed over low-power wireless personal area networks (6loWPAN) through 802.15.4 interfaces. The results show that the proposed approach not only provides a more robust and easy-To-update solution, but it also brings an improvement to the overall performance in terms of goodput and energy consumption. Core server stress tests are also presented, and the server performance is also analyzed in terms of RAM consumption and escalation strategies.</subfield>
        </datafield>
        <datafield tag="536" ind1=" " ind2=" ">
            <subfield code="9">info:eu-repo/grantAgreement/ES/DGA-FEDER/Construyendo Europa desde Aragón</subfield>
            <subfield code="9">info:eu-repo/grantAgreement/ES/DGA/T31-17R</subfield>
            <subfield code="9">info:eu-repo/grantAgreement/ES/MINECO/TIN2015-64770-R-TISFIBE</subfield>
            <subfield code="9">info:eu-repo/grantAgreement/ES/MINECO/TIN2016-76770-R</subfield>
        </datafield>
        <datafield tag="540" ind1=" " ind2=" ">
            <subfield code="9">info:eu-repo/semantics/openAccess</subfield>
            <subfield code="a">All rights reserved</subfield>
            <subfield code="u">http://www.europeana.eu/rights/rr-f/</subfield>
        </datafield>
        <datafield tag="590" ind1=" " ind2=" ">
            <subfield code="a">3.745</subfield>
            <subfield code="b">2019</subfield>
        </datafield>
        <datafield tag="591" ind1=" " ind2=" ">
            <subfield code="a">COMPUTER SCIENCE, INFORMATION SYSTEMS</subfield>
            <subfield code="b">35 / 156 = 0.224</subfield>
            <subfield code="c">2019</subfield>
            <subfield code="d">Q1</subfield>
            <subfield code="e">T1</subfield>
        </datafield>
        <datafield tag="591" ind1=" " ind2=" ">
            <subfield code="a">ENGINEERING, ELECTRICAL &amp; ELECTRONIC</subfield>
            <subfield code="b">61 / 266 = 0.229</subfield>
            <subfield code="c">2019</subfield>
            <subfield code="d">Q1</subfield>
            <subfield code="e">T1</subfield>
        </datafield>
        <datafield tag="591" ind1=" " ind2=" ">
            <subfield code="a">TELECOMMUNICATIONS</subfield>
            <subfield code="b">26 / 90 = 0.289</subfield>
            <subfield code="c">2019</subfield>
            <subfield code="d">Q2</subfield>
            <subfield code="e">T1</subfield>
        </datafield>
        <datafield tag="592" ind1=" " ind2=" ">
            <subfield code="a">0.775</subfield>
            <subfield code="b">2019</subfield>
        </datafield>
        <datafield tag="593" ind1=" " ind2=" ">
            <subfield code="a">Computer Science (miscellaneous)</subfield>
            <subfield code="c">2019</subfield>
            <subfield code="d">Q1</subfield>
        </datafield>
        <datafield tag="593" ind1=" " ind2=" ">
            <subfield code="a">Engineering (miscellaneous)</subfield>
            <subfield code="c">2019</subfield>
            <subfield code="d">Q1</subfield>
        </datafield>
        <datafield tag="593" ind1=" " ind2=" ">
            <subfield code="a">Materials Science (miscellaneous)</subfield>
            <subfield code="c">2019</subfield>
            <subfield code="d">Q2</subfield>
        </datafield>
        <datafield tag="655" ind1=" " ind2="4">
            <subfield code="a">info:eu-repo/semantics/article</subfield>
            <subfield code="v">info:eu-repo/semantics/publishedVersion</subfield>
        </datafield>
        <datafield tag="700" ind1=" " ind2=" ">
            <subfield code="0">(orcid)0000-0002-6977-6363</subfield>
            <subfield code="a">Saldaña, J.</subfield>
            <subfield code="u">Universidad de Zaragoza</subfield>
        </datafield>
        <datafield tag="700" ind1=" " ind2=" ">
            <subfield code="0">(orcid)0000-0002-5237-0447</subfield>
            <subfield code="a">Fernandez-Navajas, J.</subfield>
            <subfield code="u">Universidad de Zaragoza</subfield>
        </datafield>
        <datafield tag="700" ind1=" " ind2=" ">
            <subfield code="0">(orcid)0000-0003-4690-6089</subfield>
            <subfield code="a">Ruiz-Mas, J.</subfield>
            <subfield code="u">Universidad de Zaragoza</subfield>
        </datafield>
        <datafield tag="710" ind1="2" ind2=" ">
            <subfield code="1">5008</subfield>
            <subfield code="2">560</subfield>
            <subfield code="a">Universidad de Zaragoza</subfield>
            <subfield code="b">Dpto. Ingeniería Electrón.Com.</subfield>
            <subfield code="c">Área Ingeniería Telemática</subfield>
        </datafield>
        <datafield tag="773" ind1=" " ind2=" ">
            <subfield code="g">7 (2019), 29942-29962</subfield>
            <subfield code="p">IEEE Access</subfield>
            <subfield code="t">IEEE Access</subfield>
            <subfield code="x">2169-3536</subfield>
        </datafield>
        <datafield tag="856" ind1="4" ind2=" ">
            <subfield code="s">8311503</subfield>
            <subfield code="u">http://zaguan.unizar.es/record/79014/files/texto_completo.pdf</subfield>
            <subfield code="y">Versión publicada</subfield>
        </datafield>
        <datafield tag="856" ind1="4" ind2=" ">
            <subfield code="s">116519</subfield>
            <subfield code="u">http://zaguan.unizar.es/record/79014/files/texto_completo.jpg?subformat=icon</subfield>
            <subfield code="x">icon</subfield>
            <subfield code="y">Versión publicada</subfield>
        </datafield>
        <datafield tag="909" ind1="C" ind2="O">
            <subfield code="o">oai:zaguan.unizar.es:79014</subfield>
            <subfield code="p">articulos</subfield>
            <subfield code="p">driver</subfield>
        </datafield>
        <datafield tag="951" ind1=" " ind2=" ">
            <subfield code="a">2020-09-25-11:45:24</subfield>
        </datafield>
        <datafield tag="980" ind1=" " ind2=" ">
            <subfield code="a">ARTICLE</subfield>
        </datafield>
    </record>

    
</collection>