Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Infrastructure Security //

DNS

9/21/2018
09:35 AM
Larry Loeb
Larry Loeb
Larry Loeb
50%
50%

Cloudflare Looks to Take the Pain Out of DNSSEC Protocol Adoption

Uptake of the newer DNSSEC protocol has been slow, but a new tool from Cloudflare looks to make it easier to ensure secure websites and more control over DNS.

Cloudflare is adding a new feature to its hosting and firewall products that the networking company hopes will address the slow uptake of the Domain Name System Security Extensions (DNSSEC) protocol.

The method to support the DNSSEC protocol has been a manual one before this, requiring a website owner to add a "DS record" to its account with their registrar.

A Cloudflare customer that is working with a registry that supports DNSSEC can activate it for their account by the press of a button from the Cloudflare dashboard.

DNSSEC proves authenticity and integrity -- though not confidentiality -- of a response from the authoritative nameserver. This makes it much harder for a bad actor to inject malicious DNS records into the resolution path through malware techniques such as BGP Leaks and cache poisoning. Trust in Domain Name System (DNS) can be critical when a domain is publishing record types that are used to declare trust for other systems.

A simple way for a user to test if DNSSEC is enabled within their network is to try and load brokendnssec.net with a browser. If the page loads, the protocol is inactive.

The number of DNS queries validated by recursive resolvers for DNSSEC has remained flat over the years. Worldwide, less than 14% of DNS requests have DNSSEC validated by the resolver according to APNIC, which functions as the Regional Internet Registry for the Asia Pacific area.

Cloudflare believes that struggle to add a DS record may be at the root of the low utilization:

Locating the part of the registrar UI that houses DNSSEC can be problematic, as can the UI of adding the record itself. Additional factors such as varying degrees of technical knowledge amongst users and simply having to manage multiple logins and roles can also explain the lack of completion in the process. Finally, varying levels of DNSSEC compatibility amongst registrars may prevent even knowledgeable users from creating DS records in the parent.

While all of this is going on, the ICANN Organization is preparing to change the cryptographic keys that help to protect the Internet's DNS for the first time.

The changing of the keys, known as the "Root Key Signing Key (KSK) Rollover," is currently scheduled for October 11. Final ratification of that date has not yet been done.

ICANN attempted this update a year ago but had to cancel it at the last minute. The rollover was postponed due to "unclear data received just before the rollover." ICANN thinks the two thirds of users that do not use DNSSEC will not be impacted by the KSK rollover.

Related posts:

— Larry Loeb has written for many of the last century's major "dead tree" computer magazines, having been, among other things, a consulting editor for BYTE magazine and senior editor for the launch of WebWeek.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
NSA Appoints Rob Joyce as Cyber Director
Dark Reading Staff 1/15/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: Hunny, I looked every where for the dorritos. 
Current Issue
2020: The Year in Security
Download this Tech Digest for a look at the biggest security stories that - so far - have shaped a very strange and stressful year.
Flash Poll
Assessing Cybersecurity Risk in Today's Enterprises
Assessing Cybersecurity Risk in Today's Enterprises
COVID-19 has created a new IT paradigm in the enterprise -- and a new level of cybersecurity risk. This report offers a look at how enterprises are assessing and managing cyber-risk under the new normal.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-8567
PUBLISHED: 2021-01-21
Kubernetes Secrets Store CSI Driver Vault Plugin prior to v0.0.6, Azure Plugin prior to v0.0.10, and GCP Plugin prior to v0.2.0 allow an attacker who can create specially-crafted SecretProviderClass objects to write to arbitrary file paths on the host filesystem, including /var/lib/kubelet/pods.
CVE-2020-8568
PUBLISHED: 2021-01-21
Kubernetes Secrets Store CSI Driver versions v0.0.15 and v0.0.16 allow an attacker who can modify a SecretProviderClassPodStatus/Status resource the ability to write content to the host filesystem and sync file contents to Kubernetes Secrets. This includes paths under var/lib/kubelet/pods that conta...
CVE-2020-8569
PUBLISHED: 2021-01-21
Kubernetes CSI snapshot-controller prior to v2.1.3 and v3.0.2 could panic when processing a VolumeSnapshot custom resource when: - The VolumeSnapshot referenced a non-existing PersistentVolumeClaim and the VolumeSnapshot did not reference any VolumeSnapshotClass. - The snapshot-controller crashes, ...
CVE-2020-8570
PUBLISHED: 2021-01-21
Kubernetes Java client libraries in version 10.0.0 and versions prior to 9.0.1 allow writes to paths outside of the current directory when copying multiple files from a remote pod which sends a maliciously crafted archive. This can potentially overwrite any files on the system of the process executi...
CVE-2020-8554
PUBLISHED: 2021-01-21
Kubernetes API server in all versions allow an attacker who is able to create a ClusterIP service and set the spec.externalIPs field, to intercept traffic to that IP address. Additionally, an attacker who is able to patch the status (which is considered a privileged operation and should not typicall...