Insights & updates from our experts
Preventing Insecure Content
It is no longer be possible to create or update records if they contain insecure links in their HTML, JavaScript or CSS fields.

Any pre-existing insecure content will continue to work for now. To help customers prepare and migrate any insecure content, the account owners will receive an email with a list of records that are registered in their account and that include one or more links to insecure content.

This list is a JSON file attachment that should make it fairly easy to find the offending content.

The insecure content can be migrated to a secured web server or Xurrent’s Media Library to ensure that it continues to work once the Content Security Policy (CSP) is enforced. Note that from now on, the CSP will already be enforced for every new Xurrent account.

An AI SRE that knows your incidents
Most AI SREs are pattern matchers trained on public data. They know what a memory leak looks like in the abstract. They don't know that your payments-api has a flaky liveness probe everyone ignores, that the checkout team owns the retry policy, or that the last three "database incidents" were actually cache misconfigurations. That knowledge lives in your postmortems, your Slack channels, and the heads of two senior engineers.

How Long Should ITSM Implementation Really Take in 2026?
Most vendors will tell you ITSM implementation takes six months to a year — but modern, configuration-first platforms have rewritten the math entirely. See what real implementations look like in 2026, and why a long rollout is now a choice, not a given.















.webp)
.webp)


.webp)











