US Executive Order 14144 - Strengthening and Promoting Innovation in the Nation's Cybersecurity 4(c)(ii): Sec. 4(c)(ii) Enable encrypted DNS wherever clients and servers support it

What else in your programme already covers this

This control maps to 2 controls across 2 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in Sec. 4 Securing Federal communications – US Executive Order 14144 - Strengthening and Promoting Innovation in the Nation's Cybersecurity

• 4(b)(i) Sec. 4(b)(i) Cover internet number resources by a registry agreement and keep registry records current
• 4(b)(ii) Sec. 4(b)(ii) Publish Route Origin Authorizations for agency IP address blocks
• 4(b)(iii) Sec. 4(b)(iii) Deploy routing security as a contracted internet service provider
• 4(c)(i) Sec. 4(c)(i) Support encrypted DNS in products that act as DNS resolvers
• 4(d)(i) Sec. 4(d)(i) Enforce encrypted, authenticated transport between email clients and servers
• 4(e)(i) Sec. 4(e)(i) Enable transport encryption by default for voice, video and messaging
• 4(e)(ii) Sec. 4(e)(ii) Use end-to-end encryption by default while keeping records capability
• 4(f)(ii) Sec. 4(f)(ii) Support TLS 1.3 or a successor by 2 January 2030