Module IV
Transféré par
Trong Oganort GampoulaThèmes abordés
- Supervision des équipements,
- Protocoles de sécurité,
- Sécurité réseau,
- Trappes SNMP,
- NAT,
- Traffic autorisé,
- Gestion des flux,
- Pare-feu,
- Surveillance réseau,
- Collecteur SNMP
Module IV
Transféré par
Trong Oganort GampoulaThèmes abordés
- Supervision des équipements,
- Protocoles de sécurité,
- Sécurité réseau,
- Trappes SNMP,
- NAT,
- Traffic autorisé,
- Gestion des flux,
- Pare-feu,
- Surveillance réseau,
- Collecteur SNMP
Common questions
Alimenté par l’IAAccess Control Lists (ACLs) enhance network security by defining which traffic can pass through routers and interfaces, thereby controlling access based on IP address, protocol, or port. In configuring NAT, ACLs specify the internal local addresses that should undergo translation to communicate with external networks. In SNMP configurations, ACLs determine which IP addresses are permitted to access SNMP data, ensuring unauthorized hosts cannot communicate with SNMP agents, thereby securing sensitive network management information .
Stateless firewalls examine each packet independently against a set of predefined rules, which makes them quicker but less intelligent in terms of context awareness. They do not keep track of traffic or connections over time. Conversely, stateful firewalls track active connections and utilize this knowledge to make more informed decisions by accounting for the state of traffic flows. This allows them to recognize legitimate packets in an established session and block unsolicited packets that do not match an established session, providing a higher level of security by observing packet flows across sessions .
The primary advantage of implementing PAT is its efficiency in conserving public IP addresses by mapping multiple internal IP addresses to a single public IP using unique port assignments for each connection. This facilitates internet access for numerous devices within a network with a minimal number of public IPs. However, a major challenge of PAT is that it can become a bottleneck in networks with heavy data traffic, potentially introducing latency and complicating troubleshooting, as multiple connections share a common external address, making it difficult to track individual device activity .
Cisco enhances SNMP security by encouraging the use of access control lists (ACLs) to restrict which IP addresses can use specific SNMP community strings. Best practices for using SNMP community strings include changing the default community string immediately, using complex and unique strings, limiting SNMP operations to read-only access when possible, and applying ACLs to ensure only authorized network management systems can perform SNMP requests, thereby reducing unauthorized access risks .
In SNMP-based network management, agents are processes running on network devices that collect and store management information about the device, exposing it in a standardized format. MIBs define the structure of management data stored by the agents in a hierarchical form, similar to a database schema. Network monitoring software queries agents for data, using the MIB to interpret the responses. This interaction allows for centralized monitoring and control of diverse network devices, enabling comprehensive network management and the swift identification and resolution of issues .
NAT facilitates communication between internal and external networks by translating private IP addresses used within a local network to a public IP address before packets are forwarded over the Internet. When a packet originates from a device in the internal network with a private IP, the NAT router modifies the packet’s IP address to a public one recognized by external systems. This ensures that internal addresses remain hidden from the external network. NAT can be static, with one-to-one mappings between local and global IP addresses, or dynamic, where multiple local addresses can be mapped onto an existing pool of global addresses .
Firewalls play a crucial role in managing DMZ traffic by enforcing security policies that control the flow of traffic between the external network, DMZ, and internal network. They are configured to allow traffic from the external network to the DMZ and the internal network to the DMZ and outside, while blocking any unsolicited inbound traffic to the internal network. Firewalls filter and log traffic, apply rules based on protocol, IP addresses, and ports, ensuring only legitimate traffic is allowed, thus protecting sensitive internal resources from unauthorized access and potential attacks .
A DMZ (DeMilitarized Zone) serves as a buffer zone in a network architecture to host public-facing servers like web, mail, or FTP servers while maintaining internal network security. It is designed to be accessible from both the internal network and the external one without compromising the security of the internal network. This is achieved by applying specific security rules: traffic is allowed from the external network to the DMZ but not to the internal network, and from the internal network to both the DMZ and the external network, while traffic from the DMZ to the internal network is prohibited. This setup helps in protecting the internal network from external threats while providing necessary services to the public .
The use of private IP addresses is essential to conserve the limited number of public IP addresses available under IPv4 addressing. RFC 1918 defines specific address ranges that are to be reserved for private networks which are not routed on the public Internet. These ranges include 10.0.0.0/8 (Class A), 172.16.0.0/12 (Class B), and 192.168.0.0/16 (Class C). By designating these addresses for internal network use, organizations can reduce their dependency on public IP allocations, enabling more efficient use of the globally available IPv4 address space while improving security by isolating internal traffic .
SNMP version 3 enhances security by introducing robust mechanisms for authentication and encryption that were lacking in earlier versions. While SNMP version 1 and 2c relied on a simple community string that did not provide strong protection, SNMP version 3 addresses these weaknesses by supporting secure communication between devices through user authentication, message integrity, and encryption. These features help prevent unauthorized access and protection from eavesdropping or data manipulation .
