Brief history of network security from 1837 to present
•Transferir como PPTX, PDF•
1 gostou•4,361 visualizações
“The only thing constant is change” dates back to 500 BC, but it has never rung more true when it comes to managing your network security policy. Bombarded by an onslaught of changes resulting from new applications, emerging threats and network re-architectures, security professionals struggle with manual processes as they sift through hundreds and often thousands of firewall rules and access lists. The result: slow response to business requests, and costly mistakes that cause outages and introduce risk. This presentation covers: · Common risks to avoid when making changes to your network security devices · How to better understand business requirements from the network security perspective · How to accelerate change requests and ensure security and compliance using automation
Recomendados
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Destaque
Destaque (11)
Semelhante a Brief history of network security from 1837 to present
Semelhante a Brief history of network security from 1837 to present (20)
Mais de AlgoSec
Mais de AlgoSec (20)
Último
Último (20)
Brief history of network security from 1837 to present
- 2. “The Only Thing That Is Constant Is Change” - Heraclitus of Ephesus Around 500 B.C.
- 3. A (Very) Brief History of Network Security
- 4. A (Very) Brief History of Network Security 1837
- 5. A (Very) Brief History of Network Security 1837 1969
- 6. A (Very) Brief History of Network Security 1837 1969 1971
- 7. A (Very) Brief History of Network Security 1837 1969 1971 1994
- 8. A (Very) Brief History of Network Security 1837 1969 1971 1994 Present day
- 11. POLL
- 12. 105 A.D.
- 13. 105 A.D. 1564 1974
- 14. We are Using Yesterday’s Technologies to Solve Tomorrow’s Problems
- 15. What Happens When SHIFT Hits the Fan?
- 16. What Happens When SHIFT Hits the Fan? “95% of Firewall breaches are the result of misconfiguration, not firewall flaws” We put our business at Risk
- 17. What Happens When SHIFT Hits the Fan? We Disrupt our business Source: The State of Network Security 2014
- 18. What Happens When SHIFT Hits the Fan? We Slow down our business (Time=Money) Source: Examining the Impact of Security Management on the Business
- 19. Why Do We Deal with So Much (network security) SHIFT?
- 20. Why Do We Deal with So Much (network security) SHIFT? Accelerated Application Delivery
- 21. Why Do We Deal with So Much (network security) SHIFT? Changing Network Architecture
- 22. Why Do We Deal with So Much (network security) SHIFT? Changing Threat Landscape
- 23. Why Do We Deal with So Much (network security) SHIFT? Changing Threat Landscape Changing Network Architecture Accelerated Application Delivery
- 24. Why Do We Deal with So Much (network security) SHIFT? Changing Threat Landscape Changing Network Architecture Accelerated Application Delivery Nothing to do with “Pure” Security
- 25. 7 Deadly Sins of Security Change Management
- 26. Focusing on the “plumbing” instead of the business applications 7 Deadly Sins of Security Change Management
- 27. Not Removing Rules for Decommissioned Applications 7 Deadly Sins of Security Change Management
- 28. Ineffective Communication Between Teams 7 Deadly Sins of Security Change Management
- 29. Not documenting enough (or at all!) 7 Deadly Sins of Security Change Management
- 30. Not Reusing Existing Rules and Objects DB_srv = dbserver = databasesrv 7 Deadly Sins of Security Change Management
- 31. Not Performing Change Reconciliation (no cowboy changes!) 7 Deadly Sins of Security Change Management
- 32. Manual “fat finger” input mistakes (port 443 ≠ port 433) 7 Deadly Sins of Security Change Management
- 33. Best Practices for Security Change Management
- 34. Think Process First (Not just for adding rules!) Best Practices for Security Change Management
- 35. Single Pane of Glass Across Teams -Security, Ops, Apps Across Environments - Physical, Virtual, Cloud Across Devices and Vendors - Firewalls, Router, Proxies Best Practices for Security Change Management
- 36. Application-Centric Approach - map application flows Best Practices for Security Change Management
- 44. Proactively Assess Risk (what-if) Best Practices for Security Change Management
- 46. Perform Validation and Reconciliation Best Practices for Security Change Management
- 49. Automate EVERYTHING that can be automated - Change design - Policy Push - Risk Analysis - Documentation - More… Best Practices for Security Change Management
- 50. Managing Security at the Speed of Business
- 51. Company Overview 5 1 1000+ Customers in 50 countries including 15 of the Fortune 50 The Leader in Security Policy Management “Obsession” for Customer Satisfaction Award-Winning Security Management Suite Technology Partner Ecosystem
- 52. Firewall Analyzer Security Policy Analysis & Audit FireFlow Security Policy Change Automation BusinessFlow Application Connectivity Management Business Applications Security Infrastructure The AlgoSec Suite 5 2 Application Owners AlgoSec Security Management Suite SecurityNetwork Operations
- 53. 5 3
- 54. Learn more algosec.com Learn even more blog.algosec.com Seeing is believing algosec.com/demo Q&A