Comments on: HauteSecure – Good idea, bad implementation http://www.mikeonads.com/2007/07/11/hautesecure-good-idea-bad-implementation/ Ramblings about online advertising, ad networks & other techie randomness Wed, 28 May 2014 09:36:00 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: repair powerpoint files http://www.mikeonads.com/2007/07/11/hautesecure-good-idea-bad-implementation/comment-page-1/#comment-147526 repair powerpoint files Thu, 24 May 2012 10:30:00 +0000 http://www.mikeonads.com/2007/07/11/hautesecure-good-idea-bad-implementation/#comment-147526 Great post Nice one thanks. Great post Nice one thanks.

]]>
By: repair powerpoint files http://www.mikeonads.com/2007/07/11/hautesecure-good-idea-bad-implementation/comment-page-1/#comment-147527 repair powerpoint files Thu, 24 May 2012 10:30:00 +0000 http://www.mikeonads.com/2007/07/11/hautesecure-good-idea-bad-implementation/#comment-147527 Great post Nice one thanks. Great post Nice one thanks.

]]>
By: corrupt zip repair http://www.mikeonads.com/2007/07/11/hautesecure-good-idea-bad-implementation/comment-page-1/#comment-147340 corrupt zip repair Wed, 07 Mar 2012 07:03:00 +0000 http://www.mikeonads.com/2007/07/11/hautesecure-good-idea-bad-implementation/#comment-147340 Nice post, thanks. I really love it! Nice post, thanks. I really love it!

]]>
By: Sandi Hardmeier http://www.mikeonads.com/2007/07/11/hautesecure-good-idea-bad-implementation/comment-page-1/#comment-2352 Sandi Hardmeier Sat, 14 Jul 2007 09:58:51 +0000 http://www.mikeonads.com/2007/07/11/hautesecure-good-idea-bad-implementation/#comment-2352 Hi Mike, The service is in early beta at the moment - in fact, it wasn't made available to the public until a few days ago - this is something that needs to be kept in mind when assessing the service as it stands today - I know that those behind Haute Secure want any and all feedback regarding their service, and I'll be making a point of bringing your blog to their attention, but personally I prefer to emphasise that a service is in beta when writing about it so that the final product is not judged on writings about early builds :o) You and I have expressed similar concerns. I have been having an ongoing dialogue with those behind Haute re things such as the product's chattiness and my concerns about the flagging of entire domains on the basis of past incidents - hopefully things will improve if more emphasis is placed on *content* warnings and they are made easier to distinguish from *domain* warnings. I worry that wholesale warnings triggered by domains will lead to Haute Secure eventually being ignored (something I have shared with the team). That being said, we are facing some real problems such as COLOs when they run old or badly configured servers which leads to hundreds, if not thousands, of sites being compromised and hostile code inserted for the express purpose of infecting visitors. Then there are the numerous dangerous domains that all point to the same IP address. In such situations I would be more than happy for an entire IP range to trigger a domain warning because it's likely to be more effective than trying to block thousands of individual web sites at as COLO. The same can be said for services like myspace which can have hundreds if not thousands of pages that have been compromised. Sometimes it is easier to warn about the entire domain which has been the source of recurring problems than to try and track down and block thousands of individual URLS. The URLs you mention as being marked as 'safe' are a problem (as we both so well know) :o) But, Haute is based around behavioural analysis - and its purpose is to try and warn us of sites that are trying to do something bad (as distinct to offering betrayware for download) so if the site is not being seen to actively try to install malware on a system without user interaction then they may fall outside the scope of the product as it stands today - and you and I both know how good those behind winfixer are at evading detection. You may find these articles interesting: http://community.hautesecure.com/forums/p/27/30.aspx#30 http://community.hautesecure.com/blogs/company/archive/2007/07/12/the-details-on-beta-build-419-rtw-of-haute-secure.aspx http://community.hautesecure.com/forums/t/29.aspx As always, my best wishes, Sandi &c. Hi Mike,

The service is in early beta at the moment – in fact, it wasn’t made available to the public until a few days ago – this is something that needs to be kept in mind when assessing the service as it stands today – I know that those behind Haute Secure want any and all feedback regarding their service, and I’ll be making a point of bringing your blog to their attention, but personally I prefer to emphasise that a service is in beta when writing about it so that the final product is not judged on writings about early builds :o )

You and I have expressed similar concerns. I have been having an ongoing dialogue with those behind Haute re things such as the product’s chattiness and my concerns about the flagging of entire domains on the basis of past incidents – hopefully things will improve if more emphasis is placed on *content* warnings and they are made easier to distinguish from *domain* warnings.

I worry that wholesale warnings triggered by domains will lead to Haute Secure eventually being ignored (something I have shared with the team).

