Recent security breaches via software have made supply chain security a priority across government. No longer is it enough to build security into a solution; now every product that is part of that solution is being examined for its security and risk. In response, the Biden Administration issued a Cybersecurity Executive Order that aims to provide more control over the content of code that comes in contact with government systems and infrastructure.
With so many high-profile hacks this year, it's easy to want to throw up your hands and say, "Is there nothing that can be trusted?!" Interestingly, that lament is what is driving the latest approach to cybersecurity -- zero trust. Zero trust is what it sounds like, a security approach centered on the belief that organizations should not automatically trust anything accessing their systems either inside or outside their perimeters. Instead, all people and devices must be verified before access is granted. To the untrained eye, this seems untenable. How, in this day and age, when we depend on digital information and connection to do most anything, can we use a process where we have to constantly verify identity and access permissions? Luckily, the practice of zero trust is more sophisticated than its premise.
The last year has brought about incredible change in the federal workforce, and it shows no sign of stopping. With a new Director for the Office of Personnel and Management (OPM) confirmed, the next several months will bring new energy and activity to formalizing and standardizing workplace policies, processes, and approaches for the "new normal" of a digital-first government.
The move to telework changed how many people view and even perform their jobs. Before the pandemic, telework was sporadically used throughout government and viewed pretty skeptically. Now that the genie is out of the bottle, it's clear that government can continue to function without people in office buildings from 9am-5pm. As in-person work starts to come back around, the new shift will be in defining and managing a hybrid workforce.
Shared Services in government is nothing new. The idea began in the 1980s with the consolidation of payroll and some other administrative functions. In the '90s the focus was on creating entities that could provide common business functions across government and, in that effort, become a cost center.
The 2000s saw the rise of the term 'Line of Business' that looked at common business functions across government to identify opportunities to transform, streamline and share. The Obama Administration looked specifically to IT as a shared service, releasing the Federal IT Shared Services Strategy that provided federal agency chief information officers and key stakeholders guidance. This guidance focused on the implementation of shared IT services as a key principle of their efforts to eliminate waste and duplication, with the intention to reinvest in innovative mission systems.
Remote Management
Stay-at-home orders, social distancing measures, and backlogged inspection schedules all combine to make a great case for implementing sensors and other IoT devices as part of infrastructure management. With technology providing data on the status of equipment, facilities, and general infrastructure like roads and bridges, the need to deploy inspectors to the field can be minimized. In the short term, this reduces potential points of exposure for inspectors and field staff. Longer term, it adds a new "colleague" to field management teams. IoT can handle routine, low risk monitoring, freeing up humans to focus on more complex or higher priority tasks and activities.
