0001193125-11-070159.txt : 20110317 0001193125-11-070159.hdr.sgml : 20110317 20110317171821 ACCESSION NUMBER: 0001193125-11-070159 CONFORMED SUBMISSION TYPE: 8-K PUBLIC DOCUMENT COUNT: 3 CONFORMED PERIOD OF REPORT: 20110317 ITEM INFORMATION: Other Events ITEM INFORMATION: Financial Statements and Exhibits FILED AS OF DATE: 20110317 DATE AS OF CHANGE: 20110317 FILER: COMPANY DATA: COMPANY CONFORMED NAME: EMC CORP CENTRAL INDEX KEY: 0000790070 STANDARD INDUSTRIAL CLASSIFICATION: COMPUTER STORAGE DEVICES [3572] IRS NUMBER: 042680009 STATE OF INCORPORATION: MA FISCAL YEAR END: 1231 FILING VALUES: FORM TYPE: 8-K SEC ACT: 1934 Act SEC FILE NUMBER: 001-09853 FILM NUMBER: 11695882 BUSINESS ADDRESS: STREET 1: 176 SOUTH STREET CITY: HOPKINTON STATE: MA ZIP: 01748-9103 BUSINESS PHONE: 5082937208 MAIL ADDRESS: STREET 1: 176 SOUTH STREET CITY: HOPKINTON STATE: MA ZIP: 01748-9103 8-K 1 d8k.htm FORM 8-K Form 8-K

 

 

UNITED STATES

SECURITIES AND EXCHANGE COMMISSION

WASHINGTON, D.C. 20549

 

 

FORM 8-K

 

 

CURRENT REPORT

PURSUANT TO SECTION 13 OR 15 (d) OF THE

SECURITIES EXCHANGE ACT OF 1934

Date of report (Date of earliest event reported): March 17, 2011

 

 

EMC CORPORATION

(Exact Name of Registrant as Specified in Charter)

 

 

 

Massachusetts   1-9853   No. 04-2680009

(State or Other Jurisdiction

of Incorporation)

 

(Commission

File Number)

 

(I.R.S. Employer

Identification No.)

 

176 South Street, Hopkinton, MA   01748
(Address of Principal Executive Offices)   (Zip code)

Registrant’s telephone number, including area code: (508) 435-1000

N/A

(Former Name or Former Address, if changed since last report)

 

 

Check the appropriate box below if the Form 8-K filing is intended to simultaneously satisfy the filing obligation of the registrant under any of the following provisions (see General Instruction A.2. below):

 

¨ Written communications pursuant to Rule 425 under the Securities Act (17 CFR 230.425)

 

¨ Soliciting material pursuant to Rule 14a-12 under the Exchange Act (17 CFR 240.14a-12)

 

¨ Pre-commencement communications pursuant to Rule 14d-2(b) under the Exchange Act (17 CFR 240.14d-2(b))

 

¨ Pre-commencement communications pursuant to Rule 13e-4(c) under the Exchange Act (17 CFR 240.13e-4(c))

 

 

 


Item 8.01. Other Events.

On March 17, 2011, RSA, the Security Division of EMC (“RSA”), posted an open letter from Arthur W. Coviello, Jr., Executive Chairman, RSA, to its customers on its website and issued a SecurCare Online note directly to its customers. Based on what EMC Corporation (“EMC”) currently knows, EMC does not believe that the matter described in the letter and note will have a material impact on its financial results. The letter and note are being furnished as Exhibit 99.1 and Exhibit 99.2 hereto and are incorporated by reference herein.

Item 9.01. Financial Statements and Exhibits.

(d) Exhibits

 

99.1    Open letter from Arthur W. Coviello, Jr., Executive Chairman, RSA, the Security Division of EMC, to RSA customers dated March 17, 2011
99.2    RSA SecurCare Online note dated March 17, 2011

 

2


SIGNATURES

Pursuant to the requirements of the Securities Exchange Act of 1934, the registrant has duly caused this report to be signed on its behalf by the undersigned hereunto duly authorized.

 

EMC CORPORATION
By:  

/s/ Paul T. Dacier

  Paul T. Dacier
  Executive Vice President and
  General Counsel

Date: March 17, 2011

 

3


EXHIBIT INDEX

 

Exhibit
No.

  

Description

99.1    RSA SecurCare Online Note dated March 17, 2011
99.2    Open letter from Arthur W. Coviello, Jr., Executive Chairman, RSA, the Security Division of EMC, to RSA customers dated March 17, 2011
EX-99.1 2 dex991.htm OPEN LETTER Open Letter

Exhibit 99.1

Open Letter to RSA Customers

Like any large company, EMC experiences and successfully repels multiple cyber attacks on its IT infrastructure every day. Recently, our security systems identified an extremely sophisticated cyber attack in progress being mounted against RSA. We took a variety of aggressive measures against the threat to protect our business and our customers, including further hardening our IT infrastructure. We also immediately began an extensive investigation of the attack and are working closely with the appropriate authorities.

