Definition of Snort
Defined as: An open source network intrusion detection system, capable of performing real-time traffic analysis and packet logging on IP networks. It can perform protocol analysis, content searching/matching and can be used to detect a variety of attacks and probes, such as buffer overflows, stealth port scans, CGI attacks, SMB probes, OS fingerprinting attempts, and much more.
|
|
Snort
|
|
Snort, Apache, PHP, MySQL, ACID on Redhat 9.0 Installation Guide
We will install a minimal number of packages, sufficient for a usable system. After the install we'll turn off anything that is not needed. It is an ideal dedicated IDS by hardening the OS and further securing the system. It is, however, also a system that can easily be added to for other uses. There are lots of good articles on how to secure a RedHat box on the web.
Read the Article
|
Snort, Apache, PHP, MySQL, ACID on Solaris 9 Installation Guide
This manual concern the installation and configuration of snort and acid on Solaris9. Of course, all installation of necessary components as mysql, SSL, PHP, adodb, etc .... will be explained too.
Read the Article
|
Snort, MySQL and ACID on Redhat 7.3
The purpose of this guide is to document the installation and configuration of a complete Snort implementation. This guide contains all the necessary information for installing and understanding the architectural layout of the implementation. The information in this guide was written for implementing Snort 1.8 using Redhat 7.3. You may find some discrepancies if you are installing different versions of Snort or using different versions of Redhat.
Read the Article
|
SnortDB database schema
This is a SNORT Database schema diagram in PNG format
Read the Article
|
Snort Tutorial: Guide to basic Snort use
A few months ago I was presented with a task of creating a secure DMZ with Linux servers in it, since I am not a Linux guru yet, I wanted to research different programs and told that I can use to monitor, filter, traffic, as well as some other programs, but it doesn't matter right now. By my friend's recommendation I decided to look into snort as an IDS (Intrusion Detection System). In the following essay I will tell you about writing rules and alerts for snort. I went through a lot of reading and nights of trying to configure it, and playing around with it, and I think that if material was presented in a slightly different fashion if could of made the life of snort users much easier, and so here is some basic information first.
Read the Article
|
Network Intrusion Detection Using Snort
This document takes you through the basics of intrusion detection, the steps necessary to configure a host to run the snort network intrusion detection system, testing its operation, and alerting you to possible intrusion events.
Read the Article
|
Real-Time Alerting with Snort
Real-time alerting is a feature of an IDS or any other monitoring application that notifies a person of an event in an acceptably short amount of time. The amount of time that is acceptable is different for every person.
Read the Article
|
Flying Pigs: Snorting Next Generation Secure Remote Log Servers over TCP
A Comprehensive Guide to Building Encrypted, Secure Remote Syslog-ng Servers with the Snort Intrusion Detection System.
Read the Article
|
Complete Snort-based IDS Architecture, Part One
Intrusion detection systems (IDS) are one of the fastest growing technologies within the security space. Unfortunately, many companies find it hard to justify acquiring IDS systems due to their perceived high cost of ownership (for example see Justifying the Expense of IDS by Kevin Timm and David Kinn). However, not all IDS systems are prohibitively expensive. This two-part article will provide a set of detailed directions to build an affordable intrusion detection architecture from hardware and freely available software. This discussion will avoid the classic "build or buy" debate and instead focus on building the system at a minimum cost.
Read the Article
|
Complete Snort-based IDS Architecture, Part Two
Many companies find it hard to justify acquiring the IDS systems due to their perceived high cost of ownership. However, not all IDS systems are prohibitively expensive. This is second part of a two-part article that will provide a set of detailed directions to build an affordable intrusion detection architecture from hardware and freely available software. In this installment we shall discuss Web interface configuration, summaries and daily reporting, automated attack response, sensor installation, installation of the central station, and big distributed IDS systems.
Read the Article
|
|
|
Page: 1 2 3 4
Members currently browsing this category:
|
|
