> 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/vol.-2-reference-architecture.md).
# Vol. 2: Reference Architecture
The TIC reference architecture provides guidance to system administrators when defining the scope and process for how to implement TIC. It's basically a framework for how to bucket different aspects of the program. These buckets are then managed, security-wise, in [Vol 3: Security Capabilities](/regulatory-framework-mappings/dhs-tic/vol.-3-security-capabilities.md).
{% hint style="success" %}
You can get the original Volume 2 [here](https://www.cisa.gov/sites/default/files/publications/Draft%20TIC%203.0%20Vol.%202%20Reference%20Architecture.pdf).
{% endhint %}
{% hint style="info" %}
If you're looking for the exact security sections Dispel covers, go over to our [Security Capabilities guide](/regulatory-framework-mappings/dhs-tic/vol.-3-security-capabilities.md).
{% endhint %}
## What does the framework care about?
There are seven goals of the TIC program, and these provide the base structure for the reference architecture. The goals are:
#### **Boundary-focused**
TIC 3.0 divides agency architectures by trust zones, shifting the emphasis from a strictly physical network perimeter to the boundaries of each zone within an agency environment to ensure baseline security protections across dispersed network environments.
#### Descriptive, not prescriptive
The updated reference architecture, taxonomy, capabilities, and use cases will broaden the concepts of the program to accommodate cloud, mobile, and encrypted applications, services and environments.
#### Risk-based to accommodate varying risk tolerances
Federal agencies have varying degrees of risk tolerances that must be considered as IT modernization tasks are planned and executed. In some cases, the controls identified in the TIC 3.0 documentation may not provide enough security to adequately address residual risks necessary to protect information and systems.
#### Environment-agnostic
The terms, definitions, and logical components of network infrastructure and solutions are vendor and technology-neutral. Additionally, the modernized TIC provides flexibility on the application of the security capabilities to accommodate a variety of agency environments.
#### Dynamic and readily adaptable
To keep pace with technological innovation, the TIC Program Management Office (PMO) will continue to produce and update use cases and overlays through collaboration with agencies and service providers to maintain currency.
#### Automated and streamlined verification
The program’s goal is to define scalable, comprehensive and continuous validation processes for ensuring agency implementation of TIC capabilities in contrast to the point-in-time reviews.
#### Delineate the NCPS and TIC initiatives
CISA continues to provide these security capabilities in accordance with the *Federal Cybersecurity Enhancement Act of 2015* to protect “all information traveling between an agency information system and any information system other than an agency information system.” The NCPS EINSTEIN and TIC initiatives will continue to support and complement each other in support of this legislation. The NCPS PMO and TIC PMO will independently provide guidance for their respective initiatives.
{% hint style="info" %}
"NCPS" is the National Cybersecurity Program System--an set of systems protecting U.S. Federal Government IT infrastructure. The web is called EINSTEIN. You can learn more about the program [here](https://www.cisa.gov/national-cybersecurity-protection-system-ncps).
{% endhint %}
## Security Objectives of TIC 3.0
| Objective | Description |
| ------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
| Manage Traffic | Observe, validate, and filter data connections to align with authorized activities; least privilege and default deny |
| Protect Traffic Confidentiality | Ensure only authorized parties can discern the contents of data in transit; sender and receiver identification and enforcement |
| Protect Traffic Integrity | Prevent alteration of data in transit; detect altered data in transit |
| Ensure System Resiliency | Promote resilient application and security services for continuous operation as the technology and threat landscape evolve |
| Ensure Effective Response | Promote timely reaction and adapt future response to discovered threats; policies defined and implemented; simplified adoption of new countermeasures |
## Key Concepts of TIC 3.0
* Trust Zones
* Policy Enforcement Points (PEPs)
* Management Entities (MGMT), and
* Security Capabilities.
---
# 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/vol.-2-reference-architecture.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.