 |
 |
|
March 17, 2006So how ARE you supposed to submit samples of malicious software or spyware to Microsoft?Microsoft has recently streamlined their process for receiving samples of malicious software or spyware, and I asked if it was ok to let everyone know about it. It's actually rather easy:
Note that these use @submit.microsoft.com now, rather than @microsoft.com. One reason for the change is to move the mail server they use for sample submissions outside of their corporate SPAM and virus filters. In the past they have had issues with sample submission e-mails getting filtered, particularly on the SPAM side. These addresses replace the old submission addresses:
As before, please use "False Positive" or "False Negative" in the mail subject line if possible to indicate the type of submission, and use password of 'infected' on the submitted .zip or .rar file. If you have any questions about this process let me know, and I will take it to the program manager in the Microsoft Antimalware Team. Have fun. Keep the samples coming. Microsoft loves them. Posted by SilverStr at March 17, 2006 10:44 PM | TrackBackComments
It might be worth noting that Microsoft also has an address for reporting security issues related to their software - particularly useful for people who discover bugs that might be exploitable to cause security incidents, and would like to see them fixed before they get exploited. The address is secure@microsoft.com. [This irritates many people who think it should be "security" just like many other vendors use, but Microsoft uses "security" for physical security related issues at Microsoft sites, such as "I've locked myself out of my car", or "someone's trying to pry the smart-card reader off the door to building 44". This use significantly predates the creation of a "security" mailing alias for vulnerability reporting, and Microsoft figured it would be easier to re-educate everyone who ever wants to post vulnerability details to Microsoft than it would be to re-educate their employees. Go figure.] Posted by: Alun Jones at March 20, 2006 08:24 AM |
 
My 5 Favorite Books
Writing Secure Code
Secure Programming Cookbook Security Engineering Secure Coding Principles & Practice Inside the Security Mind
My 5 Favorite Papers
Smashing the Stack
Penetration Studies Covert Channel Analysis of Trusted Systems DoD Trusted Computer System Evaluation Criteria NSA Security Recommendation Guides
Archives
March 2010
October 2009 August 2009 May 2009 April 2009 March 2009 February 2009 January 2009 December 2008 November 2008 October 2008 September 2008 August 2008 July 2008 June 2008 April 2008 January 2008 December 2007 November 2007 October 2007 September 2007 August 2007 July 2007 June 2007 May 2007 April 2007 March 2007 February 2007 January 2007 December 2006 November 2006 October 2006 September 2006 August 2006 July 2006 June 2006 May 2006 April 2006 March 2006 February 2006 January 2006 December 2005 November 2005 October 2005 September 2005 August 2005 July 2005 June 2005 May 2005 April 2005 March 2005 February 2005 January 2005 December 2004 November 2004 October 2004 September 2004 August 2004 July 2004 June 2004 May 2004 April 2004 March 2004 February 2004 January 2004 December 2003 November 2003 October 2003 September 2003 August 2003 July 2003 June 2003 May 2003 April 2003 March 2003 February 2003 January 2003 December 2002 November 2002 October 2002 September 2002 August 2002 July 2002 |
|
