Peter LaMantia

The named symptoms are legacy DNS records, third-party dependencies with unclear ownership, incomplete SPF and DMARC coverage, and externally visible assets outside governance. They place external DNS within external attack surface management and digital risk management, tie it to brand trust, and say AI is accelerating reconnaissance and exploitation—raising the urgency of a pre-emptive cybersecurity posture on DNS rather than a response after a problem appears.

In a post on unknown external DNS network assets, LaMantia says the issue is prevalent across enterprises and points to steps for a pre-emptive posture. A later post reports the same pattern in DNS assessments for enterprise security leaders at a recent Innovate Cybersecurity Forum, listing the four findings above as recurring results.

Read original · Original 2

Managing DNS, monitoring DNS, and registering domains are not the same as owning governance for every domain, subdomain, DNS record, and externally exposed asset across the enterprise.

• The claim is that the biggest DNS security risk is not a misconfiguration but an ownership gap.
• The test is direct: if you cannot identify the owner and purpose of a subdomain, you have a governance problem.
• This reframes DNS risk as an issue of ownership, visibility, and control rather than a technical one.

LaMantia says this conclusion comes from assessing thousands of DNS assets for hundreds of enterprises. An unidentified subdomain makes the ownership gap concrete: nothing is technically broken, but no one can say why the record exists or who is responsible for it.

Read original

What’s missing is ownership, accountability, change control, and lifecycle management around the assets. To address that gap, they present a named framework, "The DNS Governance Operating Model," described as integrating EASM, DNS posture management, continuous threat exposure management (CTEM), and DNS governance into one operating model for medium and large enterprises.

The framework appears in one newsletter edition. The post ends by asking readers: what do you see as the greatest obstacle to effective DNS governance in medium and large enterprises?

This is the most developed account of LaMantia's approach in these posts. An earlier ownership argument explains why DNS risk persists; this post turns it into a program that also covers change control and lifecycle management.

Read original

Infrastructure leaders already accept that DNS should be consolidated, but the risk of changing it feels more immediate than the risk of leaving it alone. The counterargument: the status quo is riskier than most organizations realize, urgency is shifting, and the fragmented, poorly governed environment a company has learned to live with is itself the biggest DNS risk.

The stakes are personal: anyone who has been on an emergency bridge call during a DNS outage or hijack will recognize the story. That incident, not the assessment finding, changes the internal calculation.

Read original

With ICANN's Brand TLD application window open, the choice is between continuing to rely on rented third-party namespaces and moving toward a brand-authentic namespace the organization controls over the long term. The post also offers a short overview of how security can be strengthened with a trusted Brand Top-Level Domain, framing it as an open question rather than a recommendation.

The Brand TLD question appears in a post otherwise focused on external DNS exposure, making it a distinctive thread in the material rather than a general theme.

Brand TLDs appear in only one of the five posts. Ask how central this work is to LaMantia's ongoing writing.

Read original

Newcomers should start here to understand why DNS risk persists even when organizations already run DNS tools.

The post distinguishes managing, monitoring, and registering DNS from owning its governance across every domain, subdomain, record, and externally exposed asset in an enterprise.

• LaMantia says that, after assessing thousands of DNS assets for hundreds of enterprises, the biggest risk they find is an ownership gap rather than a misconfiguration.
• The test is concrete: if you cannot identify the owner and purpose of a subdomain, you have a governance problem.
• The post points to a newsletter on why DNS risk is an ownership, visibility, and control issue.

For brands planning a campaign

For a vendor selling DNS security, this post frames the buying problem as accountability and ownership rather than detection coverage. It offers a strong opening structure for a webinar or content collaboration that asks enterprise teams to map ownership before evaluating tools.

Newcomers should read it second: it turns the ownership problem into a named framework and is the clearest statement of LaMantia's approach in the posts.

The post argues that security tools can detect many issues, such as dangling CNAMEs, orphaned records, and certificate problems, but those risks often go unmitigated or resurface without ownership, accountability, change control, and lifecycle management.

• It presents "The DNS Governance Operating Model" as a framework that integrates EASM, DNS Posture Management, CTEM, and DNS governance into one operating model for enterprise organizations.
• It asks readers what they see as the greatest obstacle to effective DNS governance in medium and large enterprises.

For brands planning a campaign

