Attacks/Breaches

4/13/2015
11:00 AM
Steve Riley
Steve Riley
Commentary
Connect Directly
LinkedIn
RSS
E-Mail vvv
100%
0%

Better Together: Network Operations & Infosec

Getting networking and information security teams together in the same room is a critical step for companies that want to build a continuous information security culture.

The recent computer attacks against Anthem and Premera Blue Cross are the latest case studies that demonstrate the necessary convergence of IT and security operations. This is something information security professionals should welcome, even demand. In fact, the network operations team can be an information security department’s best resource for gaining understanding and insight into an organization’s security operations, which traditional security solutions and best practices alone cannot provide.

Understanding what “normal” network activity looks like is critical to quickly spotting suspicious activities that point to a malicious outsider or insider, or a mistake by an innocent employee that result in data theft or loss. However, bridging the gap between the Network Operations Center (NOC) and Security Operations Center (SOC) is not only a technology challenge, but also an organizational one. There are three keys to fostering this collaboration:

  • Eliminating the silos that separate both systems and personnel, 
  • Creating joint emergency response teams comprised of network operations and information security personnel, and
  • Implementing a long-term plan for how to constantly improve processes and training.

In the typical IT organizational chart, network operations is responsible for ensuring system performance and information availability, while information security focuses on protecting those systems and information stores from threats. Typically, as Rudyard Kipling wrote, “and never the twain shall meet.” However, the spate of high-profile breaches against large companies across retail, financial services, and healthcare over the last year show that must change.

In most of these cases, the companies were not aware they had been breached until a third party notified them. Although Anthem discovered its breach on its own after a database administrator noticed a query running with his account that he didn't initiate, that discovery wasn’t made until after the attacker had spent six weeks silently stealing information.

For an enterprise, the key takeaway is its critical need to be able to detect activities on the network that can lead to a data breach. That capability is diminished by the fact that security operations and network operations typically work in silos. That means security vulnerabilities have to be handled twice: first by the SOC, which has evidence of malicious activity but often no mechanism for actively stopping it, and then again by the NOC, which needs to wait for specific instructions from the SOC. Any time delay here creates advantages for an attacker.

Additionally, most technology systems and business applications work in their own silos and do not communicate with one another. Consequently, IT cannot streamline and automate information sharing or event correlation between security vulnerabilities and performance issues. Here are four steps to overcome this organizational hurdle:

Step 1: To maximize insight, foster teamwork
The first step is to acknowledge the value of the network team in security operations. Network engineers have visibility and access to forensic data that simply doesn’t exist in other parts of an organization. Once IT leadership acknowledges this, the next step is all about putting the tools and processes in place to integrate network resources into security processes. It sounds simple, but having a thorough understanding of normal is a critical factor in preventing potentially harmful activity on your organization’s network.

Step 2: Packet capture meet SIEM
Security teams should work to leverage the network team’s investments in packet capture agents, packet analyzers, NetFlow sources and deep packet inspection performance monitoring. Often these can be tightly integrated into a Security Incident Event Management (SIEM) system for high-fidelity visibility, and quick pivots into useful forensic data. It’s also worth noting how the Premera breach serves a reminder to information security professionals that joining forces with the network team does not obviate the need to continue traditional due diligence. Premera had failed to install the most recent security patches, opening the door to the attackers.

Step 3: Change the culture but hands off also applies
In terms of fostering collaboration, there should be clear roles and responsibilities across NOC and SOC teams, supported by well-defined “hand-offs.” Documenting them isn’t enough. You have to use them, analyze key weaknesses, and continuously improve them. Joint emergency response teams enable broader insight, increased tribal knowledge, faster artifact gathering, well-rounded analysis, and ultimately a stronger information security posture. Identify and appoint a strong leader who can rally the troops, and mold them into a cohesive team passionate about continuous improvement – not just compliance.

Step 4: Don’t accept the status quo
With a strong base to build upon, an organization should turn its focus to accelerating and improving its capabilities. Never be satisfied with the status quo. To optimize operations, leverage techniques from traditional continuous improvement strategies such as Theory of ConstraintsLean, or lessons learned from the DevOps movement.  Invest in training and skill development so your people are effective and empowered, break work down into smaller chunks so it flows smoother, automate to gain operational efficiencies, and measure risk, performance and quality of operations.

Threats are getting increasingly harder to discover, and attackers are more brazen than ever. Getting network operations and information security teams together in the same room for the first time will be a critical step for organizations that want to build a continuous information security improvement culture capable of defending against those threats.

Steve actively works to raise awareness of the technical and business benefits of Riverbed's performance optimization solutions, particularly as they relate to accelerating the enterprise adoption of cloud computing. His specialties include information security, compliance, ... View Full Bio
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Julian Assange Arrested in London
Dark Reading Staff 4/11/2019
8 'SOC-as-a-Service' Offerings
Steve Zurier, Freelance Writer,  4/12/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
5 Emerging Cyber Threats to Watch for in 2019
Online attackers are constantly developing new, innovative ways to break into the enterprise. This Dark Reading Tech Digest gives an in-depth look at five emerging attack trends and exploits your security team should look out for, along with helpful recommendations on how you can prevent your organization from falling victim.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-1840
PUBLISHED: 2019-04-18
A vulnerability in the DHCPv6 input packet processor of Cisco Prime Network Registrar could allow an unauthenticated, remote attacker to restart the server and cause a denial of service (DoS) condition on the affected system. The vulnerability is due to incomplete user-supplied input validation when...
CVE-2019-1841
PUBLISHED: 2019-04-18
A vulnerability in the Software Image Management feature of Cisco DNA Center could allow an authenticated, remote attacker to access to internal services without additional authentication. The vulnerability is due to insufficient validation of user-supplied input. An attacker could exploit this vuln...
CVE-2019-1826
PUBLISHED: 2019-04-18
A vulnerability in the quality of service (QoS) feature of Cisco Aironet Series Access Points (APs) could allow an authenticated, adjacent attacker to cause a denial of service (DoS) condition on an affected device. The vulnerability is due to improper input validation on QoS fields within Wi-Fi fra...
CVE-2019-1829
PUBLISHED: 2019-04-18
A vulnerability in the CLI of Cisco Aironet Series Access Points (APs) could allow an authenticated, local attacker to gain access to the underlying Linux operating system (OS) without the proper authentication. The attacker would need valid administrator device credentials. The vulnerability is due...
CVE-2019-1830
PUBLISHED: 2019-04-18
A vulnerability in Locally Significant Certificate (LSC) management for the Cisco Wireless LAN Controller (WLC) could allow an authenticated, remote attacker to cause the device to unexpectedly restart, which causes a denial of service (DoS) condition. The attacker would need to have valid administr...