Details
DNS over HTTPS has generally not been adopted in the DoD. DNS is tightly controlled.
It is detrimental for applications to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.
Applications are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions).
Examples of non-essential capabilities include, but are not limited to, advertising software or browser plug-ins not related to requirements or providing a wide array of functionality not required for every mission, but cannot be disabled.
Solution
Windows group policy:
1. Open the group policy editor tool with ‘gpedit.msc’.
2. Navigate to Policy Path: Computer ConfigurationAdministrative TemplatesMozillaFirefoxDNS Over HTTPS
Policy Name: Enabled
Policy State: Disabled
macOS ‘plist’ file:
Linux ‘policies.json’ file:
Add the following in the policies section:
‘DNSOverHTTPS’: {‘Enabled’: false}
Supportive Information
The following resource is also helpful.
This security hardening control applies to the following category of controls within NIST 800-53: Configuration Management.This control applies to the following type of system Unix.
References
- 800-53|CM-7a.
- CAT|II
- CCI|CCI-000381
- Rule-ID|SV-251577r807203_rule
- STIG-ID|FFOX-00-000033
- Vuln-ID|V-251577