Digital Learnings in Sitecore & Cloud

In a project where we're implementing Content Hub, there in a PIM system which is used to manage products that feed into various downstream systems. Content Hub is to be the new source of truth for Digital Assets, and this will include all product images. We already have various entities mastered in other systems including PIM such as products and categories bing syncrhonised into Content Hub as taxonomies that will enable tagging of Digital Assets to assist in organising them. This integration is done via Mulesoft with the PIM system raising an event when an individual product/category is changed, with a Mulesfot subscriber responding to the event and pushing the change to Content Hub via it's REST interface . In our case we want the association of product images with products in Content Hub to control what images are shown for products in downsteram systems. This means that data will flow from Content Hub back through Mulesoft and into PIM. PIM then manages the flow of ...

As with any publicly (or internally) accessible web application, it is vitally important to make sure that your Sitecore installation is appropriately configured to protect it against attacks from malicious forces on the net. The primary reference to follow when configuring the security of your Sitecore instance is of course the Sitecore Security Hardening Guide .  However there are a few additional steps that you should consider following when configuring Sitecore to provide additional security against some known attack vectors where your Sitecore installation may be vulnerable.  All the recommendations and issues listed below appear to still be valid as of Sitecore v7.1 Extra restrictions on the /sitecore folder on delivery servers The Hardening Guide recommends restricting Anonymous user access to the /sitecore/admin , /sitecore/debug and /sitecore/shell/WebService folders.   My recommendation on delivery server instances is to go further and restrict anonymou...