<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="13853" 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/13853?output=omeka-xml" accessDate="2026-04-28T20:28:24+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="90841">
              <text>AS-CL IDS: anomaly and signature-based CNN-LSTM intrusion detection system for Internet of Things</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="90842">
              <text>Artificial intelligence; Deep learning; Hybrid intrusion detection; Internet of things; Intrusion detection systems; IoT dataset; Machine learning</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="90843">
              <text>In recent years, the internet of things (IoT) has had a significant impact on our daily lives, offering various advantages for improving our quality of life. However, it is crucial to prioritize the security of IoT devices and the protection of user's personal data. Intrusion detection systems (IDS) play a critical role in maintaining data privacy and security. An IoT IDS continuously monitors network activity and identifies potential security risks or attacks targeting IoT devices. While traditional IDS solutions exist, intrusion detection heavily relies on artificial intelligence (AI). AI can greatly enhance the capabilities of IoT IDS through real-time monitoring, precise threat identification, and automatic response capabilities. It is essential to develop and utilize these technologies securely and responsibly to mitigate potential risks and safeguard user privacy. A hybrid IDS was proposed for anomaly-based and signature-based intrusions, leveraging convolutional neural network with long short-term memory (CNN-LSTM). The name of the proposed hybrid model is anomaly and signaturebased CNN-LSTM intrusion detection system (AS-CL IDS). The AS-CL IDS concentrated on two different IoT IDS detection strategies employing a combination of deep learning techniques. The model includes model training and testing as well as data preprocessing. The CIC-IDS 2018, IoT network intrusion dataset, MQTT-IoT-IDS2020, and BoTNeTIoTL01 datasets were used to train and test the AS-CL IDS. The overall performance of the proposed model was assessed using accepted assessment metrics. Despite reducing the number of characteristics, the model achieved 99.81% accuracy. Furthermore, a comparison was made between the proposed model and existing alternative models to demonstrate its productivity. As a result, the proposed model proves valuable for predicting IoT attacks. Looking ahead, the deployment strategy of the IoT IDS can anticipate the utilization of real-time datasets for future implementations. 2023 Jinsi Jose and Deepa V. Jose.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="90844">
              <text>Jose J.; 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="90845">
              <text>International Journal of Advanced Technology and Engineering Exploration, Vol-10, No. 109, pp. 1622-1639.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="90846">
              <text>Accent Social and Welfare Society</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="90847">
              <text>2023-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="90848">
              <text>&lt;a href="https://doi.org/10.19101/IJATEE.2022.10100187" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.19101/IJATEE.2022.10100187&lt;/a&gt; &lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85181473105&amp;amp;doi=10.19101%2FIJATEE.2022.10100187&amp;amp;partnerID=40&amp;amp;md5=0b6c832fb08086e156f2625d5b67c442" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85181473105&amp;amp;doi=10.19101%2fIJATEE.2022.10100187&amp;amp;partnerID=40&amp;amp;md5=0b6c832fb08086e156f2625d5b67c442&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="90849">
              <text>All Open Access; Gold Open Access</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="46">
          <name>Relation</name>
          <description>A related resource</description>
          <elementTextContainer>
            <elementText elementTextId="90850">
              <text>ISSN: 23945443 | CS; 2023-2024; Vol-1; 00157-00174</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="90851">
              <text>Online</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="90852">
              <text>English</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="90853">
              <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="90854">
              <text>Jose J., Department of Computer Science, CHRIST University, Bangalore, India, Department of Data Science, St. Josephs College, Moolamattom, India; Jose D.V., Department of Computer Science, CHRIST University, Bangalore, India</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
