When any business launches a new innovative service, particularly a technology service, it is critical to listen to prospect questions extremely carefully. Since the launch DNS Inspector, we consistently hear these 3 questions.
- What are examples of DNS security exposures or gaps?
- What will happen if these exposures are not addressed?
- How does DNS Inspector solve this problem?
Exposures Examples
Insecure Redirect Hops
Session compromise and/or Man in the Middle → DNS Hijack
Lame Delegations
Hacker can take control of your DNS → DNS Hijack
Dangling CNAMEs
CNAME pointing to URL you do not control → DNS Hijack
Orphaned DNS
A Record pointing to an IP you do not control → DNS Hijack
NO DNSSEC
Man in the Middle → DNS Hijack
System Controls
Ungoverned Registrar or DNS Accounts: Social Engineer → DNS Hijack
How DNS Inspector Solves
- Automation to discover and display security gaps on your domains and DNS, so they can be closed
- Displays in a single pane of glass, domain portfolio information related to live certificates, response headers, network hops, IPs, Registrars & DNS provider information to inform triage and resolution.
Without DNS Inspector teams are disadvantaged
- Exposures are hidden from IT and InfoSec teams.
- Teams would need to spend hundreds of hours to uncover these gaps and information.
- Teams have no way to know when a new security exposure is introduced on their DNS network.