Best practice #2: Capture traffic 24/7

Omnipeek User Guide

Introduction
Using Capture Engines with Omnipeek
The Capture Window
Dashboards
Viewing and Decoding Packets
Creating and Using Filters
Post-capture Analysis
Expert Analysis
Multi-Segment Analysis
Web Analysis
Voice & Video Analysis
Displaying and Reporting Statistics
Using the Peer Map
Creating Graphs
Setting Alarms and Triggers
Sending Notifications
Using the Name Table
Viewing Logs and Events
Applying Analysis Modules
Configuring Options
Capturing Data for Wireless Analysis
Configuring capture adapters
Omnipeek Remote Assistant
Global Positioning System
Menus and Keyboard Shortcuts
Reference
Analysis Modules
Expert Events
Real-World Security Investigations
- About real-world security investigations
- Investigation #1: Tracing the course of a server attack
- Investigation #2: Ensuring compliance with security regulations and catching leaked data
- Investigation #3: Transaction verification for an online gaming company
- Investigation #4: Transaction verification for a merchant services company
- Security best practices
  Best practice #2: Capture traffic 24/7 Best practice #3: Set filters to detect anomalous behavior Summary
Connecting to a Capture Engine

Omnipeek: Omnipeek User GuideDownload PDF

Real-World Security Investigations : Security best practices : Best practice #2: Capture traffic 24/7

In addition to capturing traffic at every location, IT organizations should ensure that they capture traffic around the clock, so that even anomalies that occur outside of business hours can be investigated.

Security best practices Best practice #3: Set filters to detect anomalous behavior