Thursday, October 20, 2005
Hey Andrew Cushman here. I work in the Security Technology Unit. My team is focused on outreach to the security researcher community. Our roots are in MSRC – we started a couple years ago focused on “finders” (researchers that report bugs to MSRC). The goal was to figure out how those researchers and Microsoft could communicate and work together more effectively.
Monday, October 17, 2005
Mike Nash here – this is actually the first time that I’ve posted on the blog. You’ve probably heard that we recently made some announcements around our security strategy with Steve Ballmer in the past couple weeks. I thought it was the perfect occasion for me to join in on the blogging and fill you in a little more about what we did.
Monday, October 17, 2005
Hi everyone, wanted to point out that Friday we published a security advisory just to make sure people were getting the information on problems after installing 051 that Mike blogged about previously. Here’s the link. There’s not a lot new, we just wanted to make sure it was getting the proper visibility.
Friday, October 14, 2005
Hey everyone, Mike Reavey here. Wanted to drop everyone a note that yes we are aware of some of the information floating around about problems after installing the MS05-051 update on Windows 2000 systems. We’ve investigated this and here’s what we have found. In cases where the default permissions on the COM+ catalog directory and files have been changed from the default settings, various problems might occur after applying the MS05-051 update (such as The Windows Installer service may not start or the Windows Firewall Service may not start or the Network Connections folder is empty).
Thursday, October 13, 2005
Hi everyone, Stephen Toulouse here. There’s been a lot of talk today about exploit code, specifically around security bulletins MS05-051 and MS05-046. The good news is that we’re not aware at this time of any exploit code being available publicly. Currently we’ve been told the exploit code is only available through third party fee-based security offerings.
Tuesday, October 11, 2005
Like greased lightnin’. Granted I don’t have overhead lifters or a four speed on the floor, nevertheless today was systematic . Nine bulletins requires that a lot of pieces come together. Hands down this was the smoothest release based on “pain” to bulletin ratio I can remember. Plus my trusty companion, vente almond mocha helped too.
Thursday, October 06, 2005
Hey folks, Mike Reavey here, I wanted to take a quick second to make sure everyone saw the Advance Notification for the Security Bulletin release for this October. This coming Tuesday, we’re planning to release nine security bulletins, and they are being released in Windows with one affecting Exchange Server as well.
Thursday, October 06, 2005
Hi everyone, Stephen Toulouse here. Back from a nice vacation and wanted to stop and just jot a quick note about Steve Ballmer and Mike Nash’s respective speeches today where they detailed a number of new products and partnerships relating to security. You can get the full details here. Specific Q&A’s around Microsoft Client Protection and the SecureIT Alliance are available here and here.
Tuesday, September 27, 2005
Hi all- Alexandra Huft here again! I thought you might find it interesting to see “behind the scenes” of how a security vulnerability eventually becomes a security bulletin. So, I’ll start way back at the beginning. We receive reports from many different finders on issues that may or may not be a vulnerability.
Thursday, September 15, 2005
It’s been 10 years since I did any hands-on dev work. However working in the security space at Microsoft, “SDL” or the Security Development Lifecycle is very visible and obviously important to even those not directly involved in development. We had the opportunity here in LA to share with customers how Microsoft took BillG’s edict that security should be our top priority, and over the past couple of years re-engineer our entire development process to implement this vision at every level - from design through to post-release maintenance.
