- ClassificationCategoryCybersecurityDomainCybersecurityFramework FamilyOther
- Regulatory ContextTypeArchitecture / Technical ModelLegal InstrumentGuidanceSectorGovernment SectorIndustryGovernment & Public Sector
- Region / PublisherRegionNorth AmericaRegion DetailUnited StatesPublisherCybersecurity and Infrastructure Security Agency (CISA), under OMB Memorandum M-19-26
- VersioningVersionTIC 3.0 Core Guidance (Program Guidebook v1.2, July 2025; Security Capabilities Catalog v3.2, December 2024; Cloud Use Case v1.0, April 2023)Effective DateSeptember 12, 2019 (OMB M-19-26); core guidance v1.0 July 2020Issue DateJuly 2020 (core guidance v1.0); M-19-26 issued September 12, 2019
- AdoptionAdoption ModelRegulatory ComplianceImplementation ComplexityHigh
- Official ReferenceOpen Link in New TabSource
License included / downloadable: Yes
The TIC 3.0 core guidance, use cases and catalog are published free by CISA as TLP:CLEAR documents on cisa.gov, and OMB M-19-26 is a public memorandum on whitehouse.gov; the platform links to the official texts.
Framework text is licensed by its publisher and is included only where stated above.
- TIC 3.0 is the federal civilian network security initiative directed by OMB Memorandum M-19-26 (September 12, 2019) and documented by CISA.
- M-19-26 rescinded the memoranda that required agency traffic to flow through a physical TIC access point.
- The core guidance has five volumes, including the Security Capabilities Catalog (version 3.2, December 2024, mapped to NIST CSF 2.0).
- Four use cases cover Traditional TIC, Branch Office, Remote User, and Cloud (version 1.0, April 2023).
- Agencies divide their architecture into trust zones and place policy enforcement points close to the data and systems they protect.
Overview
Trusted Internet Connections (TIC) 3.0 is the network security initiative for U.S. federal civilian agencies that OMB Memorandum M-19-26 (September 12, 2019) directed and that the Cybersecurity and Infrastructure Security Agency (CISA) documents in the TIC 3.0 Core Guidance. M-19-26 rescinded M-08-05 (November 20, 2007), M-08-16, M-08-27 and M-09-32, the memoranda that had required agency traffic to flow through a physical TIC access point, and gave agencies one year to update their network and system boundary policies and to identify which TIC use cases they allow (section E).
CISA released the core guidance as version 1.0 in July 2020 after a December 2019 draft. It is five additive volumes: the Program Guidebook (Volume 1, now version 1.2 of July 2025), the Reference Architecture (Volume 2), the Security Capabilities Catalog (Volume 3, version 3.2 of December 2024, mapped to NIST CSF 2.0), the Use Case Handbook (Volume 4) and the Overlay Handbook (Volume 5), plus four use cases: Traditional TIC, Branch Office, Remote User and Cloud (version 1.0, April 2023), the last of the initial common use cases that M-19-26 Appendix A listed. CISA's program page records November 26, 2024 as the latest update, made to the catalog; the September 2026 refresh of the core documents was administrative, with no technical changes.
An agency implements TIC 3.0 by dividing its architecture into trust zones, placing policy enforcement points (PEPs) where its chosen use cases call for them, applying the universal and PEP security capabilities from the catalog at a rigor matched to each zone's trust, adding compensating controls where residual risk remains, sending telemetry to CISA and keeping the inventory of network connections that M-19-26 requires. OMB and CISA track implementation through FISMA reporting.
Why does it matter?
From 2007 until M-19-26, the TIC initiative required an agency's internet traffic to pass through a small number of physical TIC access points, which the memorandum called an obstacle to the adoption of cloud-based infrastructure. TIC 3.0 moves the perimeter: security capabilities sit at multiple policy enforcement points close to the data, applications and systems they protect (Guidebook section 6), and each agency selects use cases and rigor according to its own risk tolerance. Responsibility for compliance with TIC capabilities shifts to the agency (Guidebook section 9): the manual TIC Compliance Validation reviews end, agencies must apply compensating controls where the catalog does not cover residual risk, and OMB and CISA follow adoption through FISMA reporting (M-19-26 section E).
Key benefits include:
- Cloud and remote access without a backhaul
M-19-26 section C lets traffic bypass a TICAP or MTIPS access point when the alternative controls in a TIC use case are in place, which removed the policy barrier to IaaS, SaaS, PaaS and remote-user architectures.
- One vocabulary for architectures
Trust zones, policy enforcement points, security patterns, use cases and overlays (Guidebook section 6.1) give agencies, CISA and vendors a common way to describe and compare a network design.
- Rigor set by risk, not by a fixed list
The catalog dropped the Critical/Recommended prioritization of TIC 2.x; agencies decide the level of each capability per trust zone and document the residual risk they accept (Guidebook sections 4 and 6.1).
- A catalog already mapped to NIST
Every capability in the Security Capabilities Catalog carries NIST Cybersecurity Framework category mappings, updated to CSF 2.0 in version 3.2, so TIC evidence reuses the agency's CSF and SP 800-53 work.
- Vendor overlays for procurement
The Overlay Handbook (Volume 5) lets vendors and agencies map products and services to TIC capabilities; agencies use overlays to assess vendors, decide procurements and find capability gaps (Guidebook section 7).
How does it work?
M-19-26 assigns the roles. OMB sets policy; DHS, through CISA, defines TIC requirements in use cases (section C) and runs the process with OMB, GSA and the Federal CISO Council that pilots, approves and updates them (section D); within 90 days of each use case CISA, GSA and NIST develop a compliance verification process, and GSA updates procurement vehicles within six months of new requirements. Section E makes agency CIOs keep an inventory of every network connection with its provider, cost, capacity, traffic volume, configuration and topology. Appendix A lists the initial use cases: Traditional TIC (the default), Cloud (IaaS, SaaS, Email as a Service and PaaS), Agency Branch Office and Remote Users on government furnished equipment.
The Program Guidebook turns the memorandum into concepts. Section 5 sets five security objectives: Manage Traffic, Protect Traffic Confidentiality, Protect Traffic Integrity, Ensure Service Resiliency and Ensure Effective Response, applied at a level commensurate with the resources protected and mapped to the six NIST CSF 2.0 Functions. Appendix C defines the terms: a trust zone is a discrete computing environment; a policy enforcement point is the device, tool, function or application that enforces security policies; a security pattern is an end-to-end data flow between two trust zones; a use case holds a conceptual architecture, security patterns, applicable capabilities and telemetry requirements; an overlay maps products and services to capabilities.
The Security Capabilities Catalog is the control index. Universal security capabilities are enterprise-level and expected in every use case: backup and recovery, central log management, configuration management, incident response, inventory, least privilege, strong authentication and patch management among them, plus the five added in version 3.0 (April 2023): supply chain risk management, resource lifecycle management, security test and exercise, continuous monitoring reporting and governance and policy auditing (section 4.1). PEP security capabilities are network-level and grouped into Files, Email, Web, Networking, Resiliency, DNS, Intrusion Detection, Enterprise, Unified Communications and Collaboration, Data Protection, Services and Identity (section 4.2); each use case states which apply. Telemetry to CISA is a separate duty the catalog does not define (Guidebook section 10).
Key Elements
- OMB Memorandum M-19-26 (September 12, 2019)
The policy foundation: rescinds the 2007 to 2009 TIC memoranda, defines requirements through use cases, sets the pilot and approval process and the one-year deadline for agency boundary policies.
- Five security objectives (Guidebook section 5)
Manage Traffic; Protect Traffic Confidentiality; Protect Traffic Integrity; Ensure Service Resiliency; Ensure Effective Response, where traffic means data in transit between trust zones or stored at either.
- Trust zones and policy enforcement points
Agencies tailor capabilities to the trust of each zone; capabilities are deployed at multiple PEPs instead of only at a TIC access point (Guidebook section 6.1; Reference Architecture, Volume 2).
- Security Capabilities Catalog (Volume 3, v3.2)
Universal capabilities with 3.UNI identifiers and PEP capabilities with 3.PEP identifiers in twelve functional groups, each mapped to NIST CSF categories; v3.2 of December 2024 remapped them to CSF 2.0.
- Use cases and the Use Case Handbook (Volume 4)
Traditional TIC, Branch Office, Remote User and Cloud: each gives a conceptual architecture, security patterns, applicable capabilities and telemetry requirements, and agencies may combine them.
- Overlays and telemetry (Volume 5; Guidebook section 10)
Vendors and agencies map products to capabilities in overlays; agencies continue to provide telemetry to CISA and should check FedRAMP authorization of the vendors they rely on (Guidebook section 9).
What does it cover?
TIC 3.0 applies to federal civilian executive branch agencies, the addressees of M-19-26, and to the service providers that host federal systems and information for them. It covers network traffic between trust zones and data stored in them across the four use cases: TIC access points under Traditional TIC, IaaS, PaaS, SaaS and Email-as-a-Service under Cloud, branch offices connecting through headquarters or SD-WAN, and remote users on government furnished equipment. Vendors take part through overlays. TIC 3.0 does not replace FedRAMP authorization of a cloud service, the agency's own assessment and authorization, or the telemetry duties that 6 U.S.C. 663 and CISA programs impose (Guidebook sections 9 and 10, Appendix A).
What are its objectives?
The Program Guidebook states the security objectives in section 5 and the Security Capabilities Catalog repeats them in section 3; they stand independently and are not an order of operations.
Manage Traffic: observe, validate and filter data connections to align with authorized activities, with least privilege and default deny.
Protect Traffic Confidentiality: ensure only authorized parties can discern the contents of data in transit, with sender and receiver identification and enforcement.
Protect Traffic Integrity: prevent alteration of data in transit and detect altered data in transit.
Ensure Service 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, with policies defined and implemented and simplified adoption of new countermeasures.
Framework in Context
TIC 3.0 sits among the programs the Program Guidebook names in section 13: FedRAMP, whose authorizations agencies check before relying on a vendor's TIC capabilities; NIST SP 800-207 zero trust architecture, which TIC supports by letting an agency set the trust of each zone independently, even all zones as low trust; the CDM program, whose tools implement trust zones and PEPs; EINSTEIN and the Comprehensive Log Aggregation Warehouse for cloud telemetry; the High Value Asset program; and GSA's EIS contract. CISA's complementary guidance adds IPv6 Considerations for TIC 3.0, the Cloud Security Technical Reference Architecture and the Zero Trust Maturity Model. The authorities are NSPD-54/HSPD-23, the Federal Cybersecurity Enhancement Act of 2015 (6 U.S.C. 663) and FISMA (Pub. L. 113-283).
Common Framework Mappings
Agencies map TIC 3.0 capabilities to the frameworks below because the catalog carries NIST CSF mappings and the Program Guidebook (section 9) expects TIC to be implemented alongside the NIST CSF, NIST SP 800-53 and the agency's other requirements.
Mapped frameworks include:
CIS Controls v8.1
FedRAMP Rev. 5
FIPS 140-3
ISO 27001:2022
NIST CSF 2.0
NIST 800-53 Rev.5
PCI DSS 4.0.1
SOC 2
GovRAMP
Zero Trust Maturity Model
How SmartSuite Supports TIC 3.0
SmartSuite provides the system for managing controls, evidence, mappings, assessments, and reporting.
Use Cyber & IT Risk to hold the Security Capabilities Catalog as a control library with the trust zone, policy enforcement point and use case each capability serves, linked to the agency control and evidence that implements it and to the compensating controls recorded where a use case leaves residual risk; Compliance Management tracks the M-19-26 obligations themselves: the boundary policy update, the allowed use cases, the connection inventory and the FISMA reporting that follows.
Security Capabilities Catalog Library
Load the universal (3.UNI) and PEP (3.PEP) capabilities with their NIST CSF 2.0 mappings, the use cases they apply to, an owner and an implementation status.
Trust Zone and PEP Register
Record each trust zone with its designated trust level, the policy enforcement points that serve it and the security patterns between zones, linked to the capabilities applied at each PEP.
Use Case Adoption and Compensating Controls
Track which of the Traditional TIC, Branch Office, Remote User and Cloud use cases the agency allows under M-19-26 section E, the boundary policy update and the compensating controls for residual risk.
Network Connection Inventory
Keep the M-19-26 section E inventory of connections with service provider, cost, capacity, traffic volume, logical and physical configuration and topology in IT Asset Management (ITAM).
Vendor Overlays and FedRAMP Status
Hold each provider's TIC overlay mapping and FedRAMP authorization status in Third Party Risk Management, with the capability gaps the overlay reveals (Guidebook sections 7 and 9).
Telemetry and FISMA Reporting
Evidence that telemetry reaches CISA for each use case (Guidebook section 10), CISA Services coverage and the TIC posture reported through FISMA, assembled from the same records.
Related frameworks

