The Stuxnet buzz continued this week, Adobe took a few steps toward better security and Microsoft announced plans for its largest Patch Tuesday ever. But it wasn’t just Microsoft, Adobe and everyone’s favorite worm grabbing headlines. Read on for the full week in review.
\nNot going away anytime soon; Stuxnet continued to pervade the news this week. On Monday, an editorial took a step back and examined the story so far, looking at the roots of the attack and potential targets. While the virus\u2019 alleged ties to Iran and Israel have certainly been well publicized, that\u2019s only one potentially valid explanation for it.<\/p>\n
<\/p>\n
After all, on Tuesday we discovered Iran is no longer the virus\u2019 hot spot \u2013 a title that now belongs to India and some parts of Indonesia. That\u2019s what a slice of data released by Kaspersky Lab\u2019s September report suggests. Regardless, the debate on the worm\u2019s intended target will continue to rage on, it seems.<\/p>\n
As a new month began, details came late this week on Microsoft\u2019s impending Patch Tuesday. The batch of patches, scheduled for release on Oct. 12, will be the company\u2019s largest, with 16 bulletins addressing 49 security vulnerabilities. Four of the 16 vulnerabilities are rated critical, the company\u2019s highest severity rating.<\/p>\n
The start of October also meant it was time for Adobe\u2019s quarterly patch update. In the huge update, 23 vulnerabilities were patched on Tuesday, a full week earlier than they\u2019d originally planned. The update fixed previously critical issues in Reader and Acrobat, some which had been exploited for up to two months.<\/p>\n
The software company also produced some good news on Wednesday by divulging new details about their upcoming version of Reader, its sandboxing feature called Protected Mode. Initially announced back in July, Protected Mode was described by Adobe\u2019s Kyle Randolph as being able to lessen the effect of bugs in the application.<\/p>\n
Microsoft floated a new security proposal this week, outlining a plan wherein computers would all receive \u201chealth certificates\u201d in order to access the Internet. Almost like a public health model for security, the idea is meant\u00a0 to prevent infected PCs from spreading malware and becoming parts of botnets by stopping infected machines from accessing the Internet.<\/p>\n
There were also stories this week that touched on keeping your e-mail safe, particularly if you use Google\u2019s tremendously popular Gmail. In a guest column early this week, Caleb Sima of Armorize gave some hints on how to keep your Gmail secure. As changing the password doesn\u2019t always work \u2013 Sima also recommended paying attention to filters, password recovery settings and rogue applications.<\/p>\n
As the week wound down, Google, which has been fighting an uphill battle lately, released a checklist of their own in hopes of keeping users safe. Google lays out 18 steps that users can take to help lock down their Gmail accounts, ranging from changing passwords frequently to using the forced-SSL option to checking for outdated or insecure browser add-ons and plug-ins.<\/p>\n
What caught your interest this week?<\/p>\n","protected":false},"excerpt":{"rendered":"
The Stuxnet buzz continued this week, Adobe took a few steps toward better security and Microsoft announced plans for its largest Patch Tuesday ever. But it wasn’t just Microsoft, Adobe…<\/p>\n","protected":false},"author":439,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_seopress_robots_primary_cat":"","_seopress_titles_title":"","_seopress_titles_desc":"","_seopress_robots_index":"","jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[3],"tags":[66,117,101,116,2866,115],"class_list":["post-934","post","type-post","status-publish","format-standard","hentry","category-security","tag-gmail","tag-monster","tag-patch","tag-redux","tag-security","tag-stuxnet"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p4bBYZ-f4","_links":{"self":[{"href":"https:\/\/deepquest.code511.com\/blog\/wp-json\/wp\/v2\/posts\/934","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/deepquest.code511.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/deepquest.code511.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/deepquest.code511.com\/blog\/wp-json\/wp\/v2\/users\/439"}],"replies":[{"embeddable":true,"href":"https:\/\/deepquest.code511.com\/blog\/wp-json\/wp\/v2\/comments?post=934"}],"version-history":[{"count":6,"href":"https:\/\/deepquest.code511.com\/blog\/wp-json\/wp\/v2\/posts\/934\/revisions"}],"predecessor-version":[{"id":937,"href":"https:\/\/deepquest.code511.com\/blog\/wp-json\/wp\/v2\/posts\/934\/revisions\/937"}],"wp:attachment":[{"href":"https:\/\/deepquest.code511.com\/blog\/wp-json\/wp\/v2\/media?parent=934"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/deepquest.code511.com\/blog\/wp-json\/wp\/v2\/categories?post=934"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/deepquest.code511.com\/blog\/wp-json\/wp\/v2\/tags?post=934"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}