<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Cyren-SentinelOne Threat Intelligence on sentinelchangelog.net</title><link>http://sentinelchangelog.net/tags/cyren-sentinelone-threat-intelligence/</link><description>Recent content in Cyren-SentinelOne Threat Intelligence on sentinelchangelog.net</description><generator>Hugo -- 0.157.0</generator><language>en</language><lastBuildDate>Tue, 07 Apr 2026 13:22:30 +0000</lastBuildDate><atom:link href="http://sentinelchangelog.net/tags/cyren-sentinelone-threat-intelligence/index.xml" rel="self" type="application/rss+xml"/><item><title>Cyren-SentinelOne Connector: Restoring Threat Intelligence Deployment After ARM Template Failure</title><link>http://sentinelchangelog.net/posts/2026-04-07-pr-13990/</link><pubDate>Tue, 07 Apr 2026 13:22:30 +0000</pubDate><guid>http://sentinelchangelog.net/posts/2026-04-07-pr-13990/</guid><description>Critical deployment fix for Cyren-SentinelOne connector that was failing ARM template validation in Content Hub, preventing threat intelligence data ingestion.</description></item><item><title>Cyren-SentinelOne Playbook: Credential Parameter Security Compliance Fix</title><link>http://sentinelchangelog.net/posts/2026-03-30-pr-13945/</link><pubDate>Mon, 30 Mar 2026 14:09:23 +0000</pubDate><guid>http://sentinelchangelog.net/posts/2026-03-30-pr-13945/</guid><description>Fixed Policy 300.4.1.1 violation by securing credential parameters in the Cyren-SentinelOne threat intelligence integration Playbook.</description></item></channel></rss>