10/14/2009 10:14 AM
The purpose of this document is to detail the requirements for tracking network device issues in NIMI.
Computer system vulnerabilities are software flaws that can be exploited over a network. Computer
systems that have been compromised may try to infect other systems or provide resources to unauthorized users. This document proposes a structure for tracking computer system vulnerabilities and compromises. Computer system vulnerabilities and compromises are called issues in this document. An important part of managing computer issues is notification. Individual system administrators are notified of issues found for the systems they manage. They are informed when network blocks affect their systems. Network block notification is made when network blocks are installed and lifted. The Data Communication group is notified when network blocks are needed, and when existing blocks can be removed....
10/14/2009 02:52 PM
The purpose of this project is to build a hardware and software infrastructure for network monitoring and status information currently collected and maintained by Data Communications group and Computer Security Team. Such infrastructure will help organize the data collection, storage and access, increase the efficiency of inter-organizational communication and simplify further development of network monitoring and analysis tools....
10/14/2009 03:10 PM
10/14/2009 05:08 PM
Presentation given at CHEP2006
10/14/2009 05:11 PM
Overview of nimi database.
10/14/2009 05:11 PM
Overview of TIssue database
02/25/2010 08:55 AM
Overview and schedule for TIssue v2
TO UPDATE THIS DOCUMENT: - cvs checkout tissue2/docs/* - use PowerPoint to change the original - save as PDF - click on the document link - "New File" (to add newer version)
03/05/2010 03:56 PM
Brief description of the Aged Password Detector for the SMS data.
03/09/2010 02:31 PM
This diagram show how the NIMI collectors, TIssue Detectors and TIssue are all connected.
01/10/2011 10:18 AM
This diagram shows a high-level view of the Event Streams Architecture. Event Streams consists of three parts:
- Event Notifiers:
Gather and parse selected records from a source. Example sources are files or named pipes usually configured