Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

7 Security Requirements to Accelerate Cloud Adoption

193 views

Published on

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.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

7 Security Requirements to Accelerate Cloud Adoption

  1. 1. 7 SECURITY REQUIREMENTS TO ACCELERATE CLOUD ADOPTION
  2. 2. TODAY’S SPEAKERS Anthony Guida Principal Security Architect ProtectWise Kelly Brazil Vice President of Systems Engineering ProtectWise
  3. 3. AGENDA • Why legacy approaches fail • What are the key requirements for an effective solution • How The ProtectWise Grid can help
  4. 4. MIGRATING TO THE CLOUD? HOW LEGACY PRODUCTS FAIL.
  5. 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. 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
  7. 7. REQUIREMENTS FOR AN EFFECTIVE SOLUTION
  8. 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. 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. 10. REQUIREMENT #3: HIGHLY SCALABLE •Analysis in the Cloud, not locally •Run sensors on modest instances •Multiple VPC deployment options •Policy-based traffic filtering
  11. 11. REQUIREMENT #4: BUILT-IN HIGH AVAILABILITY
  12. 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
  13. 13. REQUIREMENT #6: COST REDUCTION Legacy Solutions Security-as-a-Utility Avoid the “appliance tax”
  14. 14. REQUIREMENT #7: UNIFIED HAYSTACK
  15. 15. HOW CAN THE PROTECTWISE GRID HELP?
  16. 16. THE PROTECTWISE GRID 1 6 CLOUD INGEST VISUALIZER EGRESS CORE REMOTE INDUSTRIAL NETWORK SENSORS Flexible deployment OPTIMIZED NETWORK REPLAY Compression & Optimization up to 80% ENTERPRISE SECURITY PLATFORM Secure, long-term full packet retention (months or years) TIME MACHINE SECURE VAULT
  17. 17. A TIME MACHINE FOR THREAT DETECTION Network Traffic Machine Learning Behavior Analysis 3rd Party Threat Intel Heuristics 24 hours 1 month 6 month 1 year RETROSPECTIVE ANALYTICS +6 months +1 month +24 hours PREDICTIVE ANALYSIS REAL TIME ANALYTICS C1 C2 C3 COLLECTIVE CORRELATION Signatures BYOI
  18. 18. DEMO
  19. 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
  20. 20. QUESTIONS
  21. 21. NEXT STEPS •We’ll send you a copy of our white paper “Deploying ProtectWise in the Cloud” •Questions? Email info@protectwise.com
  22. 22. THANK YOU

×