That being said, we are facing some real problems such as COLOs when they run old or badly configured servers which leads to hundreds, if not thousands, of sites being compromised and hostile code inserted for the express purpose of infecting visitors. Then there are the numerous dangerous domains that all point to the same IP address. In such situations I would be more than happy for an entire IP range to trigger a domain warning because it’s likely to be more effective than trying to block thousands of individual web sites at as COLO.

The same can be said for services like myspace which can have hundreds if not thousands of pages that have been compromised. Sometimes it is easier to warn about the entire domain which has been the source of recurring problems than to try and track down and block thousands of individual URLS.

The URLs you mention as being marked as ‘safe’ are a problem (as we both so well know) :o ) But, Haute is based around behavioural analysis – and its purpose is to try and warn us of sites that are trying to do something bad (as distinct to offering betrayware for download) so if the site is not being seen to actively try to install malware on a system without user interaction then they may fall outside the scope of the product as it stands today – and you and I both know how good those behind winfixer are at evading detection.

You may find these articles interesting:

http://community.hautesecure.com/forums/p/27/30.aspx#30

http://community.hautesecure.com/blogs/company/archive/2007/07/12/the-details-on-beta-build-419-rtw-of-haute-secure.aspx

http://community.hautesecure.com/forums/t/29.aspx

As always, my best wishes,

Sandi &c.

]]>
By: steve http://www.mikeonads.com/2007/07/11/hautesecure-good-idea-bad-implementation/comment-page-1/#comment-2260 steve Thu, 12 Jul 2007 02:00:57 +0000 http://www.mikeonads.com/2007/07/11/hautesecure-good-idea-bad-implementation/#comment-2260 Mike, Thanks for the feedback. It appears our design goals for this version are not clear. This release is designed to prevent users from malware attacks delivered by drive-by exploits. As you probably know, there is virtually no protection today whatsoever against them. We created a solution to do this in two ways: the first is the Haute Secure client on your PC that stops malicious code from executing without a user’s permission. The second is the constantly updated malicious link database that stops the delivery of malicious code by blocking links known to be laced with malware. For example, if you were to browse to winfixer.com, and it tried to exploit your browser (or a 3rd party plugin) to install malware, this would be something Haute Secure catches and stops. If it asks the user for explicit permission to download winfixer and the user clicks “yes”, we do not currently protect from that. It holds then that the results we gave you are correct: those sites listed as dangerous have indeed been caught and verified as delivering (via drive by exploits) malicious code on unsuspecting users’ PCs. If you have had a chance to use the product, you’ll see that we do not block the popular sites that we found are distributing malware. Rather, we give you notice that we found malware on them and will stop drive-by exploits lurking on them as you browse the site. Protecting users who click “yes” and become infected is a separate problem space and we have plans to address it with the same approach in the future. In the near term, we will enable members in the community such as yourself to contribute links like winfixer.com to the block lists. That way we’re blocking the page from loading and keeping people away from the temptation of downloading malicious code. With respect to analyzing script, I agree that this is an approach to the problem. There are other products on the market that do this, but as a general rule, they require signatures of the exploit code to work. Haute Secure is behavior-based, and therefore requires no signatures and can detect infection attempts from exploitation of 0-day vulnerabilities. Please keep in mind that this is a beta release. Your continued constructive criticism will help us improve future releases of this product. Thanks again for the feedback. Steve Mike,

Thanks for the feedback. It appears our design goals for this version are not clear. This release is designed to prevent users from malware attacks delivered by drive-by exploits. As you probably know, there is virtually no protection today whatsoever against them. We created a solution to do this in two ways: the first is the Haute Secure client on your PC that stops malicious code from executing without a user’s permission. The second is the constantly updated malicious link database that stops the delivery of malicious code by blocking links known to be laced with malware. For example, if you were to browse to winfixer.com, and it tried to exploit your browser (or a 3rd party plugin) to install malware, this would be something Haute Secure catches and stops. If it asks the user for explicit permission to download winfixer and the user clicks “yes”, we do not currently protect from that.

It holds then that the results we gave you are correct: those sites listed as dangerous have indeed been caught and verified as delivering (via drive by exploits) malicious code on unsuspecting users’ PCs. If you have had a chance to use the product, you’ll see that we do not block the popular sites that we found are distributing malware. Rather, we give you notice that we found malware on them and will stop drive-by exploits lurking on them as you browse the site.

Protecting users who click “yes” and become infected is a separate problem space and we have plans to address it with the same approach in the future. In the near term, we will enable members in the community such as yourself to contribute links like winfixer.com to the block lists. That way we’re blocking the page from loading and keeping people away from the temptation of downloading malicious code.

With respect to analyzing script, I agree that this is an approach to the problem. There are other products on the market that do this, but as a general rule, they require signatures of the exploit code to work. Haute Secure is behavior-based, and therefore requires no signatures and can detect infection attempts from exploitation of 0-day vulnerabilities.

Please keep in mind that this is a beta release. Your continued constructive criticism will help us improve future releases of this product. Thanks again for the feedback.

Steve

]]>