Page 1 - Cisco Tribune Q1 2015
P. 1
Cisco
©
NEWS l PRODUCTS l PEOPLE l EVENTS
TRIBUNE
THE INDEPENDENT REPORT ON THE CISCO TECHNOLOGY MARKET
First Quarter Volume 8, Issue 1 • www.ciscotribune.com • A report published by Telecom Reseller
Voss and Evolution Automate A look at
SEE PAGE 3
SEE PAGE 6
SEE PAGE 6
WidePoint of NetFlow
Cisco
access, action
and change
tracking within
the Cisco UC
environment
Every manager in a medium to large
organization or ISO certiied company
knows the importance of change
management, accountability and the need
for an audit trail. The undisputed number
one cause of system outages is human error,
identifying what has recently changed along
with who made the change can result in
drastically faster restoration times.
Unfortunately The Cisco UC environment
contains little to no tools for logging system
access, tracking changes or administrative
actions such as service restart. Admin
access logs are buried deep in web service
log iles that you have to export off box and
scan to extract who logged on to the server.
Audit logs only show you who made a change to a device but not what the change
was and only on certain objects like phones
or mailboxes. Tracking more important
changes like system settings are practically
impossible.
Previously there was only a single
continues on page 6 ››
NetFlow Intrusion
Detection System
PATTERSON
By Mike Patterson, Plixer
Are you looking for a NetFlow
Intrusion Detection System that
will look for behaviors rather than
deep packet signatures? If you are , there
are several key enablers to look for that will
help ensure you purchase the ideal solution.
Lets take a look at each one:
1. Grouping and sorting: Your system
will need the ability to group on any
element exported in the lows. You might be
thinking about just byte or packet counts
but, why stop there? Newer exports like
those in Cisco AVC export metrics on round
trip time, retransmits, packet loss, jitter
and much more. Don’t compromise for just
the basics.
2. Filters: You will likely need to narrow
your threshold watch based on a speciic
PATTERSON continues on page 6 ››
ADspecs.indd
6
2/6/15
1:15 PM
p1-8_1stQtr_Cisco_Tribune_2015.indd 1
13/03/2015 21:09