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
US Capitol Attack a Wake-up Call for the Integration of Physical & IT Security
Seth Rosenblatt, Contributing Writer,  1/11/2021
IoT Vendor Ubiquiti Suffers Data Breach
Dark Reading Staff 1/11/2021
The Data-Centric Path to Zero Trust
Altaz Valani, Director of Insights Research, Security Compass,  1/13/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
2020: The Year in Security
Download this Tech Digest for a look at the biggest security stories that - so far - have shaped a very strange and stressful year.
Flash Poll
Assessing Cybersecurity Risk in Today's Enterprises
Assessing Cybersecurity Risk in Today's Enterprises
COVID-19 has created a new IT paradigm in the enterprise -- and a new level of cybersecurity risk. This report offers a look at how enterprises are assessing and managing cyber-risk under the new normal.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-7343
PUBLISHED: 2021-01-18
Missing Authorization vulnerability in McAfee Agent (MA) for Windows prior to 5.7.1 allows local users to block McAfee product updates by manipulating a directory used by MA for temporary files. The product would continue to function with out-of-date detection files.
CVE-2020-28476
PUBLISHED: 2021-01-18
All versions of package tornado are vulnerable to Web Cache Poisoning by using a vector called parameter cloaking. When the attacker can separate query parameters using a semicolon (;), they can cause a difference in the interpretation of the request between the proxy (running with default configura...
CVE-2020-28473
PUBLISHED: 2021-01-18
The package bottle from 0 and before 0.12.19 are vulnerable to Web Cache Poisoning by using a vector called parameter cloaking. When the attacker can separate query parameters using a semicolon (;), they can cause a difference in the interpretation of the request between the proxy (running with defa...
CVE-2021-25173
PUBLISHED: 2021-01-18
An issue was discovered in Open Design Alliance Drawings SDK before 2021.12. A memory allocation with excessive size vulnerability exists when reading malformed DGN files, which allows attackers to cause a crash, potentially enabling denial of service (crash, exit, or restart).
CVE-2021-25174
PUBLISHED: 2021-01-18
An issue was discovered in Open Design Alliance Drawings SDK before 2021.12. A memory corruption vulnerability exists when reading malformed DGN files. It can allow attackers to cause a crash, potentially enabling denial of service (Crash, Exit, or Restart).