Even as more businesses have begun requiring their employees to return to the office, there remains considerable anxiety and apprehension within the workforce. A recent Honeywell survey, aimed at assessing the global workforce’s sentiments on returning to the office, revealed 68% of them still do not feel completely safe about returning.
When the pandemic hit, many organizations responded to mandatory office closures and employee relocation by outfitting those who used desktop computers “on the network” with laptops and Chromebooks. The latter’s shipments have more than doubled year-over-year, and now many of these Chromebooks are returning to the office. The challenge is how to make them fit in with a Zero Trust model that assumes all users and devices are untrustworthy and must be authenticated.
Feeling lucky? Just 16% of organizations have reported no security incidents related to phishing or ransomware in the last year. Luck is not a security strategy, and it’s why the vast majority of companies are under attack. Too often, they’re not prepared with the proper security stack to block and stop these attacks. The result? Employees, data, and companies are at risk.
Nobody in transportation saw the disruption of 2020 coming, but it verified a few things that we all knew. As the trucking market reacted to extremely volatile freight demand, shippers were left plugging holes in routing guides built before the coronavirus hit newswires or store shelves. This flooded the spot market with goods that needed to move, and digital load boards and brokerage stepped in to meet that need in a big way.
Sometimes, it’s hard to admit that you’ve reached your limit and need to take a break, especially when working in a virtual environment. Maybe you frantically do more and more in an attempt to keep up, until a big mistake brings your efforts screeching to a halt. Or perhaps you stop only when you get sick. Or maybe you just give up.
Of the many complementary technologies that enable IoT (internet of things) deployments, there are none quite as critical as the distributed architecture commonly known as edge computing. Technically, edge computing and its concepts are nothing new. In the 1960s, the Apollo missions that brought humanity to the moon relied on a distributed network of mainframes (see Figure 1). One was located in Houston and powered the console displays in the Apollo Mission Control Center. The others were positioned at antenna sites in California, Spain, and Australia. Even in those early days of computing there was a need to position compute resources closer to the source of the data, which is, essentially, the definition of edge computing.