MongoDB - PHP
MongoDB - PHP
MongoDB - PHP
Campus Network:
4 Vital Steps to
Success
Table of Contents
Introduction 3
Summary 13
Overview
organizations accelerate digital innovation, enterprise networks are
much more complicated and dispersed, with an ever-growing number of
edges.1 Organizations increasingly need their networks to do more, so
creating one that can handle all of the demands of today is not enough.
It’s also key to consider what tomorrow will bring, which takes careful
planning. Follow the steps in this ebook to ensure secure connectivity on
a smoothly running network that will be reliable for years to come.
Where?
Every building is different, and over time, the way a building is used can change as well. Before deploying a new
network or a network refresh, ensure that you understand the nature of the physical environment. Track where
users congregate besides the conference rooms. Are there other areas, like manager’s offices, break rooms, and
seating areas, commonly used for collaboration? Be sure to Include additional capacity in these areas as part of
the plan.
In addition, you need to be aware of the materials in use in the building and the furniture. Metal items can have a
serious impact on Wi-Fi signal propagation. Once you understand where additional capacity is needed and where
there are RF obstructions (or other interference sources), you can assemble a solid access point (AP) placement
plan. Then, you can move upstream and ensure that switching capacity to service that number of APs and the
Power over Ethernet (PoE) they will require is sufficient.
Who?
Most enterprise settings have a variety of users, from employees to visitors to contractors. It is critical to know
who these people are, what level of network access they can (and should) expect, and where they can (and
should) have access. Remember that building a network is also about securing it, so have a plan for where visitor
network access or contractor access makes sense and where it doesn’t. Ensure your network is being built for
different access levels depending on user groups.
It’s also important to consider how often your client base typically churns. If new devices frequently enter the
network or if devices tend to go more than three years between replacement cycles, different decisions should be
made regarding networking standards and security measures.
How?
Key considerations include understanding who will be using what applications and how they will be accessed.
Catalog the applications and compare them with the users likely to use them. Ensure that the network is designed
to support any latency or jitter sensitivities among the application set.
Be sure to consider what applications and use patterns are likely to be driven by new or in-flight corporate
initiatives. These may not change current network needs but could impact the network in the future, and the
network being deployed today will need to support future initiatives. These application needs will drive both
network and security planning in later steps.
6
Step 2: Build a Network Plan
Once all the information has been pulled together and
understood, it’s time to build the network plan. We’ll
start at the most common access layer (wireless) and
move inward from there.
there can be value in future-proofing with the latest step one become important here, especially in new
technology. If your network and use patterns are more deployments. Knowledge of the building materials and
steady, there may be less need to push for the latest what furnishings will go into the location can decide
standards, and budget can be reserved. whether RF planning software gets it right or misses
the mark. Most modern Wi-Fi solutions can adjust
To determine proper placement of APs, use site channels and power to compensate for imperfections,
survey data of the current environment or engage but significant planning problems can haunt a
in extensive planning for greenfield deployments. deployment for years if care isn’t taken upfront.
WAN connectivity
Ensuring the proper business outcomes for employees often requires constant and reliable access to applications
and data that reside off-site. Plan WAN connectivity to allow for redundancy and use technology such as SD-WAN
where appropriate to ensure application performance is met. Size WAN connections for the amount of data likely
to leave the site and take into account planned shifts to cloud resources that may put additional requirements on
bandwidth and resiliency of the WAN.
Zero-trust access
A zero-trust framework is one in which nothing and nobody is trusted until verified. This applies whether the
user is within the campus or working remotely, as hybrid work leads to more fluid use of on-site and off-site work
locations.
Security policies must be crafted to give users access to the applications they need and restrict access to those
they do not. The best way to do this is by implementing zero-trust network access (ZTNA) to control application
access within a zero-trust framework.
10
IoT and OT devices
A modern smart campus often has numerous IoT devices that connect to what were traditionally thought of as OT
environments. These devices can be so limited in their network capabilities that they are often considered known
“holes” in a ZTNA plan. Look for solutions that can ensure the easy onboarding of headless devices and those
that can offer virtual patching. Virtual patching allows security systems within the ecosystem to automatically
implement compensating controls when they see IoT or OT devices that have known vulnerabilities.
Never assume that you know what a building is constructed of. If necessary, do some light testing with an AP on
a stick to ensure you catch walls with rebar, leaded glass, or other obstacles.
Assume there will be new applications and needs in the next few years that will push the boundaries of your
network, and plan accordingly.
Design for capacity, not coverage, in most carpeted and public spaces.
Verify switch power budgets and include overhead for new tech.
Pay careful attention to where applications reside (on-premises, in the data center, in a public or private
cloud, or SaaS-based) and plan WAN connectivity accordingly.
Understand all the IoT and OT devices in the installation and plan how they will be secured.
Consider management ease during the vendor selection process, not after the fact.
Ensure that security is layered throughout the design and look for solutions that can converge networking and
security within a common framework.
12
Summary
The campus network continues to become more complex, so when planning a network or network refresh, IT
teams must take into account several factors, including the physical environment, user locations and devices, and
the applications they will use. But perhaps most importantly, security and management cannot be afterthoughts.
By following the steps in this ebook, you can ensure secure connectivity with an easy-to-manage network that will
accommodate your needs now and in the future.
1
Lawrence Miller, “Zero Trust Access for Dummies,” Wiley, 2022.
2
Jonathan Nguyen-Duy, “How to Secure Your Edges Without Inhibiting Productivity,” Fortinet, May 5, 2022.
3
“Securing Wireless Networks,” Cybersecurity & Infrastructure Security Agency, accessed September 5, 2023.
4
Nirav Shah, “Using a Hybrid Mesh Firewall to Increase Network Security,” Fortinet, August 4, 2023.
5
Lawrence Miller, “Zero Trust Access for Dummies,” Wiley, 2022.
www.fortinet.com
Copyright © 2023 Fortinet, Inc. All rights reserved. Fortinet®, FortiGate®, FortiCare® and FortiGuard®, and certain other marks are registered trademarks of Fortinet, Inc., and other Fortinet names herein may also be registered and/or common law trademarks of Fortinet. All other product
or company names may be trademarks of their respective owners. Performance and other metrics contained herein were attained in internal lab tests under ideal conditions, and actual performance and other results may vary. Network variables, different network environments and other
conditions may affect performance results. Nothing herein represents any binding commitment by Fortinet, and Fortinet disclaims all warranties, whether express or implied, except to the extent Fortinet enters a binding written contract, signed by Fortinet’s General Counsel, with a purchaser
that expressly warrants that the identified product will perform according to certain expressly-identified performance metrics and, in such event, only the specific performance metrics expressly identified in such binding written contract shall be binding on Fortinet. For absolute clarity, any
such warranty will be limited to performance in the same ideal conditions as in Fortinet’s internal lab tests. Fortinet disclaims in full any covenants, representations, and guarantees pursuant hereto, whether express or implied. Fortinet reserves the right to change, modify, transfer, or otherwise
revise this publication without notice, and the most current version of the publication shall be applicable.
2327553-0-0-EN