Router and Switch Security Policy

1. Overview

See Purpose.

2. Purpose

This document describes a required minimal security configuration for all routers and switches connecting to a production network or used in a production capacity at or on behalf of eCuras.

3. Scope

All employees, contractors, consultants, temporary and other workers at eCuras and its subsidiaries must adhere to this policy. All routers and switches connected to eCuras production networks are affected.

4. Policy

Every router must meet the following configuration standards:

1.      No local user accounts are configured on the router. Routers and switches must use TACACS+ for all user authentication.

2.      The enable password on the router or switch must be kept in a secure encrypted form. The router or switch must have the enable password set to the current production router/switch password from the device’s support organization.

3.      The following services or features must be disabled:

  1. IP directed broadcasts
  2. Incoming packets at the router/switch sourced with invalid addresses such as RFC1918 addresses
  3. TCP small services
  4. UDP small services
  5. All source routing and switching
  6. All web services running on the router
  7. eCuras discovery protocol on Internet connected interfaces
  8. Telnet, FTP, and HTTP services
  9. Auto-configuration

4.      The following services should be disabled unless a business justification is provided:

  1. eCuras discovery protocol and other discovery protocols
  2. Dynamic trunking
  3. Scripting environments, such as the TCL shell

5.      The following services must be configured:

  1. Password-encryption
  2. NTP configured to a corporate standard source

6.      All routing updates shall be done using secure routing updates.

7.      Use corporate standardized SNMP community strings.  Default strings, such as public or private, must be removed.  SNMP must be configured to use the most secure version of the protocol allowed for by the combination of the device and management systems.

8.      Access control lists must be used to limit the source and type of traffic that can terminate on the device itself.

9.      Access control lists for transiting the device are to be added as business needs arise.

10.  The router must be included in the corporate enterprise management system with a designated point of contact.

11.  Each router must have the following statement presented for all forms of login, whether remote or local:

“UNAUTHORIZED ACCESS TO THIS NETWORK DEVICE IS PROHIBITED. You must have explicit permission to access or configure this device. All activities performed on this device may be logged, and violations of this policy may result in disciplinary action and may be reported to law enforcement. There is no right to privacy on this device. The use of this system shall constitute consent to monitoring.”

12.  Telnet may never be used across any network to manage a router unless there is a secure tunnel protecting the entire communication path. SSH version 2 is the preferred management protocol.

13.  Dynamic routing protocols must use authentication in routing updates sent to neighbors.  Password hashing for the authentication string must be enabled when supported.

14.  The corporate router configuration standard will define the category of sensitive routing and switching devices and require additional services or configuration on sensitive devices, including:

  1. IP access list accounting
  2. Device logging
  3. Incoming packets at the router sourced with invalid addresses, such as RFC1918 addresses, or those that could be used to spoof network traffic shall be dropped
  4. Router console and modem access must be restricted by additional security controls

5. Policy Compliance

5.1  Compliance Measurement

The Infosec team will verify compliance with this policy through various methods, including but not limited to periodic walk-thrus, video monitoring, business tool reports, internal and external audits, and feedback to the policy owner.

5.2  Exceptions

The Infosec team must approve any exception to the policy in advance.

5.3  Non-Compliance

An employee found to have violated this policy may be subject to disciplinary action, up to and including termination of employment.

Revised: March 14th, 2018

Table of Content

  1. Acceptable Encryption Policy
  2. Acceptable Use Policy
  3. Clean Desc Policy
  4. Data Breach Response Policy
  5. Disaster Recovery Plan Policy
  6. Digital Signature Acceptance Policy
  7. Email Policy
  8. Ethics Policy
  9. Pandemic Response Planning Policy
  10. Password Construction Guidelines
  11. Password Protection Policy
  12. Security Response Plan Policy
  13. End User Encryption Key Protection Policy
  14. Acquisition Assessment Policy
  15. Bluetooth Baseline Requirements Policy
  16. Remote Access Policy
  17. Remote Access Tools Policy
  18. Router and Switch Security Policy
  19. Wireless Communication Policy
  20. Wireless Communication Standard
  21. Database Credentials Policy
  22. Technology Equipment Disposal Policy
  23. Information Logging Standard
  24. Lab Security Policy
  25. Server Security Policy 
  26. Software Installation Policy
  27. Workstation Security (For HIPAA) Policy
  28. Web Application Security Policy
  29.  Analog/ISDN Line Security Policy
  30. Anti-Virus Guidelines
  31. Server Audit Policy
  32. Automatically Forwarded Email Policy
  33. Communications Equipment Policy
  34. Dial In Access Policy
  35. Extranet Policy
  36. Internet DMZ Equipment Policy
  37. Internet Usage Policy
  38. Mobile Device Encryption Policy
  39. Personal Communication Devices and Voicemail Policy
  40. Removable Media Policy
  41. Risk Assessment Policy
  42. Server Malware Protection Policy
  43. Social Engineering Awareness Policy
  44. DMZ Lab Security Policy
  45. Email Retention Policy
  46. Employee Internet Use Monitoring and Filtering Policy
  47. Lab Anti Virus Policy
  48. Mobile Employee Endpoint Responsibility Policy
  49. Remote Access Mobile Computing Storage
  50. Virtual Private Network Policy