<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>DSpace Collection:</title>
    <link>http://localhost:8080/xmlui/handle/123456789/2142</link>
    <description />
    <pubDate>Tue, 23 Jun 2026 07:39:22 GMT</pubDate>
    <dc:date>2026-06-23T07:39:22Z</dc:date>
    <item>
      <title>EFFECTIVE INTRUSION DETECTION SYSTEMS USING HYBRID APPROACH</title>
      <link>http://localhost:8080/xmlui/handle/123456789/2143</link>
      <description>Title: EFFECTIVE INTRUSION DETECTION SYSTEMS USING HYBRID APPROACH
Authors: Kalavadekar, Mr. rakash N; Sane, Shirish S
Abstract: - Conventional intrusion prevention&#xD;
methods such as firewalls, access management&#xD;
schemes or cryptography techniques, have not&#xD;
proved themselves to completely defend networks&#xD;
and systems from refined malwares and attacks. The&#xD;
Intrusion Detection Systems (IDS) proved to be the&#xD;
right salvage to the current issues and became an&#xD;
important element of any security infrastructure to&#xD;
sight these threats before they induce widespread&#xD;
harm. The basic aim of IDS is to detect attacks and&#xD;
their nature that may harm the computer system.&#xD;
Several different approaches for intrusion detection&#xD;
have been reported in the literature. These&#xD;
approaches are broadly categorized into three&#xD;
approaches: i) Signature-based approach ii)&#xD;
anomaly based approach and iii) hybrid approach&#xD;
that combines signature and anomaly detection&#xD;
approaches. Hybrid approach has been found to be&#xD;
superior that either signature based or anomaly&#xD;
based approaches. However, despite superior&#xD;
performance, the hybrid approach has till date&#xD;
failed to provide desired detection rate and time&#xD;
needed for detection.</description>
      <pubDate>Fri, 01 Apr 2016 00:00:00 GMT</pubDate>
      <guid isPermaLink="false">http://localhost:8080/xmlui/handle/123456789/2143</guid>
      <dc:date>2016-04-01T00:00:00Z</dc:date>
    </item>
  </channel>
</rss>

