Government Business
Article | March 11, 2022
The COVID-19 pandemic touches every aspect of business, technology, and society. And stable and effective government is at the heart of managing through this crisis. What we do now will have longer-term implications for the health and safety of our families, our citizens, the economy, and even global stability. In the past few weeks, IBM has collaborated with many of our government clients and is driving action across three critical phases of response.
Read More
Cybersecurity
Article | March 23, 2022
It can be challenging to connect government services to Californians who need them most. With a population of nearly 40 million people, the state’s residents have a wide range of experiences, abilities, education, and technical literacy. The California Design System is a collaborative effort between the California Department of Technology and the Office of Digital Innovation to help web developers and designers address common needs to make digital information and services easier to use.
The Design System is an open source project and is in early beta status. Currently in use on websites for the Department of Cannabis Control, California Drought Action, California’s COVID-19 website, and the Broadband for All portal, we invite collaboration and feedback so we can incorporate new design system components into the existing state template.
The California Design System will help build websites and products that put people first and also look great. Whether you’re an individual developer, product owner, web designer or a public employee, we invite you to get involved and help us make improvements. Reach out to the Design System team through our contact form on the home page, or work through the GitHub repository.
This collaborative effort is another example of how state government is innovating to improve state websites and better serve the people of California.
Read More
Government Business
Article | July 14, 2022
The House of Representatives laid out an infrastructure plan on June 18 – an expensive one with a price tag of approximately $1.5 trillion. It will not, of course, pass Congress in its current state, but it promises to start the critical and overdue conversation in Washington about infrastructure.
But, there’s an omission that hopefully will be addressed and debated in Congress. The new plan makes little mention of funding for America’s outdated public technology infrastructure. Yet, the nation’s technology is a critical component of its infrastructure.
Some leaders hope to make Congress aware of the challenges public officials face as they try to manage with old legacy technology systems that should have been replaced a decade ago. Broadband will likely be addressed, but all kinds of other technology assets need attention as well.
When taxpayers think about what infrastructure should include, there is not a consensus. Roads and bridges are certainly considered as public assets and will be included in every discussion of infrastructure. Water, power, schools, health care, and even the Postal Service are named in the new plan that passed the House of Representatives. But, the new bill, which is called the Moving Forward Act, does not mention government’s basic technology infrastructure.
One definition of infrastructure is “the basic physical and organizational structures and facilities needed for the operation of a society or enterprise.” Surely, technology falls into that category.
There’s no argument that America’s global economic future depends on its technology infrastructure as well as its transportation infrastructure.
But, public officials in governmental entities throughout the country attempt to provide services on old legacy systems that are decades past replacement stages. Public databases and networks are vulnerable to cyberattacks. The technology found in cities, counties, school districts, and governmental agencies is more than old and inadequate it is simply unreliable and in some instances could be considered dangerous.
In a world of ‘big data’, artificial intelligence, cloud computing, apps, the Internet of Things (IoT), and extreme security requirements, government technology assets lag too far behind in America.
Public officials don’t have funding to replace the antiquated technology systems. As Congress debates infrastructure reform, technology should be a part of the conversation.
Those in agreement that the national debt does not need another $1.5 trillion hit may advocate for ways to encourage private sector funding for the many needs of infrastructure. Collaborative initiatives could be structured in the final infrastructure bill so that there are incentives for alternative funding and private sector expertise, as well as guidelines to protect taxpayers and public agencies.
The inclusion of technology needs in any infrastructure discussion is, at the very least, worthy of discussion.
Mary Scott Nabers is president and CEO of Strategic Partnerships Inc., a business development company specializing in government contracting and procurement consulting throughout the U.S. Her recently released book, Inside the Infrastructure Revolution: A Roadmap for Building America, is a handbook for contractors, investors and the public at large seeking to explore how public-private partnerships or joint ventures can help finance their infrastructure projects.
Read More
Cybersecurity
Article | March 23, 2022
“Belonging to the essential nature of a thing; originating and included wholly within an organ or part.” That is the definition of “Intrinsic.” When we were developing the “IT Manhattan Project” framework, we were doing so in direct response to some of the most significant hacks in U.S. Federal history, which piled on to the already unprecedented push to expedite the modernizing of federal IT because of the COVID-19 response. The COVID-19 response shifted the way that the U.S. federal government operated, where our workforce worked from, the immediate need for mobile ‘available from anywhere’ workloads, and how to both secure and support that new way of doing federal business. A new, vigorous push towards rapidly modernizing federal IT environments was underway. Ultimately, it laid the groundwork for producing transformational federal memos and oversight by way of some of the following:
Executive Order 14028: “Improving The Nation’s Cybersecurity”
M-22-09: OMB’s Zero Trust Strategy M-22-09
NIST 800-53rev5: Fulfilling an expedited realization of the overall intent of NIST 800-53r5 through the emphasis on things like conditional access, TIC 3.0 frameworks, Secure Orchestration/Automation/Remediation, and modernized, agile approaches to secure micro-segmentation from Hybrid Environments up to Federal Cloud instances
Overall mandates like these carry with them a consistent anthem driving at rapid IT modernization with rigorous proof of performance schedules attached. Piling on top of those Herculean efforts, the urgency was drastically increased by several of the highest profile cyber compromises in U.S. federal history. Rapid modernization had to happen right away. The time for IT transformation was here, backed by promises of significant funding and a high level of political visibility.
The Shift to Zero Trust
At their core intent, Zero Trust architectures are expected to provide a centralized policy structure that dictates how every individual flow in our IT environments are permitted to talk. No user, host, or flow is permitted without being subjected to rigorous authentication and authorization policy. This shifts our previous understanding of North-South, East-West traffic and how we police it. The foundational intent of Zero Trust architectures centers around applying unified policy to every transaction that occurs between enterprise resources, and doing so in ways that are agnostic to the IT Silo that they reside in.
Zero Trust assumes there is no implicit trust granted to assets or user accounts based solely on their physical or network location.”
NIST 800-207 aptly
They go on to explain that the scope of this posture includes all assets, workflows, network accounts, and the like. In summary, police everything, abstract production traffic intent from the underlying infrastructure that supports it, and institute a unified security posture to execute the policing at every network entry point. Regardless of the domain. We all know that this is a tectonic but much-needed shift in our industry. I’d go so far as to say that the successful instantiation of this approach across Federal IT environments is critical to our national security going forward.
Management Complexities
Enterprise IT domains contain varied mixtures of OEM solutions, home-grown tools, and utilize a wide variety of protocols to intercommunicate that aren’t necessarily standardize. Each of these domains is normally managed by separate IT teams who specialize in maintaining those environments. In the federal landscape, each of these domains aren’t just managed by separate enterprise IT teams, but are commonly managed by different contractors. Therefore, IT security organizations have a difficult time achieving and maintaining the necessary operational awareness required to enforce centralized policy. These cultural complexities exacerbated by budgeting concerns have created a fatalistic mentality when it comes to far-reaching mandates. This is where the tectonic shift in architectural and administrative approach is so necessary. This is where multidomain architectures shine.
Let’s define a common baseline of enterprise domains seen across traditional IT environments:
Cloud
Data Center
Enterprise Networking
Extended Enterprise (IoT, OT/ICS)
Remote Access
But to deliver a successful Zero Trust across the enterprise, it is first necessary to understand some foundational building blocks on which to construct our architectural approach:
We can’t have MULTIDOMAIN POLICY without first achieving fuller
We can’t deliver macro and micro-segmentation without first having robust MULTIDOMAIN
We can’t have multi-vendor MULTIDOMAIN Zero Trust POLICY without sensical INTEGRATIONS to stitch each enterprise domain together.
Let’s face it, enterprise IT environments don’t simply include infrastructure from a single manufacturer, or even a few key manufacturers. Rather, our Enterprise IT environments are represented by a plethora of IT manufacturers specializing in different niches of IT and the domains they are commonly found in. These environments are managed by different Federal IT organizations, different contractors who support these Federal IT organizations, and many different teams that support each common IT silo. Different teams that support oft-compartmentalized areas like Network Security Operations, Network Operations, Data Center Operations, Institutional Services, Wide Area Networking contracts, Operational Technologies, and dotted lines to different leadership oversight like CIO Programs, CTO Architecture, the Cyber Security Office, and the audit oversight bodies that they are subjected to. Each of these make up a complex support structure that isn’t necessarily streamlined for efficiency.
Summary and Overarching Goals
In articles to follow, you’ll see us referencing the IT Manhattan Project framework several times. Though many details of the framework can’t be discussed due to their sensitivity, the foundational principles are relevant across the board when pursuing intrinsic multidomain Zero Trust.
Establish Visibility (Administration, Telemetry, Assurance)
Define Straightforward Policy Structure and Hierarchy (Auth Chains)
Perform Multidomain Integrations (API Integrations)
Deploy Software-Defined Framework (Day-0, Programmable Fabrics, Multi-OEM Fabric Integrations)
Establish Sensical Automation Runbooks (Day-2 Operations)
We will also explore some areas that deliver unexpected value to the agency business in immediate ways. All of this will help create a cohesive story that helps CIOs, CISOs, and enterprise architects alike communicate the criticality of this multidomain Zero Trust approach to agency leaders across the federal spectrum.
Read More