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 //

Vulnerability Management

1/4/2019
03:35 PM

How Intel Has Responded to Spectre and Meltdown

In a newly published editorial and video, Intel details what specific actions it has taken in the wake of the discovery of the CPU vulnerabilities.
2 of 7

The Intel Product Assurance and Security (IPAS) Group
One of Intel's first public statements after the disclosure was its statement of a Security First Pledge. One of the ways in which it brought that pledge into the real world was through the creation of the Intel Product Assurance and Security Group.
In the statement announcing the creation of the group, its general manager, Leslie Culbertson, wrote, 'IPAS is designed to serve as a center of security excellence -- a sort of mission control -- that looks across all of Intel. Beyond addressing the security issues of today, we are looking longer-term at the evolving threat landscape and continuously improving product security in the years ahead.'
In its response to the speculative execution vulnerabilities, Intel has also increased its emphasis on security across all its product lines. It has created groups like STORM - the strategic offensive research and mitigation group, to conduct research on security across its chips and systems. In conducting its own offensive research, Intel is trying to move beyond points like those raised by Richard Ford, chief scientist at Forcepoint, who said that Intel (and other vendors) had found themselves creating ad hoc, point mitigations rather than long-term fixes. They were, he said, '...waiting until a researcher comes up with a new vulnerability of this type and responding to it, rather than trying to put an end to the entire line of vulnerabilities.'
(Image: Bru-n0 VIA Pixabay)

The Intel Product Assurance and Security (IPAS) Group

One of Intel's first public statements after the disclosure was its statement of a Security First Pledge. One of the ways in which it brought that pledge into the real world was through the creation of the Intel Product Assurance and Security Group.

In the statement announcing the creation of the group, its general manager, Leslie Culbertson, wrote, "IPAS is designed to serve as a center of security excellence - a sort of mission control - that looks across all of Intel. Beyond addressing the security issues of today, we are looking longer-term at the evolving threat landscape and continuously improving product security in the years ahead."

In its response to the speculative execution vulnerabilities, Intel has also increased its emphasis on security across all its product lines. It has created groups like STORM the strategic offensive research and mitigation group, to conduct research on security across its chips and systems. In conducting its own offensive research, Intel is trying to move beyond points like those raised by Richard Ford, chief scientist at Forcepoint, who said that Intel (and other vendors) had found themselves creating ad hoc, point mitigations rather than long-term fixes. They were, he said, "waiting until a researcher comes up with a new vulnerability of this type and responding to it, rather than trying to put an end to the entire line of vulnerabilities."

(Image: Bru-n0 VIA Pixabay)

2 of 7
Comment  | 
Print  | 
Comments
Newest First  |  Oldest First  |  Threaded View
How Attackers Infiltrate the Supply Chain & What to Do About It
Shay Nahari, Head of Red-Team Services at CyberArk,  7/16/2019
US Mayors Commit to Just Saying No to Ransomware
Robert Lemos, Contributing Writer,  7/16/2019
The Problem with Proprietary Testing: NSS Labs vs. CrowdStrike
Brian Monkman, Executive Director at NetSecOPEN,  7/19/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Building and Managing an IT Security Operations Program
As cyber threats grow, many organizations are building security operations centers (SOCs) to improve their defenses. In this Tech Digest you will learn tips on how to get the most out of a SOC in your organization - and what to do if you can't afford to build one.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-12551
PUBLISHED: 2019-07-22
In SweetScape 010 Editor 9.0.1, improper validation of arguments in the internal implementation of the Memcpy function (provided by the scripting engine) allows an attacker to overwrite arbitrary memory, which could lead to code execution.
CVE-2019-12552
PUBLISHED: 2019-07-22
In SweetScape 010 Editor 9.0.1, an integer overflow during the initialization of variables could allow an attacker to cause a denial of service.
CVE-2019-3414
PUBLISHED: 2019-07-22
All versions up to V1.19.20.02 of ZTE OTCP product are impacted by XSS vulnerability. Due to XSS, when an attacker invokes the security management to obtain the resources of the specified operation code owned by a user, the malicious script code could be transmitted in the parameter. If the front en...
CVE-2019-10102
PUBLISHED: 2019-07-22
tcpdump.org tcpdump 4.9.2 is affected by: CWE-126: Buffer Over-read. The impact is: May expose Saved Frame Pointer, Return Address etc. on stack. The component is: line 234: "ND_PRINT((ndo, "%s", buf));", in function named "print_prefix", in "print-hncp.c". Th...
CVE-2019-10102
PUBLISHED: 2019-07-22
aubio 0.4.8 and earlier is affected by: null pointer. The impact is: crash. The component is: filterbank. The attack vector is: pass invalid arguments to new_aubio_filterbank. The fixed version is: after commit eda95c9c22b4f0b466ae94c4708765eaae6e709e.