Schneier on Security

APRIL 9, 2020

A few months ago, Brian Krebs told the story of the domain corp.com, and how it is basically a security nightmare: At issue is a problem known as " namespace collision ," a situation where domain names intended to be used exclusively on an internal company network end up overlapping with domains that can resolve normally on the open Internet.

DNS 361

DNS Wireless Internet Internet 361

Krebs on Security

APRIL 7, 2020

From February’s piece: At issue is a problem known as “ namespace collision ,” a situation where domain names intended to be used exclusively on an internal company network end up overlapping with domains that can resolve normally on the open Internet. Further reading: Mitigating the Risk of DNS Namespace Collisions (PDF).

DNS 322

DNS Wireless Risk Passwords 322

SC Magazine

APRIL 12, 2021

Name:Wreck adds a second layer of complexity – a common misinterpretation of the DNS standards involving memory pointers and message compression. . If you look at DNS, the original document is from 1983 and then there are several other scattered documents that talk about other ways to prevent problems.

DNS 108

DNS Internet Internet Media 108

CyberSecurity Insiders

JANUARY 25, 2022

This research is part of CSC’s latest report, “ Two Year Analysis: The Impact of COVID-19 on Internet Security and Safety. In today’s digital economy, domain name related cybercrime is exponentially rising and impacting organizations, customers, partners, and the connected internet supply chain.

Artificial Intelligence 52

Artificial Intelligence Phishing Technology DNS 52

Adam Levin

JULY 8, 2020

Far from being jealously guarded assets with Fort Knox-level security, a new study of Forbes Global 2000 Companies suggests many domain names are imminently hackable. A whopping 97 percent failed to use DNSSEC , a domain security protocol designed to address core vulnerabilities in the foundations of the internet itself.

Hacking 130

Hacking Retail Cyber Insurance Authentication 130

NopSec

JANUARY 27, 2015

Applications have access to the DNS resolver primarily through the gethostbyname*() set of functions. released on November 10, 2000. Plus most of the Internet-exposed services requires some sort of name resolution. My suggestion: cloud-based Linux Internet exposed servers should be patched immediately! and glibc-2.18).

DNS 52

DNS Internet Internet Risk 52

Krebs on Security

FEBRUARY 8, 2020

At issue is a problem known as “ namespace collision ,” a situation where domain names intended to be used exclusively on an internal company network end up overlapping with domains that can resolve normally on the open Internet. INSTANT CORPORATE BOTNET, ANYONE? Department of Homeland Security. Control corp.com.”

DNS 333

DNS Internet Internet Software 333