Cybercrime on local and state governments is continuing to rise, as cybercriminals understand the government possesses lots of data and information that are vital and highly classified. The risks to these federal IT systems are increasing, with insider threats from witting or unwitting employees, escalating threats from around the globe, and the emergence of new more destructive attacks. The U.S. Government Accountability Office reports that over 35,000 security incidents were reported by federal executive branch civilian agencies to the Department of Homeland Security in fiscal year 2017.
In response, the government has adopted a Zero Trust (ZT) strategy, which shifts focus toward individual access and away from protecting wide segments of the network, away from a perimeter-based only cybersecurity approach. As we reviewed in our previous blog, “Building A Zero Trust Visibility Architecture,” a few main architecture concepts, including ZT Network Requirements, ZT Framework, and ZT Visibility fabric. Here we will introduce how to implement a regular cycle of monitoring, maintenance and updating.
The key concept in a Zero Trust cybersecurity strategy is that organizations need to proactively control all interactions between people, data, and information systems to reduce security risks to acceptable levels. If agencies properly adopt Zero Trust, they have the potential to substantially change and improve their ability to protect their systems and data.
Agencies are expected to modernize their aging cybersecurity architectures to address new threats and service requirements, despite budget challenges and overtaxed workforces.
A recent assessment of ZT technologies by ACT-IAC and the Federal CIO Council concluded that modern IT security solutions need to incorporate several minimum characteristics:
With all of the new regulations and standards guiding the transition to Zero Trust, we get that it can be overwhelming for IT leaders tasked with upgrading highly complex government networks. And while this isn’t a transition that will happen overnight, it’s not as if you need to completely rip and replace your existing security infrastructure to implement Zero Trust.
When considering your Zero Trust strategy, these five steps can help simplify your implementation:
Implementing a Zero Trust model will be an incremental process for your governmental agency. A Zero Trust Architecture requires organizations to have detailed knowledge of its assets (physical and virtual), users, and business processes, which includes a survey of assets, users, data flows, and workflows.
Once this foundation information is documented, a regular cycle of monitoring, maintenance and updating is implemented. This final step is all about taking advantage of visibility tools to support continuous monitoring of the Zero Trust Architecture so you can maintain effectiveness as needs evolve.
Bypass TAPs play an important role in this step of Zero Trust maintenance and updating. Their inline lifecycle management capabilities make it easy to take inline tools out-of-band for updates, install patches, conduct troubleshooting tasks, and sandbox/optimize/validate the tools before pushing them back inline, without taking the network down.
It is critical to build a Zero Trust Architecture that allows you to monitor and maintain your Zero Trust environment, by guaranteeing total network visibility that meets the highest government cybersecurity maturity levels.
Garland Technology is here to help you succeed on the path to Zero Trust. Our full portfolio of network TAPs, network packet brokers, bypass technology, and cloud visibility solutions will simplify your cybersecurity upgrades. Set a free Design-IT meeting with one of our network engineers for a no obligation, Visio network design session.
If the inline security tool goes off-line, the TAP will bypass the tool and automatically keep the link flowing. The Bypass TAP does this by sending heartbeat packets to the inline security tool. As long as the inline security tool is on-line, the heartbeat packets will be returned to the TAP, and the link traffic will continue to flow through the inline security tool.
If the heartbeat packets are not returned to the TAP (indicating that the inline security tool has gone off-line), the TAP will automatically 'bypass' the inline security tool and keep the link traffic flowing. The TAP also removes the heartbeat packets before sending the network traffic back onto the critical link.
While the TAP is in bypass mode, it continues to send heartbeat packets out to the inline security tool so that once the tool is back on-line, it will begin returning the heartbeat packets back to the TAP indicating that the tool is ready to go back to work. The TAP will then direct the network traffic back through the inline security tool along with the heartbeat packets placing the tool back inline.
Some of you may have noticed a flaw in the logic behind this solution! You say, “What if the TAP should fail because it is also in-line? Then the link will also fail!” The TAP would now be considered a point of failure. That is a good catch – but in our blog on Bypass vs. Failsafe, I explained that if a TAP were to fail or lose power, it must provide failsafe protection to the link it is attached to. So our network TAP will go into Failsafe mode keeping the link flowing.
Single point of failure: a risk to an IT network if one part of the system brings down a larger part of the entire system.
Heartbeat packet: a soft detection technology that monitors the health of inline appliances. Read the heartbeat packet blog here.
Critical link: the connection between two or more network devices or appliances that if the connection fails then the network is disrupted.