• Resources
  • A House Divided: Bridging the Gap Between Network and Security Team

A House Divided: Bridging the Gap Between Network and Security Team

Challenges in Network Team-Cybersecurity Team collaboration & how to overcome them, featuring Matthew Devost & ELEVI Associates, LLC founder Phil Puccio

Key Takeaways
  • Security teams require access to DNS data to detect anomalies, threats, and suspicious patterns in network activity.
  • Network teams are concerned that security-driven DNS changes could introduce instability and impact network uptime.
  • The disconnect between network and security teams can slow incident response and leave critical threats undetected.
  • Lack of shared visibility into DNS data creates operational silos that hinder effective troubleshooting and root-cause analysis.
  • Establishing controlled, read-only access to DNS information for security teams enables threat hunting without risking production changes.
  • Clear role separation, governance, and tooling that supports collaboration can align network reliability goals with security monitoring needs.

Network teams and security teams don’t always see eye to eye. Security teams want access to DNS information so they can search for anomalies and patterns. Network teams don’t want the security team making changes which would impact network uptime. In this video, we run through the negative impact this divide has on networks, and what you can do about it.

⏳ Cisco Live is almost here. Put BlueCat on your agenda for smarter, more secure networks.

Get the details