From the course: CompTIA Security+ (SY0-701) Cert Prep
Switch configuration security
From the course: CompTIA Security+ (SY0-701) Cert Prep
Switch configuration security
- [Instructor] Network administrators should also be concerned about the security of switches under their care. One of the most important security tasks surrounding switches is maintaining the physical security of the device. Unlike routers which are normally centrally located in secure data centers or network rooms, switches are generally spread all over the place, providing connectivity at the edge of the network in every building and floor throughout an organization. From a security perspective, this can be a nightmare because it's critical to keep those switches locked away where nobody can physically access them without authorization. And the reason for this is simple. If someone gains physical access to your switch, they can take physical control of that portion of the network. Now, earlier in this course, you learned how virtual lands or VLANs may be used to increase the security of networks by isolating unrelated users from each other. Switch administrators should implement some common practices to ensure the secure implementation of VLANs. First, VLAN pruning is a good practice. You might recall that switches use a technology known as VLAN trunking to carry VLANs across the many switches that make up a network. This allows any switch port on the network to join any VLAN trunked to that switch. A best practice for networking is to implement the least privilege rule and only trunk VLANs to switches if the VLAN is needed on that switch. This requires a little more work on the part of network administrators, but it also reduces the impact of a compromised switch. For example, if you have a VLAN for the sales department, and the sales department is contained only within a single building, you should trunk that VLAN within that building, but not into any other buildings. Second, malicious users may attempt an attack known as VLAN hopping to switch from their authorized VLAN, to one containing resources that they would like to attack. They may do this through a variety of means, but most rely upon pretending to be a switch and asking the switch to trunk VLANs to the malicious user's device. The countermeasures for this attack vary from device to device, but generally speaking, you should configure your switches to deny automatic VLAN trunk negotiation and only trunk VLANs when explicitly authorized by a network administrator. Finally, switch administrators may wish to implement a technology known as port security. This protects against attackers disconnecting an authorized device from the wired network, and replacing it with a rogue device that may eavesdrop on other users or attempt to access secure network resources. Port security works by limiting the MAC addresses that may be used on a particular switch port, and requiring administrator intervention to change out a device. Port security works in two different modes. In static mode, the administrator manually configures each switch port with the allowable MAC addresses. This is very time consuming, but this MAC filtering approach is the most secure way to implement port security. In dynamic or sticky mode, the administrator enables port security, and then tells the switch to memorize the first MAC address that it sees on any given port, and then restrict access to that MAC address. This makes configuration much faster, but can be risky if you have unused, but active switch ports. DHCP snooping is another switch level security control that you may implement on your network. This technology allows the switch to inspect DHCP messages to ensure that they're properly formatted and that they're coming from authorized DHCP servers. DHCP snooping can block unauthorized or malformed DHCP messages to better preserve network security.
Download courses and learn on the go
Watch courses on your mobile device without an internet connection. Download courses using your iOS or Android LinkedIn Learning app.
Contents
-
-
The goals of information security2m 11s
-
Authentication, authorization, and accounting (AAA)3m 31s
-
Categorizing security controls5m 11s
-
Conducting a gap analysis2m 34s
-
Zero Trust5m 32s
-
Physical access control4m 40s
-
Physical security personnel2m 12s
-
Deception technologies2m 55s
-
Change management6m 2s
-
-
-
Trust models2m 52s
-
PKI and digital certificates4m 5s
-
Hash functions7m 38s
-
Digital signatures3m 50s
-
Digital signature standard1m 27s
-
Create a digital certificate4m 55s
-
Revoke a digital certificate1m 28s
-
Certificate stapling2m 29s
-
Certificate authorities6m 13s
-
Certificate subjects3m 35s
-
Certificate types2m 55s
-
Certificate formats2m 30s
-
-
-
Preventing SQL injection4m 25s
-
Understanding cross-site scripting3m 17s
-
Request forgery4m 8s
-
Overflow attacks3m 21s
-
Explaining cookies and attachments4m 7s
-
Session hijacking4m 8s
-
Code execution attacks2m 43s
-
Privilege escalation1m 56s
-
OWASP Top Ten4m 45s
-
Application security4m 3s
-
Defending against directory traversal3m 4s
-
Race condition vulnerabilities2m 13s
-
-
-
Restricting network access2m 8s
-
Network access control4m 30s
-
Router configuration security4m 5s
-
Switch configuration security3m 42s
-
Maintaining network availability2m 32s
-
Network monitoring3m 41s
-
SNMP2m 54s
-
Isolating sensitive systems2m
-
Zero trust networking4m 9s
-
Secure access service edge (SASE)3m 50s
-
-
-
Operating system security8m 44s
-
Malware prevention7m 25s
-
Application management3m 46s
-
Host-based network security controls7m 44s
-
File integrity monitoring4m 9s
-
Data loss prevention5m 17s
-
Data encryption5m 39s
-
Hardware and firmware security5m 24s
-
Linux file permissions4m 2s
-
Web content filtering1m 47s
-
-
-
What is vulnerability management?5m 2s
-
Identify scan targets4m 24s
-
Scan configuration5m 20s
-
Scan perspective4m 24s
-
Security Content Automation Protocol (SCAP)2m 27s
-
Common Vulnerability Scoring System (CVSS )3m 31s
-
Analyzing scan reports4m 37s
-
Correlating scan results2m 20s
-
Vulnerability response and remediation2m 14s
-
-
-
Authentication factors3m 26s
-
Multifactor authentication2m 17s
-
Something you have4m 24s
-
Password policy4m 19s
-
Password managers2m 3s
-
Passwordless authentication3m 23s
-
Single sign-on and federation3m 9s
-
Kerberos and LDAP5m 18s
-
SAML2m 35s
-
OAUTH and OpenID Connect2m 55s
-
Certificate-based authentication5m 25s
-