# Peter LaMantia

Peter LaMantia writes about enterprise DNS security and governance, including how organizations can find unknown internet-facing assets, clarify ownership of domains and records, and manage DNS risk.

- Profile: https://b2binfluencer.marketing/creators/peter-lamantia/
- LinkedIn: https://www.linkedin.com/in/plamantia
- LinkedIn followers: 1,412
- Based on 11 dated posts, latest 2026-09-22

## Summary

Peter LaMantia is useful for enterprise DNS security and governance content, especially ownership, visibility, and consolidation risks.

- Best for: An enterprise cybersecurity vendor building a DNS security practice for a webinar or content collaboration.
- Not for: A broad awareness push or a meeting-notes tool for small and mid-sized businesses.
- Check first: Ask for recent results, audience details, and newsletter or webinar metrics before committing.

### Takeaways

- Peter LaMantia argues an unknown subdomain owner signals a governance gap, not just a configuration problem.
- They say tools detect dangling records or certificate issues, but ownership and lifecycle management decide fixes.
- They note DNS consolidation stalls because the risk of change feels more urgent than doing nothing.

## Main ideas

- **Enterprises are exposed through DNS assets they cannot see or control**: LaMantia argues that the exposure is not exotic: organizations have internet-facing DNS assets outside their tracking and control, and assessments repeatedly uncover the same findings. 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.
- **The question that decides DNS security is who owns it, not who manages it**: LaMantia distinguishes the questions a company can usually answer from the one it often cannot. 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.
- **Detection is not the bottleneck; accountability and lifecycle management are**: LaMantia argues that security tools already detect many DNS problems, including dangling CNAMEs, orphaned records, and certificate issues, but detection alone leaves risks unmitigated or lets them resurface. 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.
- **DNS consolidation stalls because the risk of change feels more urgent than the risk of doing nothing**: LaMantia frames consolidation as a decision about two risks, not a technical best practice. 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.
- **Namespace ownership is a long-term digital identity decision**: Alongside the operational DNS argument, LaMantia raises a strategic question about where an organization's identity lives. 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.

## Work to read

- [Who owns your domain and DNS governance end-to-end?](https://www.linkedin.com/posts/plamantia_dns-cybersecurity-infosec-activity-7468285471639404544-gMtX)
- [The DNS Governance Operating Model](https://www.linkedin.com/posts/plamantia_cybersecurity-dns-governance-activity-7488213002262020097-8ONu)
- [The biggest DNS risk is the fragmented, poorly governed environment you've learned to live with.](https://www.linkedin.com/posts/plamantia_dns-infrastructure-cybersecurity-activity-7470822178519883776-Wyah)
- [All organizations face an external DNS exposure risk they cannot track or control.](https://www.linkedin.com/posts/plamantia_cybersecurity-dns-easm-activity-7462530300808491008-D3jc)
- [Your unknown external DNS network assets pose a significant risk to brand trust.](https://www.linkedin.com/posts/plamantia_your-unknown-external-dns-network-assets-activity-7465748786875723776-XL8t)

## Brand relationships

- **Innovate Cybersecurity Forum** (mention)

## Partnerships

Peter LaMantia's posts focus on DNS security, governance, external attack surface management, and DNS infrastructure consolidation. They mention a newsletter but no paid placements, pricing, deliverables, or official partnership inquiry route. No official sponsorship page, media kit, or partnership terms are published, so buyers should ask directly about availability, audience details, and operational requirements for a webinar or content collaboration.

## Alternatives

- Anne Bisagno: For a cybersecurity vendor building an enterprise DNS security practice and looking for a webinar or content collaboration on DNS governance. 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.
- Jonathan Baker: For a cybersecurity vendor building an enterprise DNS security practice and looking for a webinar or content collaboration on DNS governance. 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.
- Andy James: For a cybersecurity vendor building an enterprise DNS security practice and looking for a webinar or content collaboration on DNS governance. 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.

---
AI-assisted summary of public posts. Audience demographics are not available. Engagement appears only where we checked recent posts. Method: https://b2binfluencer.marketing/methodology/