The operating model provides a ready-made agenda for a webinar or content series aimed at enterprise security leaders. The closing question can gather audience input or shape an interactive session.

Newcomers should read it to understand the internal objection that stalls DNS consolidation projects, not just the technical risk.

The post says every infrastructure leader knows DNS should be consolidated, but the risk of change feels more immediate than the risk of doing nothing—until an outage or hijack happens. It invokes emergency bridge calls during a DNS outage or hijack as a shared experience and points to a newsletter about why consolidation keeps getting postponed, how urgency is shifting, and why the status quo is riskier than most organizations realize.

For brands planning a campaign

Useful for vendor messaging about the cost of delay and content that helps buyers answer internal objections to a DNS consolidation project. It also suggests a webinar angle focused on the gap between recognizing the problem and acting on it.

Newcomers should read it to see the symptoms of poor DNS governance and understand the Brand TLD angle LaMantia raises.

The post describes DNS assessments LaMantia conducted for enterprise security leaders at a recent Innovate Cybersecurity Forum and repeatedly lists the same findings: legacy DNS records, third-party dependencies with unclear ownership, incomplete SPF and DMARC coverage, and externally visible assets outside governance.

• It connects AI-accelerated reconnaissance and exploitation to external DNS becoming a critical part of EASM and digital risk management.
• It then raises ICANN's open Brand TLD application window as a strategic choice between relying on rented third-party namespaces and moving toward a brand-authentic namespace the organization controls.
• The post points to a newsletter with observations and an overview of Brand TLD security.

For brands planning a campaign

The Brand TLD question offers a distinctive angle for enterprise content and could support a collaboration pairing DNS governance education with namespace ownership decisions. The assessment findings also provide concrete prompts for an audit-focused campaign.

Newcomers can start here for the headline claim, then move to the longer posts on ownership, governance, and consolidation.

The post says unknown external DNS network assets pose a significant risk to brand trust, the issue is prevalent across all enterprises, and the article outlines steps for establishing a "Pre-emptive Cybersecurity" posture on DNS.

For brands planning a campaign

A concise top-of-funnel message to introduce DNS governance before deeper technical or operational content, with the linked article as a follow-up.

In a post about unknown external DNS network assets, they write that the exposure threatens brand trust and set out steps toward what is called a pre-emptive cybersecurity posture on DNS.

• A later post reports the same pattern from DNS assessments for enterprise security leaders at an Innovate Cybersecurity Forum: legacy DNS records, third-party dependencies with unclear ownership, incomplete SPF and DMARC coverage, and externally visible assets outside governance.
• They connect the exposure to AI speeding up reconnaissance and exploitation, and place external DNS within EASM and digital risk management.

Leads with a claim that the risk applies across organizations, then backs it with patterns observed during on-site assessments rather than a single client case.

For brands planning a campaign

This is the clearest problem statement for a vendor building an enterprise DNS practice. The observed patterns—legacy records, unclear ownership, SPF and DMARC gaps, and ungoverned external assets—translate directly into discovery questions, an assessment checklist, or a webinar opener.

Examples: Source 1 · Source 2

A post distinguishes the questions organizations can usually answer—who manages, monitors, or registers DNS—from the one they often cannot: who owns governance for every domain, subdomain, DNS record, and externally exposed asset.

• They say that, after assessing thousands of DNS assets for hundreds of enterprises, finding no owner or purpose for a subdomain points to a governance problem, not a technical one.
• A later edition continues the argument: tools can detect dangling CNAMEs, orphaned records, and certificate problems, but those risks go unmitigated or return without ownership, accountability, change control, and lifecycle management.

Reframes a technical issue as an organizational one, using a chain of ownership questions to distinguish management, monitoring, registration, and governance.

For brands planning a campaign

An ownership-first message gives a vendor a way beyond pure tooling: a governance assessment, an accountability model, or a workshop on assigning owners to DNS assets. The recurring question, “Who owns this?”, works well as a live poll or a one-page self-assessment for a session.

Examples: Source 1 · Source 2

The premise is that detection alone leaves DNS risk unaddressed, and governance must connect security tooling to accountability and change control. The post closes by asking readers what they see as the greatest obstacle to effective DNS governance in their organizations.

Names and defines a framework, then closes with a direct question to the audience. That prompt pattern recurs across the posts, which typically point readers to a newsletter edition rather than carry the full argument on LinkedIn.

