> For the complete documentation index, see [llms.txt](https://docs.dispel.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dispel.com/regulatory-framework-mappings/dhs-tic/overview.md). # Overview ## What is the TIC? ![](https://2668873066-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LqlTpechIfonX0FqSV8%2F-MXhUlS6OCplJSCyzXJ5%2F-MXhUs5lyjOPjK2WIlg0%2FDHS%20TIC.jpg?alt=media\&token=7691ffe7-5c77-4131-88ed-9b785711fba5) {% hint style="info" %} You can find the source TIC documents here: {% endhint %} The Trusted Internet Connections (TIC) initiative, since its establishment in 2007, has moved the government from a period of uncontrolled and unmonitored internet connections to a controlled state, reducing the .gov’s attack surface. In accordance with the Office of Management and Budget (OMB) [Memorandum (M) 19-26](https://www.whitehouse.gov/wp-content/uploads/2019/09/M-19-26.pdf): *Update to the TIC Initiative*, TIC 3.0 expands on the original initiative to drive security standards and leverage advances in technology to secure a wide spectrum of agency network architectures. This new version of TIC is highly iterative, which means the guidance will better reflect modern processes and technological innovations compared to previous iterations of the program. TIC 3.0 recognizes shifts in modern cybersecurity and pushes agencies toward adoption, while recognizing their challenges and constraints in modernizing IT infrastructure. The purpose of the Trusted Internet Connections (TIC) initiative, as outlined in the Office of Management and Budget (OMB) [Memorandum M-19-26](https://www.whitehouse.gov/wp-content/uploads/2019/09/M-19-26.pdf): Update to the TIC Initiative, was to enhance network and perimeter security across the Federal Government. Initially, this was done through the consolidation of external connections and the deployment of common tools at these access points. While this prior work has been invaluable in securing federal networks and information, the program must adapt to modern architectures and frameworks for government information technology (IT) resource utilization. Accordingly, OMB’s memorandum provides an enhanced approach for implementing the TIC initiative that provides agencies with increased flexibility to use modern security capabilities. OMB’s memorandum also establishes a process for ensuring the TIC initiative is agile and responsive to advancements in technology and rapidly evolving threats. ## Where are we today in the process? (A: TIC 3.0) ### **2021: TIC 3.0 – Modernize** On April 7, 2021, CISA released finalized versions of the [TIC 3.0 Traditional TIC Use Case](https://www.cisa.gov/publication/tic-30-core-guidance-documents) and [T](https://www.cisa.gov/publication/national-cybersecurity-and-protection-system-documents)[IC 3.0 Branch Office Use Case](https://www.cisa.gov/publication/tic-30-core-guidance-documents). The documents are the first official TIC use cases approved by the Federal Chief Information Security Officer (CISO) Council for TIC 3.0. Beginning in 2011, the Federal Government made strides toward migration into the cloud with the Cloud First Initiative, now known as Cloud Smart, moving its systems and data away from federally owned and operated networks. During this migration, impediments surfaced throughout implementation, including security challenges. To better serve its citizens, the Federal Government made a concerted push to leverage technological advancements in a secure manner. As a reaction to Executive Order (EO) 13800, Strengthening the 5 Cybersecurity of Federal Networks and Critical Infrastructure, OMB, DHS, and GSA developed a report outlining the information technology (IT) modernization needs for the Federal Government. The 2017 Report to the President on Federal IT Modernization (IT Modernization Report) 6 addresses agencies’ challenges with resource prioritization, ability to procure services quickly, and technical issues by focusing on: * Network Modernization and Consolidation * Shared Services to Enable Future Network Architectures *IT Modernization Report* calls for the modernization of TIC to improve protections, remove barriers, and enable cloud migration, marking the start of the 2019 TIC policy update. The report tasks the TIC initiative to: * Establish TIC pilots to understand new environments, * Update TIC Policy and associated material, * Accommodate the security needs of dispersed architectures, and * Eliminate manual TIC Compliance Validation (TCV) Process. To address these modernization tasks, OMB, CISA, and GSA facilitated four interagency working groups and oversaw pilots to collect data used to inform the TIC policy update and reference architectures. TIC 3.0 is a response to the need for improved flexibility, security, and visibility. The program is intended to be forward-leaning and environment-agnostic. TIC 3.0 broadens the concepts of the program to accommodate cloud, mobile, and encrypted applications, services and environments. The program envisions a flexible perimeter that may protect diverse hosting environments, platforms and services in contrast to the hard enterprise perimeter as previously implemented. While the NCPS and TIC initiatives continue to support and complement each other, the initiatives are evolving independently. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.dispel.com/regulatory-framework-mappings/dhs-tic/overview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.