Policy enforcement for secure domain name services
There is disclosed in one example a gateway apparatus, including: a hardware platform including a processor and a memory; and instructions stored within the memory to instruct the processor to: provide a domain name system (DNS) server, the DNS server to provide an encrypted DNS service, and to cache resolved domain names; receive an outgoing network packet; determine a destination address of the outgoing network packet; and upon determining that the destination address was not cached, apply a security policy.
1. A gateway apparatus, comprising:
a hardware platform comprising a processor and a memory; and
instructions stored within the memory to instruct the processor to:
provide a domain name system (DNS) server, the DNS server to provide an encrypted DNS service, and to cache resolved domain names;
receive an outgoing network packet;
determine a destination address of the outgoing network packet
characterize encrypted DNS capabilities of an endpoint source of the outgoing network packet; and
upon determining that the destination address was not cached, apply a security policy based on the encrypted DNS capabilities of the endpoint source.
2. The gateway apparatus of claim 1 , wherein the DNS server is a caching or forwarding server.
3. The gateway apparatus of claim 1 , wherein the DNS server is an authoritative server.
4. The gateway apparatus of claim 1 , wherein the DNS server is further to provide plain-text DNS services.
5. The gateway apparatus of claim 1 , wherein the instructions are further to provide an internet gateway service.
6. The gateway apparatus of claim 1 , wherein the instructions are further to provide a security agent to provide domain name-based security.
7. The gateway apparatus of claim 1 , wherein the instructions are further to purge cached queries after a time to live (TTL).
8. The gateway apparatus of claim 1 , wherein the instructions are to provide service or protocol exceptions to the security policy.
9. The gateway apparatus of claim 1 , wherein the security policy comprises blocking the outgoing network packet if the endpoint source has encrypted DNS and auto-configuration capabilities.
10. The gateway apparatus of claim 1 , wherein the security policy comprises providing a captive portal with configuration instructions if the endpoint source has encrypted DNS capability but lacks auto-configuration capability.
11. The gateway apparatus of claim 1 , wherein the instructions are further to characterize encrypted DNS capabilities of an application source of the outgoing network packet.
12. The gateway apparatus of claim 11 , wherein the security policy comprises blocking the outgoing network packet if the application source has encrypted DNS and auto-configuration capabilities.
13. The gateway apparatus of claim 11 , wherein the security policy comprises providing a captive portal with configuration instructions if the application source has secure DNS capabilities but lacks auto-configuration capabilities.
14. One or more tangible, non-transitory computer-readable storage media having stored thereon executable instructions to:
provision a domain name system (DNS) query cache;
provide a secure DNS server, the secure DNS server to provide at least one of DNS over hypertext transfer protocol secure (DoH) or DNS over transport layer security (DoT), and to cache addresses of resolved domain names with a time to live (TTL);
provide domain name-based security services; and
apply a security policy to an outgoing packet after determining that a destination address of the outgoing packet is not in the DNS query cache, wherein the security policy is based on an encrypted DNS capability of an endpoint source or application source of the outgoing packet.
15. The one or more tangible, non-transitory computer-readable storage media of claim 14 , wherein the DNS query cache comprises a content-addressable memory (CAM) or ternary CAM (TCAM).
16. The one or more tangible, non-transitory computer-readable storage media of claim 14 , wherein the security policy comprises blocking the outgoing packet if the endpoint source or application source has encrypted DNS and auto-configuration capabilities.
17. A computer-implemented method of providing domain name-based network security, comprising:
receiving domain name system (DNS) queries, including DNS over hypertext transfer protocol secure (DoH) or DNS over transport layer security (DoT) queries;
recursively resolving the queries;
caching resolved addresses for the queries;
receiving outbound network traffic;
checking a destination of the outbound network traffic against the cached resolved addresses;
characterizing encrypted DNS capabilities of a source endpoint that provided the outbound network traffic; and
if the destination is not found in the cached resolved addresses, applying a security policy to the outbound network traffic, wherein the security policy is based on the encrypted DNS capabilities of the source endpoint.
18. The method of claim 17 , wherein the security policy comprises blocking the outbound network traffic if the source endpoint has encrypted DNS and auto-configuration capabilities.
19. The method of claim 17 , wherein the security policy comprises blocking the outbound network traffic if the source endpoint has encrypted DNS and auto-configuration capabilities.
20. The method of claim 17 , further comprising characterizing encrypted DNS capabilities of an application source of the outbound network traffic, and adjusting the security policy based on the encrypted DNS capabilities of the application source.