Our investigation has led us to believe that the attack is in the category of an Advanced Persistent Threat (APT). Our investigation also revealed that the attack resulted in certain information being extracted from RSA’s systems. Some of that information is specifically related to RSA’s SecurID two-factor authentication products. While at this time we are confident that the information extracted does not enable a successful direct attack on any of our RSA SecurID customers, this information could potentially be used to reduce the effectiveness of a current two-factor authentication implementation as part of a broader attack. We are very actively communicating this situation to RSA customers and providing immediate steps for them to take to strengthen their SecurID implementations.

We have no evidence that customer security related to other RSA products has been similarly impacted. We are also confident that no other EMC products were impacted by this attack. It is important to note that we do not believe that either customer or employee personally identifiable information was compromised as a result of this incident.

Our first priority is to ensure the security of our customers and their trust. We are committed to applying all necessary resources to give our SecurID customers the tools, processes and support they require to strengthen the security of their IT systems in the face of this incident. Our full support will include a range of RSA and EMC internal resources as well as close engagement with our partner ecosystems and our customers’ relevant partners.

We regret any inconvenience or concern that this attack on RSA may cause for customers, and we strongly urge you to follow the steps we’ve outlined in our SecurCare Online note. APT threats are becoming a significant challenge for all large corporations, and it’s a topic I have discussed publicly many times. As appropriate, we will share our experiences from these attacks with our customers, partners and the rest of the security vendor ecosystem and work in concert with these organizations to develop means to better protect all of us from these growing and ever more sophisticated forms of cyber security threat.

Sincerely,

/s/ Art Coviello

Art Coviello

Executive Chairman

EX-99.2 3 dex992.htm RSA SECURCARE ONLINE NOTE RSA SecurCare Online Note

Exhibit 99.2

SCOL Note Title: Required Actions for SecurID Installations

Dear RSA SecurCare® Online Customer,

Summary:

We have determined that a recent attack on RSA’s systems has resulted in certain information being extracted from RSA’s systems that relates to RSA’s SecurID two-factor authentication products. While at this time we are confident that the information extracted does not enable a successful direct attack on any of our RSA SecurID customers, this information could potentially be used to reduce the effectiveness of a current two-factor authentication implementation as part of a broader attack. RSA urges immediate action.

Description:

Recently EMC’s security systems identified an extremely sophisticated cyber attack in progress, targeting our RSA business unit. We took a variety of aggressive measures against the threat to protect our business and our customers, including further hardening of our IT infrastructure. We also immediately began an extensive investigation of the attack and are working closely with the appropriate authorities.

Our investigation has revealed that the attack resulted in certain information being extracted from RSA’s systems. Some of that information is related to RSA’s SecurID two-factor authentication products. While at this time we are confident that the information extracted does not enable a successful direct attack on any of our RSA SecurID customers, this information could potentially be used to reduce the effectiveness of a current two-factor authentication implementation as part of a broader attack.

We strongly urge immediate customer attention to this advisory, and we are providing immediate remediation steps for customers to take to strengthen their RSA SecurID implementations.

Affected Products:

The affected products are RSA SecurID implementations.

Overall Recommendations:

RSA strongly urges customers to follow both these overall recommendations and the recommendations available in the best practices guides linked to this note.

 

   

We recommend customers increase their focus on security for social media applications and the use of those applications and websites by anyone with access to their critical networks.

 

   

We recommend customers enforce strong password and pin policies.

 

   

We recommend customers follow the rule of least privilege when assigning roles and responsibilities to security administrators.


   

We recommend customers re-educate employees on the importance of avoiding suspicious emails, and remind them not to provide user names or other credentials to anyone without verifying that person’s identity and authority. Employees should not comply with email or phone-based requests for credentials and should report any such attempts.

 

   

We recommend customers pay special attention to security around their active directories, making full use of their SIEM products and also implementing two-factor authentication to control access to active directories.

 

   

We recommend customers watch closely for changes in user privilege levels and access rights using security monitoring technologies such as SIEM, and consider adding more levels of manual approval for those changes.

 

   

We recommend customers harden, closely monitor, and limit remote and physical access to infrastructure that is hosting critical security software.

 

   

We recommend customers examine their help desk practices for information leakage that could help an attacker perform a social engineering attack.

 

   

We recommend customers update their security products and the operating systems hosting them with the latest patches.

For RSA product-specific recommendations, please follow the links below to the Security Best Practices Guides for each product. If you are unable to access the files via RSA SecurCare, please contact support at:

U.S.: 1-800-782-4362, Option #5 for RSA, Option #1 for SecurCare note

Canada: 1-800-543-4782, Option #5 for RSA, Option #1 for SecurCare note

International: +1-508-497-7901, Option #5 for RSA, Option #1 for SecurCare note