Learn how you can safely move to the Cloud without the drawbacks of other approaches. Say no to network redesign, and appliance and solution sprawl. Say yes to a happy DevOps team, scale, high availability, lower costs, and a single forensic haystack for cloud and hybrid environments. All possible because of The ProtectWise Grid.
5. 5 REASONS WHY LEGACY APPROACHES FAIL
1.Requires complete re-architecture
2.Reduced performance and uptime, increased latency
3.Not maintainable with standard cloud approaches
4.Encourages appliance sprawl
5.Expensive to run
6. A MODERN APPROACH IS NEEDED
Security-as-a-Utility
• Provides visibility and forensics for Cloud workloads
• Covers both Cloud and hybrid environments
• Works at scale
8. REQUIREMENT #1: NETWORK REDESIGN NOT REQUIRED
•Out-of-band packet capture
•Software sensors that are
hypervisor agnostic
•Forwarding agents when no
network taps are possible
9. REQUIREMENT #2: DEVOPS FRIENDLY
•Sensors must be lightweight and
run on modern Linux
•Minimal infrastructure, even for
largest environments
•Must be able to automate
deployment of forwarding agents
10. REQUIREMENT #3: HIGHLY SCALABLE
•Analysis in the Cloud, not locally
•Run sensors on modest instances
•Multiple VPC deployment options
•Policy-based traffic filtering
12. REQUIREMENT #5: REDUCE APPLIANCE SPRAWL
•One Cloud platform for
visibility, detection, forensics
•All analysis in the Cloud
•Sensor upgrades not
required for new functionality
in the platform
•Same sensor software for
cloud or on-premises
hardware
19. RECAP: THE 7 REQUIREMENTS
Network redesign should not be required1
Helps to avoid the “appliance tax”6
Should be highly scalable3
Uses native high-availability4
Must be DevOps friendly2
Unified haystack for cloud & hybrid environments7
Reduces appliance sprawl5