Ask how far the model has been developed and applied; it appears in a single post.

For brands planning a campaign

The named model is a ready hook for a joint session or co-authored framework explainer, with a vendor’s EASM or CTEM capability positioned within the governance layer LaMantia says is missing. Audience questions are already part of the format, making a webinar or Q&A a natural fit.

Examples: Source 1

Consolidation keeps getting postponed because the risk of change feels more immediate than the risk of doing nothing—until an outage or hijack occurs. The post describes how urgency shifts and presents the emergency bridge call during a DNS outage or hijack as a familiar story for infrastructure leaders.

Frames the decision as a trade-off between two risks rather than a technical best practice, speaking directly to people who have handled a live DNS incident.

For brands planning a campaign

A vendor can build content around migration risk versus status-quo risk, with outage and hijack scenarios supplying concrete stakes. The angle reaches infrastructure and IT operations audiences, not just security teams.

Examples: Source 1

LaMantia raises the question alongside the opening of ICANN’s Brand TLD application window and offers a short overview of how security can be strengthened with a trusted brand top-level domain, in a post otherwise focused on external DNS exposure.

Pairs an operational DNS finding with a long-horizon brand and digital-identity argument, framed as an open strategic question rather than a recommendation.

Ask how much of LaMantia’s ongoing work focuses on brand TLDs; they appear in only one post.

For brands planning a campaign

A security vendor pitch fits least naturally here. Use this thread as a discussion topic for brand, domain, and digital-identity audiences, not as evidence of DNS security demand.

Examples: Source 1

Several end with hashtags or a question for readers.

• LaMantia writes in the first person about assessments conducted and patterns observed, and keeps LinkedIn posts short rather than republishing newsletter text.
• The subject matter stays tightly focused on DNS security, governance, and infrastructure consolidation.

Short LinkedIn posts point readers to longer newsletter content and often end with a question.

For brands planning a campaign

Plan a collaboration across both surfaces: a LinkedIn-level hook plus a longer newsletter or webinar piece to develop the argument. The narrow DNS focus means an off-topic collaboration would sit awkwardly alongside the existing writing.

Examples: Source 1 · Source 2 · Source 3 · Source 4 · Source 5

They repeatedly saw legacy DNS records, third-party dependencies with unclear ownership, incomplete SPF/DMARC coverage, and externally visible assets outside governance. The post does not state whether the forum engagement involved sponsorship, a speaking fee, or a client relationship; ask LaMantia to clarify.

View example

Bisagno writes that effective BYOD programs combine clear policies, employee education, identity security and ongoing oversight, and that cybersecurity is a business-resilience issue, not just an IT concern. LaMantia makes the same point: the biggest DNS risk is the missing owner and lifecycle, not a misconfiguration.

Bisagno covers endpoint and device governance for hybrid work — BYOD, device trust, Zero Trust — for business leaders weighing productivity against risk. LaMantia stays within one technical domain, going deeper for the security and infrastructure teams responsible for it.

Read original · Original 2

Baker writes that backlog findings are not dangerous on their own; effort should go toward breaking paths an adversary can actually walk.

• LaMantia argues that tools already detect dangling CNAMEs and orphaned records, but the risk persists without ownership and lifecycle management.
• Each builds the case around a named concept — threat debt and the DNS Governance Operating Model — and both place their work within CTEM.

Baker addresses the broader vulnerability and exposure program, covering adversary TTPs, control validation, AI asset inventory and detection tuning.

• His posts point to an employer's blog and a webinar.
• LaMantia focuses on DNS and namespace governance rather than the broader program Baker describes.

Read original · Original 2

James opens with reconnaissance as the first move every serious attacker makes; LaMantia argues that AI is accelerating reconnaissance and exploitation against exposed DNS.

• Both conclude that template-driven testing or tooling alone will not change the outcome; governance and discipline matter.
• Each writes from the position of leading a security business and ends posts with a link to a longer article.

James writes about offensive security services and AI adoption decisions — red teaming scoped to a client's reality, C360RED engagements, data ownership and risk tolerance in AI rollouts — rather than DNS. His posts are more directly service- and offer-led than LaMantia's, which stay focused on the problem and the framework.

Read original · Original 2

Bisagno is the better first call when the challenge is reaching the people who approve the budget, not explaining DNS.

