<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="13803" public="1" featured="0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://omeka.org/schemas/omeka-xml/v5 http://omeka.org/schemas/omeka-xml/v5/omeka-xml-5-0.xsd" uri="https://archives.christuniversity.in/items/show/13803?output=omeka-xml" accessDate="2026-05-06T09:30:44+00:00">
  <collection collectionId="5">
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="64">
                <text>Articles</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </collection>
  <itemType itemTypeId="19">
    <name>Article</name>
    <description>Faculty Publications -Articles</description>
  </itemType>
  <elementSetContainer>
    <elementSet elementSetId="1">
      <name>Dublin Core</name>
      <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
      <elementContainer>
        <element elementId="50">
          <name>Title</name>
          <description>A name given to the resource</description>
          <elementTextContainer>
            <elementText elementTextId="90146">
              <text>Hybrid homomorphic-asymmetric lightweight cryptosystem for securing smart devices: A review</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="90147">
              <text>The Internet of Things (IoT) has emerged as a new concept in information and communication technology, and its structure depends on smart device communications. It was evolving as a significant factor of the Internet and made the interconnection of huge devices likely, accumulating huge amounts of information through innovative technologies. Thus, the requirement for IoT security is more significant. Scalable services and applications are susceptible to information leakage and attacks, demanding higher privacy and security. Cryptography is a technique to secure data integrity, confidentiality, authentication, and network access control. Owing to several limitations of IoT devices, the classical cryptographic protocols are not appropriate for all IoT smart devices like smart cities, smart homes and so forth. Consequently, researchers have introduced numerous lightweight cryptographic (LWC) protocols and algorithms for IoT security. Numerous solutions are available in the research field regarding security using cryptographic algorithms in IoT environments; however, such solutions have not attained satisfactory outcomes. So, finding a solution by examining the recent issues is open research. This article investigates the various LWC protocols for IoT devices and provides a reasonable enquiry into existing ubiquitous ciphers. Furthermore, the article appraises various recently presented lightweight (LW) block ciphers and hybrid homomorphic LWC regarding security. In addition, this article assists in comprehending the significance of security features and progression in cryptographic algorithms. Finally, the article reports on the necessary changes and recommends upcoming research focuses. Also, this article assists in realizing the importance of security and progressions in cryptographic algorithms. 2023 John Wiley &amp;amp; Sons, Ltd.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="90148">
              <text>Mathews R.; Jose D.V.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="48">
          <name>Source</name>
          <description>A related resource from which the described resource is derived</description>
          <elementTextContainer>
            <elementText elementTextId="90149">
              <text>Transactions on Emerging Telecommunications Technologies, Vol-35, No. 1</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="90150">
              <text>John Wiley and Sons Inc</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="40">
          <name>Date</name>
          <description>A point or period of time associated with an event in the lifecycle of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="90151">
              <text>2024-01-01</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="43">
          <name>Identifier</name>
          <description>An unambiguous reference to the resource within a given context</description>
          <elementTextContainer>
            <elementText elementTextId="90152">
              <text>&lt;a href="https://doi.org/10.1002/ett.4866" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1002/ett.4866&lt;/a&gt; &lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85179313097&amp;amp;doi=10.1002%2Fett.4866&amp;amp;partnerID=40&amp;amp;md5=b415405c214a1880f1d8cb1e18f2989a" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85179313097&amp;amp;doi=10.1002%2fett.4866&amp;amp;partnerID=40&amp;amp;md5=b415405c214a1880f1d8cb1e18f2989a&lt;/a&gt;</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="47">
          <name>Rights</name>
          <description>Information about rights held in and over the resource</description>
          <elementTextContainer>
            <elementText elementTextId="90153">
              <text>Restricted Access</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="46">
          <name>Relation</name>
          <description>A related resource</description>
          <elementTextContainer>
            <elementText elementTextId="90154">
              <text>ISSN: 21613915 | CS; 2023-2024; Vol-1; 00141-00156</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="42">
          <name>Format</name>
          <description>The file format, physical medium, or dimensions of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="90155">
              <text>Online</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="90156">
              <text>English</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="90157">
              <text>Article</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="38">
          <name>Coverage</name>
          <description>The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant</description>
          <elementTextContainer>
            <elementText elementTextId="90158">
              <text>Mathews R., Department of Computer Science, Christ University, Karnataka, Bangalore, India, Department of Computer Science and Engineering, St. Mary's College, Kerala, Sulthan Bathery, India; Jose D.V., Department of Computer Science, Christ University, Karnataka, Bangalore, India</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
