Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Vulnerabilities / Threats

1/9/2014
01:22 PM
Connect Directly
Twitter
RSS
E-Mail
50%
50%

Q&A: McAfee's CTO On The New Intel Security Brand

Mike Fey, McAfee enterprise vice president, CTO, and general manager of corporate products, discusses the end of the McAfee brand name

Intel CEO Brian Krzanich broke the news this week at the Consumer Electronics Show in Las Vegas that the McAfee brand name will be phased out and replaced with "Intel Security" for all of McAfee's security products. The McAfee red shield will remain but with the Intel Security name instead, and McAfee will remain a wholly owned subsidiary of Intel, working "side-by-side" with Intel Security's team.

Dark Reading spoke with Mike Fey, McAfee enterprise vice president, CTO, and general manager of corporate products, about the end of the McAfee brand name.

Dark Reading: Why did Intel decide to eliminate the McAfee name?
Fey: At a high level, it's been a three-year journey for us. Over the last three years, we have marched with our product direction, and managed our directions with Intel's directions so both sides met on common ground and strategy. Now it makes sense to join forces as Intel Security. It's not just changing the McAfee brand, but augmenting what is the security force of Intel.

Dark Reading: Why did you keep the red shield from the McAfee brand?
Fey: As we did brand testing, the shield was a worldwide presence, as it were; it's what people knew us as. If you go overseas, "McAfee" was difficult to pronounce in some regions, [so the name] wasn't quite as strong as we wanted it to be. The Intel brand is one of the top 10 brands in the world. We thought it was a great opportunity to [have] the industry and customers "reunderstand" who we are. We're not an AV company anymore. The bulk of our revenue doesn't come from there. We are in every hot space in security. It felt like a good opportunity to rebrand and respond to the marketplace.

Mike Fey, executive vice president, CTO and general manager of corporate products at McAfee
Mike Fey, executive vice president, CTO, and general manager of corporate products at McAfee

Dark Reading: Did the decision to change the brand name to Intel Security have anything to do with the infamous behavior and legal troubles of McAfee founder John McAfee?
Fey: It really didn't. When he first started having his challenges south of the border [in Belize], we did spend a lot of energy checking with focus groups to make sure it wasn't impacting the brand. We were surprised how little impact it had, especially on the enterprise side. But most know he has not been in enterprise IT for 20-plus years. Even consumers saw [him] as separate. As things became more outlandish, it had very little to do with the company. We weren't really pressured by that ... It didn't drive our decision process.

Dark Reading: How will the change roll out?
Fey: As we hit each major rev, we'll modify the branding look. The product names don't really change. EPO, Antivirus, SIEM, Next-G Firewall names we use ... Intel Security [now] goes in [the product names as well].

Security is a key pillar [for Intel].

Dark Reading: How will the two security teams interface?
Fey: We've divided and conquered where we want to deliver our solution sets. Where we want to join, we will work in a collaborative fashion. For example, with SIEM, we/McAfee drive this independently, with little input from the Intel side. But in identity, this is an area where we found synergy on the Intel side, so we can work together and strengthen a solution to bring to market. Intel has built great security innovations for years, but has not done the best job at bringing them to market because they thought of them as features for their chip families. We are working to make sure we build full solutions.

Have a comment on this story? Please click "Add Your Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message.

Kelly Jackson Higgins is the Executive Editor of Dark Reading. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Commentary
Cyberattacks Are Tailored to Employees ... Why Isn't Security Training?
Tim Sadler, CEO and co-founder of Tessian,  6/17/2021
Edge-DRsplash-10-edge-articles
7 Powerful Cybersecurity Skills the Energy Sector Needs Most
Pam Baker, Contributing Writer,  6/22/2021
News
Microsoft Disrupts Large-Scale BEC Campaign Across Web Services
Kelly Sheridan, Staff Editor, Dark Reading,  6/15/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-26585
PUBLISHED: 2021-06-24
A potential vulnerability has been identified in HPE OneView Global Dashboard release 2.31 which could lead to a local disclosure of privileged information. HPE has provided an update to OneView Global Dashboard. The issue is resolved in 2.32.
CVE-2021-31412
PUBLISHED: 2021-06-24
Improper sanitization of path in default RouteNotFoundError view in com.vaadin:flow-server versions 1.0.0 through 1.0.14 (Vaadin 10.0.0 through 10.0.18), 1.1.0 prior to 2.0.0 (Vaadin 11 prior to 14), 2.0.0 through 2.6.1 (Vaadin 14.0.0 through 14.6.1), and 3.0.0 through 6.0.9 (Vaadin 15.0.0 through 1...
CVE-2021-33604
PUBLISHED: 2021-06-24
URL encoding error in development mode handler in com.vaadin:flow-server versions 2.0.0 through 2.6.1 (Vaadin 14.0.0 through 14.6.1), 3.0.0 through 6.0.9 (Vaadin 15.0.0 through 19.0.8) allows local user to execute arbitrary JavaScript code by opening crafted URL in browser.
CVE-2020-28097
PUBLISHED: 2021-06-24
The vgacon subsystem in the Linux kernel before 5.8.10 mishandles software scrollback. There is a vgacon_scrolldelta out-of-bounds read, aka CID-973c096f6a85.
CVE-2020-7862
PUBLISHED: 2021-06-24
A vulnerability in agent program of HelpU remote control solution could allow an authenticated remote attacker to execute arbitrary commands This vulnerability is due to insufficient input santization when communicating customer process.