SourceFire to keep branding amid Cisco integration

Security firm to stick with 'strong' brand despite being acquired by Cisco last year

Tags: Cisco Systems IncorporatedMergers and acquisitionsSourcefire (www.sourcefire.com)
  • E-Mail
SourceFire to keep branding amid Cisco integration Perridge: If you look at the messaging, it is kind of a combination of Cisco and SourceFire messaging
By  Tom Paye Published  June 9, 2014

SourceFire will keep its own branding despite being acquired by Cisco late last year and integration steps that have already begun, according to the security firm's channel director, Anthony Perridge.

Speaking to ITP.net at GISEC, Perridge described the steps that were being undertaken to integrate SourceFire into Cisco, but said that SourceFire's brand remains alive and well. He said that the two companies were simply aligning their messaging.

"I think the SourceFire brand is still really strong, and if you look at the messaging, it is kind of a combination of Cisco and SourceFire messaging," he said.

"We're taking the best of both worlds, and the internal branding is better together. We're retaining everything that's good about SourceFire but also leveraging the obvious strengths of Cisco. We're talking about before, during and after an attack, and addressing the entire threat continuum."

Earlier this week, Cisco highlighted aspects of its annual security report that described the threats to energy sector companies. Perridge explained that this was in line with what customers in this region expected from SourceFire, which he said had plenty of customers in the oil & gas sector.

In particular, he said, oil & gas customers were attracted to SourceFire's solutions that help to protect SCADA networks.

"We have a lot of customers in the oil & gas market. And within the SourceFire solution specifically, there are rules that detect vulnerabilities that help protect SCADA networks specifically," he said.

"Within our SourceFire engine, we have the ability to do passive monitoring of the network. It's really very appropriate to a SCADA network. Because with a SCADA network, typically, they go in on a very old operating system, and they're left untouched for many, many years because everybody's fighting disrupting it and bringing it down."

Add a Comment

Your display name This field is mandatory

Your e-mail address This field is mandatory (Your e-mail address won't be published)

Security code