How to Build the Perfect Network From the Outside In

Piecing Through Network Platforms

When it comes to considering platforms for a network implementation, Nilsson suggests keeping all things wireless in mind, especially additives.

Some of these decisions may include, “which Wi-Fi standard to implement for wireless; Cloud-managed versus on-premises wireless controllers; what speed the wired network should be running at (faster may be better, but is more expensive); switches versus routers for wired connections, etc.,” Nilsson says.

Liberman says security platforms should be top of mind during a network implementation. This is because all platforms, no matter how robust they are, are at risk, he says.

“There has been no method of communication of ingress in a network that has not been touched by hackers,” Liberman says. “There are hundreds of millions of people whose full time job is to be a criminal and attack; their goal is to make a quick hit and get out…It’s an issue that has to be overcome.”

For Knapp, physical space is key regarding platforms, particularly when a tech manager defines his or her wiring and cabling standards.

“I think that space is important in data closets and in riser conduits,” he says. “Too often, floor data closets are undersized, and conduits between them and other locations are lacking in growth potential. You don’t build buildings often, so [tech managers should] have adequate space for both now, and ten years from now.”

And, “you need backup power,” Knapp says. “The closets don’t only need uninterrupted power supplies, but they also need to be on generators. People want their wireless, and as the internet of things (IoT) grows, HVAC, phones, light controls, etc. are running over the IP network. It needs to stay up, so building that into the plan is crucial.”

Tech Managers’ Network Mistakes – And How to Fix Them

Skipping Over Security

One common mistake tech managers make, Liberman says, is assuming each layer of a network is designed to be secure by default.

“There is no such thing,” he says. “Things [pieces of a network] are useful and easy by default – every manufacturer does ease of use before security. [Tech managers should] just assume things are insecure, and work backwards.”

To get ahead of hackers and a potential network breach, Liberman says tech managers should dress the network in armored layers.

“Assume that one security layer won’t protect you,” he says.

Liberman also says that enforcing security policies, such as requiring employees, or faculty and staff, to change their network password on a regular basis. Such policies can help tech managers arm their networks with tighter security, and reduce the risk of a breach.

Failing To Plan Ahead

Nilsson says tech managers can commit a big blunder when they implement a network for just “the now.”

“The biggest mistake is not planning for the future; purchasing low-end products that are not expandable and do not provide the level of monitoring and control necessary to provide a high quality network experience for the users,” he says.

Planning for the future can help tech managers anticipate what the next upgrade for the network will be, and will help a corporation or institution keep up with the networks of competitors.

Resisting Change

Some tech managers may be reluctant to changes needed for a network, or do not see the value of a change, Knapp says. This builds a roadblock in tech managers advancing the network, and minimizes the opportunity to meet end users’ needs.

“If you resist, users will figure out on their own how to build their own micro-rogue networks to support what they desire,” Knapp says.

Being flexible with network changes increases the chance of creating a successful network, and keeping end users happy. Flexibility will also reduce the risk of running into unwanted network surprises, such as hacked information.

“We need to anticipate the day when people will come to the workplace or residential network with a dozen personal devices,” Knapp says. “Their expectations will be high and we need to develop the skills and implement the technology to help facilitate the use of this technology.”

Tips To Follow Before You Build a Network

To implement a successful network, Nilsson says that tech managers should take their time when making decisions, and during the actual building phases. Doing so helps tech managers minimize potential mistakes, instate beneficial policies, and prepare for digital attacks.

“Running and managing a network can be challenging, so it’s best to optimize for easier network management, even if it requires more upfront setup time,” Nilsson says. “Without the right tools, it can be difficult and time-consuming to find network problems when an outage occurs. A policy-based network management approach may take a little more time to set up, but will be much easier to manage and modify throughout the life of the network.”

Liberman says that tech managers should not think that they can implement a network alone, or that they can do it without receiving training.

The best way to increase the chances of implementing a successful network is by asking for help.

“Seek advice from experts in the field, from online forums, and other peers,” Liberman says. “Or go to network professionals and vet their capabilities. You have to find the people who have a clue as to what is going on there [with networks].”

For tech managers who worry about creating an air-tight network, Liberman recommends conserving the mental energy – all networks will experience some degree of a breach, no matter how secure it is.

While preparing against a potential attack, Liberman says, education among tech managers and end users is a good way to keep the network safe.

“It is impossible to secure a network – realize that,” says Liberman. “Triage it in a manner that you spend 80 percent of the time against common attacks, and whittle it down…Go through the list of how you can be attacked, and once you have the baseline in place, own it. You cannot over enforce something.”

Knapp says securing a network in layers should be a top priority – this is because layers function as a barrier that protects institutional network information.

“I think that you should have multiple layers to get from the internal network to protected networks that contain sensitive or key institutional data,” he says. “I think network managers need to have more of a vested interest in protecting data. Security can be a pain, and using secure protocols makes it hard to read clear text packets and figure out connectivity issues. However, secure protocols protect institutional data. It is a balance, but in today’s environment, we need to be protective of the network.”