The Importance of Upgrading 

When thinking about keeping your network safe, upgrading networking hardware is often overlooked. It’s hard enough to get everything to play nicely together, and once it does, the last thing you want to do is disrupt that delicate balance. Plus, there’s a lot of planning, a lot of meetings, and probably a lot of money to spend. No wonder just the thought of upgrading infrastructure makes most admins want to run and hide.

Not upgrading, though, can put you at risk in a variety of ways.

EOL?  EOE?  EOS? SOL!

Nothing gold can stay, and that is as true for networking hardware as much as anything else.  As vendors develop new and exciting feature sets, old hardware gets strained more and more until, finally, it just can’t keep up.  You might not necessarily be interested in those new features – as long as the packets are flowing, who needs the latest and greatest?  And that makes sense – there’s a lot to be said for not being an early adopter.  As cool as cutting-edge innovation often sounds, it sometimes fails to deliver on its promises  (Look at the ill-fated Lily Drone, the Juicero Juicer, and the Cisco Umi – all products that showed great promise, but fell far short of expectations.)

We all understand how important it is to at least keep up with security updates, but products don’t get updates forever.  Watch out for these 3 phases of the product life cycle signify it’s time to get ready for replacements:

EOE: End of Engineering

No new features or fixes will be developed during this phase, although critical security fixes might still be released, and you can still get support….although the answer to most of your support questions will probably be “Upgrade.”

EOS: End of Support

There is no support and probably no security fixes (although if a critical vulnerability is uncovered, you might get a patch). For all intents and purposes, the product is dead. You might be able to get support assistance to upgrade, or they might help you if you run into an already-known bug.

EOL: End of Life

Stick a fork in it; it’s done – no support, no patches, no nothing.  For all intents and purposes, this product no longer exists.

Still Lurking Out There

Why does it matter if something still has vendor support?  Well, just because the vendor has seemingly forgotten about these devices does not mean hackers have.  Here’s an example:  In 2021, six years after Western Digital ended support for their My Drive line of external hard drives, a remote code execution bug resulted in many users losing all of their data.  The worst part is the vulnerability was reported to Western Digitial in 2018, a full three years before the bug was exploited, but since support for the drives had already ended Western Digital chose not to fix it.  

Sometimes those new features become default standards.  Devices in the late 90’s that shipped with 802.1a or 802.1b wireless networks were quickly rendered obsolete when a critical design flaw was found in  WEP.  Anyone not wanting a laughably easy to hack wireless password had to get completely new hardware.  Now all networking hardware ships with some form of WPA enabled.  

If you’re still not covinced, consider this: you could run afoul of the law if you use out-of-date hardware.  Many regulatory standards like GDPR, HIPAA, PCI DSS and more require organizations to take reasonable steps to protect sensitive information.  If you are the victim of a data breach, you will have a hard time justifying the use of old hardware.  It could also impact your certifications – if you maintain SOC 2 or ISO 27001, EOL hardware might put you out of compliance.   

Upgrading networking may not be the most exciting prospect, but as technology evolves and grows, it’s crucial to ensure you’re not falling behind. Proactive upgrades not only enhance your ability to stay secure, but they also keep you safe from regulatory and legal penalties in the case of a data breach.  Investing in the future by keeping your network infrastructure current will ensure you can support your organization’s goals for security, growth, and innovation going forward.  

Cybersecurity roles and responsibilities are in a constant state of flux. Just as the defenders adapt, so do the adversaries. Enter the latest evolution in the cybersecurity workforce: the Zero Trust Program Manager. If you’ve been in the cybersecurity field for more than a hot minute, you’re likely aware that “Zero Trust” has become a buzzword so pervasive that it’s now almost as ubiquitous as the phrase “we take your security seriously” in every corporate breach apology letter. But unlike the latter, Zero Trust is more than just lip service. It’s a paradigm shift in how we think about securing our digital environments. And it’s precisely this shift that has given rise to the need for a dedicated role to manage it.

What Exactly is a Zero Trust Program Manager?

At its core, the Zero Trust Program Manager (ZTPM) is the strategic leader responsible for implementing and overseeing an organization’s Zero Trust architecture. This role isn’t just about managing technology; it’s about orchestrating a cultural shift in how an organization approaches security. The ZTPM is tasked with ensuring that no entity—be it user, device, or application—is inherently trusted, whether inside or outside the organization’s perimeter. Instead, everything and everyone must be continuously authenticated and authorized.

This role is a blend of project management, cybersecurity expertise, and change management. The ZTPM must work closely with various stakeholders across the organization, from IT and security teams to business leaders, to ensure that the principles of Zero Trust are understood, embraced, and effectively implemented. They are the evangelist, the educator, and the enforcer of this new security mindset.

Why Does This Role Exist Today?

