<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Alerts when Lockdown blocks something on Root Lock by HeartSuite</title><link>https://heartsecsuite.com/rootlock/alerts/</link><description>Recent content in Alerts when Lockdown blocks something on Root Lock by HeartSuite</description><generator>Hugo</generator><language>en</language><atom:link href="https://heartsecsuite.com/rootlock/alerts/index.xml" rel="self" type="application/rss+xml"/><item><title>Pipe Lockdown blocks into the SIEM you already run</title><link>https://heartsecsuite.com/rootlock/alerts/siem-integration/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://heartsecsuite.com/rootlock/alerts/siem-integration/</guid><description>&lt;p&gt;&lt;strong&gt;Overview&lt;/strong&gt;: Root Lock by HeartSuite integrates with your existing SIEM, EDR, and observability stack via syslog (journald/rsyslog) and webhook. Configure once in Alert Settings → Fleet, and let your central tooling handle monitoring, correlation, and alerting. There is no requirement to run the Dashboard on every host for day-to-day fleet visibility.&lt;/p&gt;
&lt;p&gt;Raw &lt;strong&gt;denial&lt;/strong&gt; decisions and higher-level alerts are emitted in real time. Successful allowlisted work is not streamed. Incident tools receive the events you configure them to receive.&lt;/p&gt;</description></item><item><title>Drive the allowlist from your own tooling</title><link>https://heartsecsuite.com/rootlock/alerts/central-policy-management/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://heartsecsuite.com/rootlock/alerts/central-policy-management/</guid><description>&lt;p&gt;&lt;strong&gt;Overview&lt;/strong&gt;: Root Lock by HeartSuite is designed to be driven by your existing central tooling. The Dashboard is the surface for a single host. Enterprises use their control planes to manage policy and observe at scale.&lt;/p&gt;
&lt;p&gt;Cloud Path and Local Path remain how each host is installed. This page is not a different install. It is how you harvest a baseline, install that package on many hosts, and apply extras without a Dashboard session on every machine.&lt;/p&gt;</description></item></channel></rss>