Network Security Checklist
Network Security Checklist
adaptation. The latest evolutionary demands for corporate networks include the cloud and
remote work—environments where the old hub-and-spoke approach is less than ideal.
Cloud-based network security is purpose-built to secure resources wherever they reside.
Zero Trust means only permitting access to those Firewall-as-a-Service works with ZTNA to prevent
who require it and continually verifying that each anyone from accessing resources without an
person is meeting pre-determined access policies. authorized identity such as a specific user, group, or
Zero Trust Network Access (ZTNA) secures company originating IP address. Just like on-premises firewalls,
resources at the application level employing standard FWaaS defends against unwanted entry into company
logins and MFA authorization, as well as at the device resources and networks.
level utilizing posture checks, and context-based
permissions such as time of day and location.
A Secure Web Gateway (SWG) protects company A network security solution should be responsive
employees while web browsing. It prevents outbound and provide a smooth user experience. To enable
traffic from accessing restricted content such as this, the solution should ideally be cloud-based with
gambling sites, as well as known or suspected points-of-presence (PoPs) distributed throughout the
malicious file destinations. It also scans inbound globe. Companies can then choose PoPs in locations
traffic for malicious web content. near their employees, for better responsiveness and
connectivity rather than backhauling traffic through
physical data centers.
Assess Your Needs (VPN replacement, cloud firewall, Zero Trust solutions,
DNS filtering, device posture check, etc.)
The first thing you need to do is assess what your corporate infrastructure
looks like, be it as a list or a diagram. It’s important to understand your on-
premises needs such as the number of data centers your company has.
Also include all the cloud services the company uses—at least the ones you
know about. Again, try to be as exhaustive as possible, not forgetting about
that one Heroku app that DevOps is using.
Then it’s on to endpoints. What kind of devices are your remote employees
using? Is it all company-owned Macs, a mix of Windows and Mac, what
about phones or tablets that might be used to access company resources?
Also consider BYOD devices and what employees are currently using those
for.
Locations are also a key part of assessing your needs since this will help
determine the optimal PoPs to connect to.
Next, it’s time to consider what we’re trying to accomplish with the move
to a cloud-based network security provider. Is it purely a VPN replacement
with better latency for employees spread out across multiple locations? Do
you want to boost security with a modern Zero Trust approach that includes
more restrictive permissions instead of providing carte blanche access to
the network and resources?
What about adding a SWG for secure web access and malware protection,
as well as logging activity for incident response purposes? Do you need
static IPs, or access control at the DNS level?
If you have your own homegrown identity management system then look
for services that support the System for Cross-domain Management (SCIM)
specification. If your company uses multiple providers, support for Security
Assertion Markup Language (SAML) 2.0 is also a must.
Once you have your identity provider worked out and implemented it’s
important to consider user group permissions for your future Zero Trust
Network Access approach. Sales and marketing may need access to
Salesforce, for example, but those departments don’t need access to the
codebase on GitHub, or the production database for the website. These
kinds of finely segmented permissions make it easier to control who has
access to what, and limit the impacts of a breach should the worst happen.
Once you’ve got everything figured out in terms of infrastructure, needs and
goals, and compliance requirements, you have an excellent list to take with
you during product research.
There are many different options to consider here as well. Do you want a
full Software-as-a-Service (SaaS) or Network-as-a-Service (NaaS) platform
where all deployment is taken care of by the service provider, or do you want
something more DIY and customizable? Most companies want a service
that reduces the burden on their IT teams so they can spend more time
monitoring for threats, and assisting end users.
The platform also supports the major single sign-on identity providers
including Google, Jumpcloud, Microsoft’s Azure Active Directory, Okta, and
OneLogin. There is also SCIM support for those with homegrown SSOs, and
SAML 2.0 for companies that use multiple providers.
Perimeter 81’s platform can help you meet compliance burdens for ISO 27001
and 27002, HIPAA, SOC 2 Type 2, and the GDPR.
Finally, the Perimeter 81 platform can build a network for your company
in minutes and have you up and running in just a few hours, depending on
company size.
There are also significant cost savings since a cloud-native solution helps
you do away with expensive appliances such as SD-Wan, VPN, and branch
office firewalls. The reduction of hardware also relieves your team of
significant maintenance time for urgent security patches, operating system
upgrades, and, in some cases, malware signature updates.
If there are other stakeholders that need to get onboard with your move to
cloud-native network security we suggest discussing Perimeter 81’s findings
with them. You can find more details in our latest State of Cybersecurity
Report.
It’s also a good idea to show what the day-to-day benefits will look like from
tools such as ZTNA (our ZTNA datasheet can help you there). Another option
is to show a scenario of what a potential breach would look like without a
cloud-native network security approach versus having one in place. Imagine
a hacker obtaining employee login credentials from a marketing employee,
for example, and how they wouldn’t be able to use that login to break into
the codebase or HR records–or gain access at all if location and time-of-day
contexts are used.
Contact Us
Perimeter 81 Ltd.
[email protected]
https://www.perimeter81.com
Request a Demo