The rise of the ZTPM is not just a random blip on the cybersecurity radar; it’s a direct response to the changing threat landscape and the realization that traditional perimeter-based security models are no longer sufficient. The days when securing the castle walls could keep the bad guys out are long gone—primarily because the castle doesn’t even have walls anymore. Today, organizations operate in a borderless environment where users and data move fluidly across cloud services, mobile devices, and remote locations. The traditional model of “trust but verify” has been replaced with “never trust, always verify.”

Moreover, the acceleration of digital transformation, spurred on by global events like the COVID-19 pandemic, has further blurred the lines between internal and external networks. As organizations rapidly adopted remote work models and cloud services, the attack surface expanded exponentially. In this new reality, the concept of a trusted internal network is not just outdated; it’s downright dangerous.

Enter Zero Trust—a model that doesn’t assume that anything or anyone is trustworthy just because they’re inside the network. Every request, every access attempt, every interaction is scrutinized. This approach requires a fundamental shift in how security policies are designed, enforced, and managed. And that’s where the ZTPM comes in. Their role is to steer this transformation, ensuring that Zero Trust principles are not just a checkbox on a compliance form, but a living, breathing part of the organization’s security fabric.

Scope of Responsibilities

The responsibilities of a Zero Trust Program Manager are as wide-ranging as they are critical. Here’s a closer look at what this role entails:

1. Strategy Development and Implementation: The ZTPM is responsible for developing a comprehensive Zero Trust strategy that aligns with the organization’s business objectives. This includes defining the scope, setting milestones, and ensuring that all security policies and technologies are aligned with Zero Trust principles.
2. Cross-Functional Collaboration: Implementing Zero Trust is not a one-department job. The ZTPM must work closely with IT, security, compliance, and business units to ensure that the Zero Trust framework is understood and adopted across the organization. This includes leading workshops, training sessions, and regular check-ins to ensure alignment.
3. Technology Oversight: While the ZTPM isn’t necessarily the person configuring firewalls or deploying MFA solutions, they are responsible for overseeing the technology stack that supports the Zero Trust model. This includes evaluating and selecting the right tools, ensuring they are properly integrated, and monitoring their effectiveness.
4. Change Management: Moving to a Zero Trust model is as much about changing mindsets as it is about changing technology. The ZTPM must manage the human side of this transformation, addressing resistance, ensuring proper training, and fostering a culture that supports continuous verification.
5. Risk Management and Compliance: The ZTPM plays a crucial role in identifying and mitigating risks associated with the transition to Zero Trust. They must ensure that the organization remains compliant with relevant regulations and industry standards while adopting this new security model.
6. Continuous Improvement: Zero Trust is not a set-it-and-forget-it approach. The ZTPM is responsible for continuously assessing the effectiveness of the Zero Trust framework, making adjustments as needed, and staying ahead of emerging threats.

Qualifications and Skills

Given the breadth of responsibilities, the ideal ZTPM is a cybersecurity Renaissance person—a Jack or Jill of many trades, with a deep understanding of security principles and a knack for project management. Key qualifications might include:

• Experience: A strong background in cybersecurity, with experience in implementing security frameworks and leading cross-functional teams.
• Certifications: Relevant certifications such as CISSP, CISM, or specific Zero Trust certifications can be a strong indicator of expertise.
• Communication Skills: The ability to articulate complex security concepts to non-technical stakeholders is crucial.
• Leadership: Proven leadership skills, particularly in driving organizational change, are essential.
• Strategic Thinking: The ZTPM must be able to see the big picture, aligning security initiatives with broader business goals.

Zero Trust, the ZTPM & Network Access Control (NAC)

One of the critical areas where the Zero Trust Program Manager (ZTPM) must exert influence is in the realm of Network Access Control (NAC). NAC plays a pivotal role in the enforcement of Zero Trust principles, acting as one of the frontline defenses against unauthorized access. In the context of Zero Trust, NAC is not merely a gatekeeper that decides who gets in; it is a dynamic system that continuously assesses and verifies the trustworthiness of every device and user attempting to access the network.

The ZTPM must work closely with network administrators and security teams to ensure that NAC solutions are tightly integrated into the broader Zero Trust architecture. This involves configuring NAC policies to align with the Zero Trust mantra of “never trust, always verify.” For example, NAC policies may need to be updated to enforce strict access controls based on user roles, device health, and contextual factors such as the location and behavior of the device. The ZTPM oversees this integration, ensuring that the NAC system not only blocks unauthorized devices but also actively participates in the continuous monitoring and assessment of devices already within the network.

Furthermore, the ZTPM must consider how NAC fits into the overall user experience. While security is paramount, the role requires balancing stringent access controls with the need for operational efficiency. Implementing NAC in a Zero Trust environment is not just about adding layers of security; it’s about creating an adaptive, intelligent system that can respond to threats in real-time without unnecessarily hindering legitimate business activities. This means the ZTPM must ensure that NAC is fine-tuned to minimize disruptions while still providing robust protection, making it an essential tool in the Zero Trust toolkit.

By effectively managing NAC within a Zero Trust framework, the ZTPM helps to create a more resilient and responsive security posture, one where access is always under scrutiny and never taken for granted.