Study notes: Understanding DNSSEC

DNSSEC

Recently I have been researching materials covering DNSSEC as it is an important subject for LPIC-3 Exam 303. DNSSEC has been developed to address security issues of the DNS protocol, in particular preventing DNS cache poisoning attacks. Below I post DNSSEC description from Internet Corporation for Assigned Names and Numbers (ICANN), which I find useful and included in my study notes. 

"DNSSEC strengthens authentication in DNS using digital signatures based on public key cryptography. With DNSSEC, it's not DNS queries and responses themselves that are cryptographically signed, but rather DNS data itself is signed by the owner of the data.

Every DNS zone has a public/private key pair. The zone owner uses the zone's private key to sign DNS data in the zone and generate digital signatures over that data. As the name "private key" implies, this key material is kept secret by the zone owner. The zone's public key, however, is published in the zone itself for anyone to retrieve. Any recursive resolver that looks up data in the zone also retrieves the zone's public key, which it uses to validate the authenticity of the DNS data. The resolver confirms that the digital signature over the DNS data it retrieved is valid. If so, the DNS data is legitimate and is returned to the user. If the signature does not validate, the resolver assumes an attack, discards the data, and returns an error to the user."

Source: https://www.icann.org/resources/pages/dnssec-what-is-it-why-important-2019-03-05-en

DNS Records

The following DNS records are associated with DNSSEC:

  • DNSKEY - contains public signing key
  • DS - contains the hash of a DNSKEY record
  • RRSIG - contains a cryptographic signature
  • NSEC - links to the next record name in the zone; used to verify the non-existence of a record
  • NSEC3 - same as NSEC; additionally it uses cryptographically hashed record names to prevent enumeration of the record names in a zone
  • NSEC3PARAM - used by authoritative DNS servers to calculate and determine which NSEC3-records to include in responses

Enabling DNSSEC: BIND

DNSSEC is enabled in named.conf with the following directives:

dnssec-enable yes;
dnssec-validation yes;

A tutorial with detailed DNSSEC configuration steps on BIND by Daniel Stirnimann: 

https://securityblog.switch.ch/2020/12/01/dnssec-signing-your-domain-with-bind-9-16/

DNSSEC with AWS and Route 53

Fortunately, since December 2020 DNSSEC is supported by Amazon Route 53. This significantly limits deployment effort and simplifies configuration. See this YouTube video by Andreas Wittig for the details. 



Comments

  1. AnonymousDecember 3, 2022 at 7:47 PM

    The finest trick to get higher odds to beat slots is to select video games with a theoretical Return to Player above 96%. You find a record of the 12 finest slot machines to play right on this desk. He’d walk away after a few minutes, then 코인카지노 return a bit later to give the game a second chance.

    ReplyDelete

Post a Comment

Popular posts from this blog

Splunk: Authentication with Discord? Wht not! (OAuth 2.0)

Image
As some of you may already know, thanks to OAuth standard (which stands for Open Authorization) we don't need a separate account for every single website. It allows us to share information about our Google account with a third party, such as our name and e-mail address. On many sites we are free to use that "Login with Google/Facebook/other" button to sign up and/or login. Thanks to OAuth we don't have to give our password to the app/website. Upon login we are redirected to the OAuth provider site to login there (for instance to our Google account). And now the best part - if we are already logged on the provider site, this is likely to result in instant login on a third party site (sometimes interrupted by a pop up to confirm OAuth scope).  Here is a list of well-known OAuth providers (Wikipedia): https://en.wikipedia.org/wiki/List_of_OAuth_providers To get better understanding of OAuth 2.0 I would recommend reading these docs for developers: Using OAuth 2.0 to Acces
Read more

Linux: auditd fundamentals

Image
auditd stands for the audit daemon and it can be used to log events happening on a Linux host. It is a very powerful tool that can enable Threat Detection and/or - as the name suggests - create audit records. It writes to /var/log/audit/audit.log and collects such information as timestamp, PID, UID, Audit UID (auid), session info (ses), SELinux info (subj) and message (msg). Installation auditd is installed by default on most of the Linux distributions. In my case, I'm using RHEL 8 for the test purpose. The package is called audit .  Rules auditd is rule-based software and it support the following three types of rules: control : to configure general settings of the audit system, such as event rate limit, etc. file : file rules or watches can monitor files or directories and are using the following syntax: -w path-to-file -p permissions -k keyname syscall : these rules are loaded into the matching engine that intercepts every single syscall on the system and for this reason they
Read more