No. Organizations can choose to meet their security, regulatory, and operational requirements in different ways. Those that rely on network-based monitoring can adopt the solutions described in this project as they adopt TLS 1.3 in their enterprise. As an example, OMB M-22-09 recommends the use of secure cryptographic protocols like TLS 1.3, and it recognizes the need for deep traffic inspection in application environments with compensating controls to make sure that visibility and privileges are restricted to authorized users who have the need to perform their job. There are cases where the risks of weak or compromised network inspection devices can be higher for networks that service a diverse and dynamic set of users, devices, and network destinations, such as those used by the organization’s staff for day-to-day work. In cases where organizations segment their networks, move away from intranets, and permit access to enterprise services from any network, inspecting traffic in these environments may become more focused and dependent on business cases over time. Fine grained policy control over which sessions are inspected is recommended.