Reduced Mean-Time-To-Know (MTTK)
By approximately what percentage did the Stealthwatch deployment reduce the time it took to mitigate a security incident?
What types of operational challenges did the use of Stealthwatch by Cisco solve?
Reduction in Mean-Time-to-Know (MTTK) root cause of network or security incidents |
|
|
Improved in network performance |
|
|
Improved network security posture |
|
|
Improved in application performance |
|
|
Improved efficiency in the identification of security threats |
|
|
Improved forensic analysis |
|
|
Increased correlation of user identity and activity |
|
|
Increased visibility of mobile devices |
|
|
Increased flow collection, monitoring and analysis |
|
|
Enhanced compliance posture |
|
This case study of Stanford University is based on a December 2012 survey of Cisco Stealthwatch customers by TechValidate, a 3rd-party research service.
“[Cisco’s Stealthwatch] validates the fact that when a system is compromised/virused – we have the network information to back it up in the form of flows.”
Which of the following security threats have you used Stealthwatch to detect and/or prevent?
Advanced Persistent Threats |
|
|
Network Malware or Virus |
|
|
Suspicious user behavior |
|
|
External hacking attempt |
|
|
Compromised host |
|
|
Data loss / Exfiltration |
|
|
Command and Control traffic / Botnets |
|
|
Network reconnaissance |
|