Home > Articles > Security > Network Security

Security and the Management Plane, Part 1

In part 1 of a two-part article, network management specialist Stephen Morris discusses the management plane, its interaction with the other planes, and the need to maintain its security. Some important principles of network management are also discussed along the way.
Like this article? We recommend

Overview of the Management Plane

A few years ago I overheard an IT staffer saying, "I know the salaries of all the people on this site. They're stored on a remote disk and I have the password." This security incident illustrates the crucial point that up to 80% [1] of attacks originate from within organizational boundaries. We should always bear this principle in mind when thinking about securing any system or network:

Security is only as strong as its weakest link (often human or process).

So what's so special about the management plane?

The management plane (MP) provides an important element in the orderly running of networks. It's a valuable resource for deploying and managing increasingly advanced network services including (among others):

  • IP-based differentiated services—voice/video-over IP

  • Layer 3 (or IP) VPN—incorporating MPLS

  • Layer 2 VPN—extending the reach of a LAN across a service provider

The demand for these services is growing and many service providers are deploying them. This change is in response to both user demand and the threat to service providers of price-sensitive, commoditized business models. The service-level agreement (SLA) is a key commercial differentiator of the above services, but SLAs are difficult to achieve without leveraging the MP.

A further, more subtle role for the MP is enabling the alignment of IT and enterprise core business processes. While not the subject of this article, this important topic is all the rage nowadays. One way to effect this alignment is for IT to explicitly define and document the services it manages within an organization, such as the following:

  • Client and server machine configuration

  • Segmenting the network into virtual LANs (VLANs)

  • Software distribution and license management

  • Network protection (antivirus) and security

In a separate step, these services are typically rolled out onto the network via the MP of the associated devices. Following this point, the MP is used to keep the services up and running.

If the process of service definition, rollout, and subsequent management is automated, this setup becomes a powerful way for IT to run the network. In turn, this power can be leveraged by the organization to help achieve its business goals; for example, extending LAN-level services to remote workers, creating secure extranets, and so on. Unfortunately, most organizations use scripts and other proprietary facilities to run their networks. This technique tends to restrict the potential for aligning IT and business goals because so much IT staff time is spent firefighting.

Automating MP interactions (for instance, using network management software) facilitates powerful business-enabling processes. In many ways, the industry focuses on the control plane, often at the expense of the MP. In this article and the next, I hope to illustrate the point that the MP is often an underutilized resource. Hence, the need to secure it!

Security Threats

Traditional threats to security include denial-of-service, hacking, snooping, data modification, and more. The increased deployment of differentiated IP-based services provides the opportunity for a theft-of-service type of attack. In this attack, a user fraudulently marks IP packets in order to receive a higher level of service.

The MP provides facilities for helping in the war against these and many other types of attacks. Let's take a closer look at the MP.

The Management Plane: Network Gold

The MP performs management functions for an overall system and provides coordination among all the planes (control, data, forwarding, and so forth). The MP, control plane, and data plane are illustrated in Figure 1 in conjunction with a remote management system.

Figure 1Figure 1 Management system and conceptual device planes.

The management system in Figure 1 may be one or more of the following:

  • Element Management System (EMS). Handles one or more devices and provides a device-centered perspective.

  • Network Management System (NMS). Handles many devices and provides a network-wide perspective (often communicates with the EMS).

  • Operational Support System (OSS). Handles network-wide operations with interfaces to upper business layers (often drives the NMS).

Regardless of the management system type, all device access passes through the MP. In Figure 1, the MP is shown interacting with the control plane (such as changing a routing table entry on one of the devices in the managed network).

Under the direction of the network manager, the management system interacts with the MP, typically performing reads and writes of managed objects. The MP can also relay notification messages that are sent autonomously from the network to the management system. Typically, the latter message type signifies some important event or fault that has occurred in the network, such as these:

  • Node or link failure (may require rapid reaction to avoid service loss)

  • Onset of congestion in some important part of the network (may require reaction within a few hours)

  • Completion of a software upgrade on a node (may be purely informational)

