Steve Gibson (47:28)
Oh wow. So last Tuesday the Microsoft Security community blog posted the under the title introducing Microsoft Security Store which starts out saying security is being re engineered because you know, we didn't get it right. The first time for the AI era. Of course, we had to get that in moving beyond static rule bound controls, an after the fact response toward platform LED machine speed defense. Oh, that all sounds wonderful. I wonder what it costs. We recognize that defending against modern threats requires the full strength of an ecosystem combining our unique expertise and shared threat intelligence. But with so many options out there, it's tough for security personnel professionals to cut through the noise. In fact, of course they're creating some more and even tougher to navigate long procurement cycles. Yeah, you don't want those. You just want to click a button and have it and stitch together tools and data before seeing meaningful improvements. That's why we built Microsoft Security Store, a storefront designed for security professionals to discover, buy and deploy security SSAs solutions and AI agents from our ecosystem partners such as Darktrace, Illumio and BlueVoyant Security. SaaS solutions and AI agents on security Store integrate with Microsoft security products including Sentinel platform to enhance end to end protection. These integrated solutions and agents collaborate intelligently, sharing insights and leveraging AI to enhance critical security tasks like triage. Wait, isn't that what happens after you get attacked anyway? Threat hunting and access management. So anyway, the page continues at some length describing how the Security Store essentially allows security professionals to browse, point, click, purchase, deploy and manage their cloud security more easily than ever before. No more waiting for those pesky purchasing cycles and authorizations. You know, just get what you need and start using Microsoft's new security Copilot solutions in minutes. So I have no doubt that we have many listeners who will probably find this new Microsoft packaging and deployment to be very useful. So I just wanted to make sure that those listeners were aware of this new facility. I am fortunate that I have nothing to do with Azure and why we'll be able to live out the rest of my life happily with that statement remaining true, I'm quite sure. Okay, so there's welcome news on the scalable vector graphics security front. Remember earlier this year the world saw a dramatic rise in the abuse of SVG format image files. To ours and many other people's surprise and astonishment, it turns out that SVG image files being formatted and formally defined as XML have always, from version 1.0 allowed, been allowed to contain JavaScript, which would be faithfully executed whenever the image was rendered by whatever was rendering it. Like unfortunately, people's email clients. So this capability pretty much sat idle for most of that image format's life, because SVG has been around for quite a while until it was recently rediscovered by malefactors and started being abused with increasing frequency. So much so that the, I mean, like everybody, all the security industry did articles on the the explosion in scalable vector graphics abuse. Various product vendors, you know, change the behavior of their SVG rendering code, you know, such as stripping out script tags and its related code before rendering the the images that were being described by the SVG files. And to that end, Microsoft has just announced that they are joining that group. They said, starting September 2025, outlook for web and new Outlook for Windows. Remember, there's the old Outlook for Windows and the new Outlook for Windows. So if you're on the old one, you're good luck. The new Outlook for Windows will stop displaying inline SVG images, meaning at all. They're not even going to show you the image, they're just like, no, they're going to instead show a blank space. They said this affects under 0.1% of images, improves security and requires no user action. SVG attachments remain supported organizations should update documentation and inform users. Okay, so images embedded in Outlook email so that they would normally be displayed. Like when you look at the email, that will no longer happen. You just get a little, you know, an empty rectangle. And this only applies to SVG images, which, as Microsoft correctly notes, accounts for a minuscule percentage of all email images. When any of us are sending images around in email, we're using GIFs, JPEGs and PNGs. That's your typical embedded email image format. So anyone who needs to send an email can attach an SVG file to the email. It will not be rendered, but it'll be there as an attachment. So tough luck, bad guys. You had what, nine months and then everyone finally responded. So unfortunately, nine months is quite a while. Still, Chrome has Advanced to version 141. The web functions that Chrome supports moved forward. There was something about wallet credentials being changed. I jumped on that thing. Oh, maybe this is wonderful. Turns out it was just an incremental little tweak. Nothing significant. There were two high, high priority vulnerabilities patched. The most severe of the two, which was patched in one 40, so it's been fixed in 141 was a heap buffer overflow in the web GPU component. The person who discovered that earned themselves $25,000. And I, I just. When I, whenever I see these bounties being paid by CRO, by Google and, and for, for, for Chrome, I think that's the right way to go. You absolutely need to incentivize the, the security researchers to, you know, spend some time looking around and they're finding things. The second critical or high priority vulnerability was also a heat buffer overflow, but that one was in the browser's video component and that earned its reporter $4,000. There was also a $5,000 bounty paid for a side channel information leakage which was found in the storage component. All told, 21 security problems were fixed and Google paid out a total, you know, that that 25K4 and an additional 5, a total of 49K to external security researchers. So anyway, it's just clear that the concept of paying researchers bounties for their responsible reporting of bugs is a winning strategy. I did want to also mention just because I saw this, as I mentioned before, one little more note about Google, specifically Gmail, not security related, but perhaps affecting some of our listeners. Starting January of next year, Google will be eliminating Gmail's POP fetching feature, which pulls email from other external accounts via pop, the Post Office protocol, into Gmail accounts. So Google recommends that users who wish to have their other email accounts sent to their Gmail inboxes instead of having Gmail pull it using POP to have their mail forwarded to Gmail in order to get the transfer. So push it from the recipient end rather than pulling it from the Gmail end. And in a move that I expect we're going to be seeing everyone adopt, actually a lot of companies have so far Google announced that their drive product for Windows and Mac OS has been enhanced now to detect and block ransomware. And of course, you know, they couldn't resist tossing in the fact that it's enhanced with AI because you know Leo, you sprinkle some AI on anything and.