• Her posts frame security as a business-resilience and governance question, not an IT one, and address leadership directly: personal devices, hybrid work, regulated industries, identity, policy, employee education, and oversight.
• A DNS governance session co-built with her could use the ownership and accountability argument LaMantia makes, then frame it for executives as part of technology governance and Business Resilience.
• She is also the stronger choice for a multi-topic relationship.
• Her material covers BYOD, device trust, Zero Trust, and a phased approach to building security foundations, giving a vendor with a broader portfolio additional topics to explore.
• Vendors marketing to regulated enterprises will also find her framing of compliance, productivity, and employee experience closer to how those buyers describe the problem internally than DNS exposure statistics are.

Bisagno's posts contain no DNS, external attack surface management, subdomain ownership, SPF/DMARC, or name-space material.

• The vendor would need to supply the DNS problem statement, ownership test, consolidation argument, and operating model, while Bisagno provides the enterprise-governance frame rather than the subject expertise.
• That makes this a vendor-written piece in an executive's voice, not a co-authored technical explainer, and shifts the audience from DNS and EASM practitioners to general security and business leaders.
• If the campaign needs credibility with people who already run DNS estates, this reaches the buyer but not the practitioner.

Examples: Source 1 · Source 2

Baker is the better choice when the vendor wants DNS to enter the conversation as one exposure among many, not as its own discipline.

• His posts make a clear argument: managing a list of findings does not reduce risk; programs should focus on the paths an adversary can actually walk.
• He lays out concrete programme actions — map critical assets against the adversaries that matter for the industry and geography, validate defenses against real documented techniques, inventory AI agents and integrations, and keep detection engineering current — and calls the problem threat debt, supported by a webinar and blog.
• For a DNS vendor, this is the most natural route into an existing, funded budget line.
• DNS records, dangling CNAMEs, and unknown externally exposed assets are exactly the kind of findings that sit in a backlog and become dangerous in combination, as Baker argues.
• A joint session on which exposure paths matter, using DNS as a worked example, fits his vocabulary and reaches security programme leaders already spending on continuous exposure management and validation.

DNS becomes an illustration rather than the subject.

• The ownership-and-governance framing LaMantia has built — who owns every record, subdomain, and externally exposed asset, and the operating model connecting EASM, DNS posture management, and change control — would have to be rebuilt from scratch.
• A vendor selling DNS governance may also find itself competing for attention within a broader exposure-management narrative that other vendors own more credibly.
• Baker's posts appear tied to his employer's product and community, including references to a named platform and co-hosted webinar, so a vendor in the same or an adjacent category should check for direct commercial conflicts before treating him as an independent voice.
• He offers no ready-made DNS-specific hook, leaving more of the content work to the vendor.

Examples: Source 1 · Source 2

James is the better choice when the campaign should start with the attacker rather than the defender.

• His posts open with the observation that serious attackers begin with reconnaissance — studying people, technology, suppliers, and processes before moving — and argue that too much security testing follows the testing company's template instead of the customer's reality.
• He writes as the chief executive of a red-team firm and tests that claim through his company's method: engagements designed around the client's environment and the risks that actually matter.
• That reconnaissance framing maps closely to the DNS problem.
• Unknown external DNS assets, legacy records, and third-party dependencies are discovered during the same phase James describes.
• A DNS vendor can use his narrative — what an attacker sees before they act — to make external attack surface management feel urgent rather than administrative.
• His AI post adds another current angle: organisations deploying AI top-down before defining data ownership, governance, and risk tolerance, pairing with the AI-accelerated reconnaissance point LaMantia makes.
• The collaboration becomes a red-team view of what is exposed, with the vendor's DNS capability presented as a way to see it first.

James's posts leave the governance argument — the vendor's strongest content asset — largely behind.

• They offer no ownership model, accountability framework, or DNS, domain, or name-space material, so a session built around them would persuade by demonstrating adversary behaviour rather than giving the audience an operating model to adopt.
• His posts also read as company promotion, including an explicit invitation to discuss engaging his firm.
• A vendor sharing a stage with him may therefore amplify a security services provider whose offerings overlap with the services business around the vendor's product.
• The two-post sample establishes his reconnaissance-first and disciplined-AI positions, but does not show how he teaches or what evidence he brings to a technical audience.
• Ask for examples of his technical presentations and the evidence he uses before committing.

Examples: Source 1 · Source 2