The bidirectional message exchange allows the management system to keep track of and modify the state of the underlying managed network devices. The MP facilitates this process and allows the management system (and hence the network manager) to keep track of the picture it has of the network.

NOTE

A fundamental rule of network management is that the management system is constantly working to maintain an accurate picture of the state of the managed devices. [2] The more closely matched the management system picture is with the real network, the better.

An important point about Figure 1 is that each managed device—router, switch, hub, etc.—contains its own set of planes (not shown in Figure 1). It is, however, a major goal of the management system (particularly the NMS and OSS) to provide a single system image of the underlying network. In this context, the three planes in Figure 1 can be considered to represent an entire network of devices. This useful abstraction facilitates management scalability as the network grows.

As we'll see later, security demands that every element of Figure 1 be individually secured.

NOTE

It's axiomatic to say that a network is generally only as fast as its slowest element. Similarly, a network is generally only as secure as its least secure element.

Why Provide Planes?

Wouldn't it be easier if networks were just monolithic entities, without having to think about all these planes? Unfortunately not, particularly given the growing complexity of network devices. The provision of planes greatly assists pretty much everyone in the networking value chain: developers, testers, installers, end users. To understand why, let's look at a few common characteristics of network devices:

  • Expensive to develop and purchase

  • Long lived, they may reside in managed networks for years

  • Upgraded over time to add new technologies, such as MPLS, layer 2/3 VPN

Try to think of network devices (routers, switches, hubs, etc.) as special-purpose computers. Typically, they contain many different interfaces on which traffic is sent and received. Modern devices are equipped with interfaces that support many technologies, such as these:

  • Ethernet—legacy or VLAN-aware or QoS-aware (i.e., IEEE 802.1p/Q)

  • HDLC/PPP

  • Frame relay

  • ATM

  • MPLS

  • IP

Configuring and managing services on any of the above is decidedly non-trivial! Many different elements have to be configured, such as layer 2/3 addresses, subnet masks, routing/signaling protocols, virtual circuits, and more.

Separating the various areas of device management, control, and data (among others) into individual planes [3] provides a useful abstraction. End users can then become accustomed to a stable MP user interface; for example, the Cisco CLI is a de facto standard. SNMP provides a slightly less visible point of MP access but is a (de jure) standard nonetheless. By placing CLI and other access technologies into the MP, device vendors can provide a useful division of labor. Unfortunately, sometimes the division into planes results in MP development taking place late in the project lifecycle. This delay presents its own special problems!

If a vendor wants to add new technology support to a device, the vendor (initially) only has to upgrade the control plane. Associated changes to the other planes can then be applied later, rather than having to update all planes at once. This stratagem makes development somewhat easier to control and is similar in concept to the layered architecture of network protocols.

Accessing the Management Plane

Traditionally, access to the MP is made using either the command-line interface (CLI) or a network management protocol (such as SNMP or OSI). Management access to the MP of a given device typically occurs through a dedicated interface such as an Ethernet port, serial port, and so on. Figure 2 illustrates a hard-pressed network manager laboring to keep a big network up and running while her coffee goes cold. Also in Figure 2, we see the two access methods (CLI/SNMPv3) in use by the NMS. We assume that SNMPv3 is in use on all devices in the network. This may not be the case in practice; e.g., legacy devices may not support SNMPv3.

Figure 2Figure 2 Command-line and SNMP access to the management plane.

NOTE

Many network devices also support web access—both secured and unsecured. Many vendors support CLI, SNMP, and web-based access, essentially providing the same facilities from all three methods. In this article and the next, I'll focus on CLI and SNMP only.

CLI is little more than a text menu-based interface, much like that of MS-DOS. Some vendors provide very fine-grained control as part of CLI; for example, with numerous levels of access.

SNMP is somewhat more sophisticated than CLI because it's a standard, message-based protocol with a well-defined, extensible data model.

NOTE

The difference between CLI and SNMP is that CLI provides a human-to-machine interface, while SNMP uses a machine-to-machine interface.

It's likely that as technology advances, the use of SNMP (in conjunction with NMS products) will overtake CLI.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020