Notes - MIECT
Segurança Em Redes De Comunicações
Notes - MIECT
Segurança Em Redes De Comunicações
  • Segurança Em Redes De Comunicações
  • Corporate Networks Topics
    • Objectives of Network Design
    • Equipments
    • Hierarchical Network Model
    • Modular Network Design
    • Designing the Access Layer
    • Designing the Core Layer
    • Virtual LANs
      • VLANs on Access Points
    • Spanning Tree Protocol
    • IP Routing Overview
  • Introduction to Network Security
    • Type of Attacks
    • Attacks Phases
      • Infiltration Phase
      • Propagation Phase
      • Aggregation and Exfiltration Phase
    • Defenses
    • Security Metrics
  • Network Access Control
    • AAA Architecture
      • TACACS+
      • RADIUS
      • DIAMETER
    • IEEE 802.11 services
    • Joining a BSS
      • WLAN Frames
      • Joining BSS with AP
    • WPA and 802.11i (WPA2)
  • Network Flow Control
    • Network Security Systems
    • Firewalls
    • High-Availability
    • Load Balancing Firewall Load
    • Best Practices and Recommendations
    • IP Spoofing
    • Half-Open TCP Connection Problem
    • DDoS Mitigation at Source
    • Cisco’s Access Control Lists (ACL)
    • Linux IPTables
    • Control By Analysis of Higher Layers
  • Secure Communications
    • Public Key Infrastructure (PKI)
    • X.509 Certificate Contents
    • Traffic Tunnel Concept
      • Next Hop Resolution Protocol (NHRP)
      • Hub-Spoke vs. Spoke-Spoke
    • IPSec
    • Establishing SA and Cryptographic Keys
    • Virtual Private Networks (VPN)
    • Management of Asymmetric Keys
  • Remote Access
    • Remote Access
    • IPsec NAT Transversal
    • Integration with Flow Control
  • Intrusion Detection and Prevention
    • Intrusion Detection and Prevention
    • Host-Based vs. Network-Based
    • Signature vs. Anomaly Based
    • Network Deployment
  • Network Monitoring SIEM
    • Core and End-to-End Monitoring
    • Node Monitoring
    • End-User/Host/App Monitoring
    • Server/Service/Cloud Monitoring
    • Per-Service Detailed Monitoring
    • Data Sources
      • SNMP
      • NetFlow
    • Network Passive Probing Packet Capturing
    • Remote CLI Access
    • Log Files Access
      • Log Management Systems (LMS)
      • Security Information and Events Management (SIEM)
Powered by GitBook
On this page
  • Algorithms
  • Addressed Firewalls
  • Stealth Firewalls
  • Load-Balancers Instances
  • Redundant Load Balancers
  • Addressed Firewalls
  • Stealth Firewalls
  • Single Load Balancer
  • Multi-Levels of Defense
  1. Network Flow Control

Load Balancing Firewall Load

PreviousHigh-AvailabilityNextBest Practices and Recommendations

Last updated 2 years ago

Load-balancing equipment can distribute traffic by multiple firewalls.

  • Decrease processing and memory requirements of each firewall.

  • Allow for scalable growth of traffic.

  • Makes the network less vulnerable to DoS attacks.

  • When its also responsible to distribute policies/rules is called an Orchestrator.

Algorithms

IP Hash.

  • The IP address (or a set of flow identifiers) of the client is used to determine which server/firewall receives the flow or request.

  • Does not require state maintenance. Hash function output determines the target.

Round Robin.

  • Requests are distributed across the group of servers sequentially.

  • Can not be used with firewalls, if firewalls do not share a state.

Least Connections.

  • A new request is sent to the server/firewall with the fewest current connections.

  • The relative computing capacity of each server/firewall is factored into determining which one has the least connections.

“Smart”.

  • Based on an external source of information.

Addressed Firewalls

Interfaces have IP addresses.

Load balancers (or routers) route traffic as an IP next-hop.

Can provide routing services.

  • Replace routers.

Stealth Firewalls

Interfaces do not have IP addresses.

  • May have multiple-layer rules.

Load balancers (or switches) route traffic on a per-interface/VLAN basis.

Can not provide routing or NAT/PAT services.

  • Can not replace routers.

Load-Balancers Instances

Load balancers may have (theoretical) isolated instances to handle different zones/groups.

  • With a set of firewalls per zone/group.

Physical or virtual partitions.

Some vendors call it group ports.

Redundant Load Balancers

Addressed Firewalls

Balancers should share routing history.

  • Flow is sent always to the same firewall.

  • To avoid firewall state sharing (less load).

Stealth Firewalls

Balancers should share VLAN routing history.

  • Flow is sent always to the same VLAN/Firewall.

  • To avoid firewall state sharing (less load).

Single Load Balancer

Multi-Levels of Defense

First Level of stateless firewalls for DDoS protection.

Second Level(s) of stateful firewalls for general protection.

Information from services may be used.

  • To free resources in the stateful firewalls.

  • Configure black/white list rules at the stateless firewalls.