CIS Controls v8.1 is a prioritized set of 18 Controls and 153 Safeguards, in three Implementation Groups, with a new Govern function.

FedRAMP Rev5 is the legacy FedRAMP certification type: NIST SP 800-53 Rev. 5 baselines, 3PAO assessment and agency authorization for cloud services used by U.S. agencies.

ISO/IEC 27001:2022 specifies requirements for an information security management system: Clauses 4 to 10, risk treatment, the Statement of Applicability and 93 Annex A controls.

NIST CSF 2.0 (CSWP 29, February 26, 2024) is the voluntary cybersecurity framework with six Functions including Govern, 22 Categories, 106 Subcategories, Profiles and Tiers.

NIST SP 800-171 Rev. 2: 110 CUI security requirements in 14 families, withdrawn by NIST on May 14, 2024 but still the edition DFARS 252.204-7012 and CMMC Level 2 cite.

NIST SP 800-53 Rev. 5 is the NIST catalog of security and privacy controls in 20 families, mandatory for federal systems under OMB A-130 and FISMA; Release 5.2.0 issued August 27, 2025.
Frequently Asked Questions For U.S. CISA Trusted Internet Connections (TIC) 3.0 (Federal Network Security Architecture)
M-19-26 (September 12, 2019) rescinded M-08-05, M-08-16, M-08-27 and M-09-32, which had required agency traffic to flow through a physical TIC access point (section B). It made DHS, through CISA, define TIC requirements in use cases whose alternative controls let traffic bypass a TICAP or MTIPS (section C), set up a pilot and approval process with OMB, GSA and the Federal CISO Council (section D), and gave agencies one year to update their boundary policies and name the use cases they allow, tracked through FISMA reporting (section E).
Section 5 of the Program Guidebook and section 3 of the Security Capabilities Catalog list them: Manage Traffic; Protect Traffic Confidentiality; Protect Traffic Integrity; Ensure Service Resiliency; and Ensure Effective Response. Traffic means data in transit between trust zones or stored at either. Each objective stands alone, agencies apply them at a level commensurate with the resources protected, and the guidebook maps them to the six NIST CSF 2.0 Functions.
A trust zone is a discrete computing environment designated for information processing, storage or transmission whose trust level the agency sets; a policy enforcement point (PEP) is a security device, tool, function or application that enforces security policies (Guidebook Appendix C). TIC 3.0 disperses security capabilities across multiple PEPs close to the data instead of concentrating them at a TIC access point, and a security pattern describes the end-to-end data flow between two zones (section 6).
CISA has published the Traditional TIC, Branch Office, Remote User and Cloud use cases; the Cloud use case (April 2023) completed the initial set that M-19-26 Appendix A listed. Traditional TIC remains the default for scenarios no other use case covers. Agencies choose and may combine use cases to suit their risk tolerance, and where a use case does not address residual risk they must apply compensating controls, with their senior officials accountable for risk management (CISA program page; Guidebook section 9).
Volume 3 indexes universal security capabilities, which are enterprise-level and expected in every use case, and PEP security capabilities grouped into Files, Email, Web, Networking, Resiliency, DNS, Intrusion Detection, Enterprise, Unified Communications and Collaboration, Data Protection, Services and Identity (sections 4.1 and 4.2), each mapped to NIST CSF categories. Version 3.0 (April 2023) added five universal capabilities and the Services and Identity groups; version 3.2 (December 2024) updated the mappings to CSF 2.0 and is the current edition.

Put this framework to work in SmartSuite
Manage controls, risks, evidence, and audits in one platform designed for modern governance, risk, and compliance.


