5 comments
Optimizely Status site: <a href="https://status.optimizely.com/" rel="nofollow">https://status.optimizely.com/</a><p>Currently says "Partial Outage Affecting Recommendations Tracking and Reporting"
Let’s say I use Optimizely (I don’t), is there a good best practice to say?:<p>“yeah load this JS m, but it can’t load / random other JS referencing sketchy places”
Yes: <a href="https://developer.mozilla.org/en-US/docs/Web/Security/Defenses/Subresource_Integrity" rel="nofollow">https://developer.mozilla.org/en-US/docs/Web/Security/Defens...</a>
In theory yes, in practice no since every SaaS wants to ship 5 times a day and add 15 new dependencies on other SaaS providers each release, and marketing wants to load gobs of 3rd party tracking and analytics code from their favorite SaaS of the day without having to get approval from those pesky security people. Let's not even mention ad networks.
Unfortunate with this nonsense slop report for a seemingly significant event like this.<p>> Your origin can be clean while your visitors are robbed — the compromise sits in the tag layer.
[flagged]
[flagged]