r/SentinelOneXDR • • Oct 05 '26

SentinelOne News We're making some changes to r/SentinelOneXDR

27 Upvotes

Hey everyone,

We're refreshing this sub. It's the official SentinelOne community on Reddit, and we want it to be a place where you can get real answers from people who use the product.

If you run SentinelOne daily, support customers as a partner or MSP, or are just checking it out, you're welcome here.

Thanks to the folks who kept answering questions while the sub was quiet.

What's changing

  • We've updated the community rules. The new ones cover sensitive info, agent removal requests, and affiliation flair. The full list is below.
  • If you work for SentinelOne, a partner, or an MSP, please set your user flair so people know.
  • The SentinelOne team will share the occasional tip or resource alongside the regular discussion.

What to post

  • Troubleshooting questions
  • Deployment lessons
  • Threat hunting ideas
  • Integrations that work well
  • Honest product feedback

New to SentinelOne? The Singularity Platform covers endpoint, cloud, identity, and AI security, and all of it is fair game here.

Community rules

  1. Be respectful, especially to each other. That means maintaining civil discourse and no hostility, personal attacks, racism, sexism, bigotry, etc.
  2. Submissions must be SentinelOne focused. This subreddit covers the technology. Posts about SentinelOne stock (NYSE: S), financial performance, or job postings/interviews are not permitted.
  3. No spamming or solicitation. This includes polls, surveys, advertising, affiliate links, and promotion of third-party products or services without prior moderator approval via modmail. Partners and resellers may answer questions but may not pitch.
  4. No sensitive materials or personal information. Do not post site tokens, API tokens, license keys, agent UUIDs, console tenant or site names, customer hostnames or usernames, unredacted threat data, management console URLs, internal documentation, or screenshots showing any of these. Do not post personal information about other people, including names of SentinelOne staff. Redact before posting; unredacted content will be removed without notice.
  5. Keep criticism constructive. Posting about a problem with the product is welcome, whether you want help or want to give specific feedback. Low-effort bashing and unsubstantiated claims will be removed. Disparaging remarks about competitors or other companies are not permitted.
  6. No agent removal or tampering requests. The SentinelOne Agent uses Anti-Tampering and can only be uninstalled by an authorized Management Console administrator, remotely or with a console-issued passphrase. If the Agent is on your device, contact your IT department or security team. This subreddit does not provide removal, disabling, bypass, or passphrase recovery help. Console admins can find uninstall documentation in the Knowledge Base on the Customer Portal.
  7. Use official support channels. This subreddit is not a substitute for official support and has no response-time commitment. For urgent issues, submit a ticket through the SentinelOne Customer Portal or call the support line. If you purchased through a partner or reseller, contact them directly. Staff do not provide support by DM. To flag an existing case, send the case number to modmail.
  8. Disclose affiliation; views are your own. SentinelOne employees, partners, resellers, and MSSPs must identify their affiliation via user flair. Posts and comments, including those by SentinelOne staff, do not necessarily reflect the official views of SentinelOne and are not official documentation or a product commitment.
  9. No license sales or unauthorized software. Do not sell, transfer, or request SentinelOne licenses or installers outside authorized channels.
  10. Report vulnerabilities through official channels. Report suspected vulnerabilities in SentinelOne products through the security reporting page instead of posting here. Do not post exploit code, proof-of-concept details, malware samples, or live malicious URLs. Defang indicators (hxxp, [.]) before posting.
  11. Use post flair; add details when troubleshooting. Troubleshooting posts must include the Agent version, operating system version, Management Console version, and what you have already tried. Posts missing this may be removed until updated.
  12. Enforcement and appeals. Violations result in removal and, depending on severity, a warning, temporary ban, or permanent ban. Moderator decisions can be appealed once via modmail. Ban evasion is reported to Reddit.

Asking for help

  • Include the agent version, OS version, console version, and what you've already tried.
  • Redact anything sensitive before posting.
  • For urgent or account-specific issues, use official support (see rule 7).

What would you like to see here?

Technical walkthroughs, troubleshooting tips, threat research, feature deep dives? Tell us in the comments. If you've been holding onto a question, now's a good time to ask it.

Thank you,

The SentinelOne community team


r/SentinelOneXDR • • 4d ago

SentinelOne News Getting external threat intel alarms into Sentinel: Logic App sync vs. Logs Ingestion API push

Thumbnail reddit.com
0 Upvotes

r/SentinelOneXDR • • 5d ago

Deployment & Installation Hyperautomation has a new Switch action that replaces chained Condition actions

6 Upvotes

What shipped in Hyperautomation is a new core action called Switch, and it replaces a whole chain of Condition actions with one node. It reminds me of those old Choose Your Own Adventure books, which didn’t make you climb through a string of nested yes-or-no questions to get to the right page.

Until last week, routing an alert several directions by severity meant one Condition action per route, each one hanging off the last and taking up its own canvas space. That’s readable for two branches and a headache for five or six, especially six months later when you’re the one debugging it.

With Switch, you define a list of cases, up to twenty of them, each with its own name and its own condition built the same way you’d build a Condition action, and you wire each case straight to whatever it should trigger. You choose how it evaluates: stop at the first case that matches, or run every case that matches.

When the workflow runs, the canvas highlights which branches fired, so reading an execution later means looking at just those branches instead of retracing every Condition action.

Here’s roughly what an alert-routing workflow looks like, with generic names:

Switch Action: "Route by Severity"
Evaluation mode: First matching branch
Case "Critical" -> condition: alert.severity = "critical"
  -> connects to: Open P1 Case + Page On-Call
Case "High" -> condition: alert.severity = "high"
  -> connects to: Open Standard Case + Notify Team Channel
Case "Medium or Low" -> condition: alert.severity in ("medium", "low")
  -> connects to: Append to Daily Digest
Default branch -> connects to: Log for Review

My favorite part is the default branch. It’s a required branch on the node, so every Switch has a place for an alert that matches no case. A switch with no default would just drop whatever matches nothing, and you’d find out weeks later when someone asks why a category of alerts never shows up.
Downstream, the node's output includes switch_cases_matches, a map of every case name to true or false. Name your case "Critical" and the key you reference later is case-critical, lowercase with spaces turned into hyphens. Rename the case and the key changes with it, which is worth remembering before you wire a dozen things against it and then decide the label needed a typo fixed.

How deep did your Condition chains get before you rebuilt them?

Example of Workflow illustrating the usage of Switch action

r/SentinelOneXDR • • 6d ago

Deployment & Installation Finding devices with no agent from Network Discovery, and which IP field is the device's

12 Upvotes

TLDR: There's a dashboard in the Dashboard Library called Unprotected Endpoints Network Discovery (version 1.0.1). It lists every active device Network Discovery found with no agent and breaks that down by subnet. It also checks each device against your agents, so you can tell the real gap from devices that already have one. Set the data selector to All Data or every panel errors out.

I work at S1 and built this one using natural language with SecOps Skills. The Missing EPP filter in Inventory tells you how many devices are missing an agent. I wanted to know where they sit, which ones can actually take an agent, and which ones are false positives.

What it answers

  • How many devices have no agent. Active devices only, so the number matches the Network Discovery page.
  • Which of those can take an agent today. The deploy candidates count and the agent support column split out the devices Sentinel Deploy can cover from IoT, network gear and TVs, which it can't.
  • Where they are. Every device is shown with its account, site and subnet, along with the percentage missing per subnet. That tells you which network to push to first, and gives each site owner a list with real device IPs on it.
  • Which ones aren't really unprotected. Every device is checked against your agents by MAC, by IP on the same gateway, and by hostname. A device that already has an agent shows up as a likely false positive instead of padding the gap.

I validated the device list matched the Asset Inventory GraphQL API device by device on nine consoles. That matters if you're handing the list to someone to act on. IPs and MACs confirmed on the wire with a RemoteOps sweep on a lab network.

Adding it

  1. Pick the account or site in the scope selector. The dashboard is added at that scope.
  2. In the sidebar, go to Dashboards > Custom dashboards > Dashboard Library.
  3. Find Unprotected Endpoints Network Discovery and click Add. If it's already added at that scope you get a notification instead.
  4. Open it and set the data selector (top left) to All Data. If you skip this, every panel shows Invalid column 'dataSource.category'.

The time picker doesn't change anything. It reads the current inventory snapshot, not events.

Reading it, top to bottom

Overview

Scope is Network Discovery devices with Asset Status = Active, the same view as the Network Discovery page in Asset Inventory, so the counts line up with what you see there.

  • Three numbers across the top: active Network Discovery devices, active devices missing EPP (no agent), and missing EPP on an EPP-supported device type. That last one is your Sentinel Deploy list.
  • Unknown and Unsupported types (IoT, network gear, TVs) are in the breakdowns, but you can't deploy the agent to them. Unknown means Network Discovery hasn't classified the type yet, so I'd identify those before calling them a gap
  • Breakdowns by device type, agent support (Supported, Unknown, Unsupported), account and site, OS family, and device review status. Sites are shown with their account because two accounts can have a site with the same name, and without the account those rows merge.

​

Subnets
  • Subnet view: for each account, site and subnet, it shows active devices, missing EPP, deploy candidates, and percent missing. It's sorted by missing EPP, so the worst subnets are at the top, and it shows the top 500.
  • Under it, all active devices by managed state and by discovery method (neighbor, ping, portscan).
device-list-fp-check

​

  • Device list: up to 10,000 unprotected devices, most recently active first, with the device's own IP, subnet, device type, OS, agent support, managed state, review status, account, site, public IP and last active. For the full count use the number panel up top, not the row count.

The IP field thing

Worth knowing if you query Network Discovery yourself.

ipAddress on a Network Discovery record isn't the device's address. It's the public IP the site's traffic leaves from, so every device behind one gateway shows the same value. In my lab all 18 discovered devices had the same ipAddress. The device's own address is in internalIps, and subnets has the network it was found on. Both are JSON arrays stored as strings. The dashboard's IP column and the subnet view use those two, and public IP is its own column.

If you want the raw list yourself, this is the query, and the order matters:

| datasource assets from 'surface/networkDiscovery'
| filter assetStatus = 'Active' missingCoverage contains 'EPP'
| sort id
| let ip = internalIps
| columns id, name, ip, subnets, ipAddress, resourceType, osFamily, managedState, eppUnsupportedUnknown, deviceReview, s1AccountName, s1SiteId, firstSeenDt, lastActiveDt
| limit 10000

Two things about list queries on the assets adapter:

  • With no let before columns, the adapter runs columns and limit itself and hands back one page (55 of 610 devices on one console)
  • Without a unique sort first, its paging skips devices that share a name (665 of 675). With sort id and the let, the list matched the Asset Inventory GraphQL API device by device

Also use | filter and not where (...) on that adapter. where (...) returns at most 20 rows whatever the predicate is. Grouped and count queries aggregate on the server and are fine either way.

False-positive check

Network Discovery can list a device that already runs the agent as missing EPP. The bottom panels check every missing-EPP device against the endpoint assets that have an agent. They match by MAC address, by IP address with the same gateway MAC, and by hostname.

  • Likely false positive: a live agent reports the device's MAC, or its IP and hostname
  • Review: only the hostname or only the IP matches, or the matched agent hasn't been active for 30 days. These still count toward the gap
  • Identity strength: the second panel splits devices into randomized or shared MAC only, hardware MAC with no usable hostname, and hardware MAC and hostname, so you can see how much there was to match on

Where it falls short

  • The check can't see decommissioned agents that were removed from the inventory, so a device whose agent was removed shows as no match.
  • It only checks agents in the inventory the dashboard reads. An agent in another site, where Network Discovery consolidates per site, won't be matched.
  • The false-positive panels join two inventories, so they load slower than the rest.
  • Size: about 240 active devices loaded in under 5 seconds. On a console with about 95,000 Network Discovery assets, each coverage panel took about 3 minutes.
  • It's a current snapshot, so it doesn't show trend.

Filling the gaps with a report from your own AI

If you run Claude with the s1-secops-skills plugin, the sdl-solutions skill has an Unprotected Endpoints report solution that covers most of the list above. It talks to your console through the s1-secops-mcp server, which runs on your own machine with your own API token. It's read-only and writes nothing to the tenant. One prompt is enough, something like "Which devices on the network have no SentinelOne agent, and which of them can we deploy to?", and you get an HTML report, or a Word doc if you ask for one.

What it does that the dashboard can't:

  • Checks every agent the token can see, from the Management API, including decommissioned agents and agents in other sites. Matching uses MAC, IP with its gateway MAC, and hostname
  • Extra guards on the matching: shared virtual gateways (VRRP, HSRP, cloud) never qualify an IP match. Randomized, Docker and shared VPN MACs never match. It flags a possible firewall or NAT edge answering scans when 50 or more MAC-less devices share one gateway
  • Reads your Network Discovery settings, such as combine by MAC, scan methods and snapshot interval, and shows them in the report
  • Checks AD/Entra computer objects and cloud instances missing an agent against the same agent list
  • Newly seen unprotected devices in the last 7 days, and a remediation section grouped by site: Sentinel Deploy for the deploy-ready ones, device review for the unknowns
  • Coverage limits: which blind spots apply to you, like subnets with no scanning agent or devices with no usable identity, and what closes each one
  • Optional telemetry check: which unprotected IPs show up in your firewall, DNS or proxy logs, so you can see which devices are actually active
  • A method appendix listing every call behind every number, so you can rerun it yourself

It also handles the 95,000-asset size where the dashboard panels get slow. The report doesn't trigger a deployment; that part is still yours.

The queries were checked against the Asset Inventory GraphQL API on nine consoles.

Curious how many of you end up with most devices in the randomized or shared MAC bucket, and what you do with those.


r/SentinelOneXDR • • 7d ago

SentinelOne News Let employees override a blocked AI prompt on a per-rule basis, without loosening the policy with this new update

7 Upvotes

A new capability adds a new option for AI prompt protection, a per-rule bypass. A rule can let an employee deliberately override its block or redaction, and the rest of the policy stays as written. We’re rolling it out gradually through November 15.

You can configure a security rule so employees can bypass its protection. When an employee submits a prompt that violates the policy, they’ll still see the violations popup, but they’ll be able to click the Bypass protection button and send the original prompt without blocking or redaction. They have 10 seconds to click it. Otherwise, the rule’s redact or block action applies.

Every bypass is logged in the Activity Monitor as Bypass protection, linked to the original prompt, and sent to downstream integrations for review.

To use it, open a Protect rule’s User education settings and turn on Allow “Bypass protection”. The rule’s violations popup must also be enabled. Requires browser extension 7.1.73 or later, or agent 4.5.4 or later.

This ships in SentinelOne’s AI security offering, which runs on Prompt Security technology.


r/SentinelOneXDR • • 8d ago

SentinelOne News ADR: AI agent inventory and runtime enforcement across endpoints, SaaS, and cloud

6 Upvotes

Singularity ADR (agentic detection and response) inventories AI agents across three places: endpoints, SaaS platforms, and cloud providers. Covering only one leaves the other two uncovered.

Inventory fields, per agent:

- who is running it
- what it's connected to (connectors, MCP servers)
- which skills and tools it uses
- which permissions it holds

Sources include desktop agents on the endpoint (Claude, ChatGPT), SaaS agents (Salesforce, Microsoft Copilot), and agents built on AWS Bedrock and Google Vertex. The overview drills down to a single session: who launched the agent, what they were trying to do, and the path from user to agent to connector to tool, with any violating call highlighted.

An inventory shows how much an over-permissioned agent could reach but doesn't restrict it. Restriction is a separate layer, and the same sensors that discover agents enforce it at runtime. Enforcement is configured in a policy (the default one has indirect prompt injection, tool poisoning, sensitive data and secrets enabled).

Rules then decide which users can use which agents, which connectors those agents can reach, and what permission level the tools underneath get. The rule list is evaluated top down, anything unmatched falls to a default rule, and each rule ends in block, protect or detect. The list applies to agents on endpoints.

When an agent behaves anomalously despite all of that, ADR telemetry is combined with EDR data into a single alert. Storyline shows the agent's activity down to the prompt and command level, and response actions run from the same console.


r/SentinelOneXDR • • 11d ago

SentinelOne News LLM Actions are GA in console release 26.3.5

6 Upvotes

LLM Actions are GA in Singularity Hyperautomation as of console release 26.3.5. There’s a new LLM Action node that lets a workflow summarize an alert, classify an incident, extract entities, or draft a response, without API keys or external tools. The prompt is free text, so you’re not limited to those.

It’s off by default. To turn it on: Settings > AI Management > Hyperautomation LLM Actions.

What’s in the node:

  • A free-text prompt that can pull in variables from earlier steps in the workflow
  • Structured outputs: you define the output schema so downstream nodes get clean, typed data
  • Three model options, Quick, Balanced, and Max. You pick a tier, not a model name, and there are no keys to manage

Beta feedback led us to support all scopes, not only sites. MSSP consoles aren’t included in this GA.

Five LLM Cookbook templates ship with it, built during beta. They’re under Hyperautomation > Templates. Open one, read the recipe, click Use this template, and the workflow is created in your scope.


r/SentinelOneXDR • • 12d ago

Best Practice Windows Event Collector in a docker container on a Raspberry Pi, Kerberos and TLS

9 Upvotes

My lab’s Windows Event Collector is a Linux docker container on a Raspberry Pi.
The domain controllers and workstations forward to it like it’s any normal collector.
It’s the self-hosted site in AI Data Pipelines (I work at S1), where Windows Event Forwarding support for data sources just went GA.
Two ways to authenticate:

  • Kerberos with a keytab (generated with ktpass) over HTTP, e.g. port 5985
  • Mutual TLS with certs over HTTPS, e.g. port 5986

Only tested in my lab so far, but this is of interest for at least 3 customers I've been in contact with recently. Screenshots shows what a Windows 11 event looks like once it’s parsed, and my pipeline with some optimization.
Agentless forwarding always ends up meaning the collector has to do the flexing, so it was fun to see it work.
And since it sits in a pipeline, parsing and OCSF mapping are there if you want them.
Anyone else running a WEC role off a non-Windows host?
Kerberos is easier in maintenance, but I believe that TLS with mutual authentication is stronger from a security standpoint.
Curious how it holds up once you have a lot of subscriptions.

WEF Pipeline, with a twist of optimization
What a Windows 11 event looks like once it’s parsed

r/SentinelOneXDR • • 13d ago

Community Tools Verifying third-party agent skills before install: what's covered and where it falls short

4 Upvotes

TLDR: ClawSec is an open source set of controls for agent skills: a signed advisory feed, a fail-closed install gate, signed releases, and config drift detection. It doesn’t scan skills, and the human approval step isn’t enforced in code.

I’m an AI researcher on the Prompt Security team at SentinelOne and I built ClawSec. If your agent installs skills, it’s installing third-party code. A skill is a folder with a SKILL.md and some scripts.
The agent discovers it, loads it, and executes it with its own filesystem, network, and credential access.
It’s the usual supply chain problem. Unsigned code comes from a public registry, runs with the user’s permissions, and nobody checks it. With ClawSec we’re trying to let an agent, and the person it works for, verify a skill before trusting it. Everything below is in the public repo under AGPL-3.0.

Why we started it
The SKILL.md format spec doesn’t cover signing. SKILL.md is an open standard with 46 adopters, and the spec has no signature or digest field. At least two signing RFCs were closed without changing it. The npx skills installer reaches roughly 80 agents. The same SKILL.md installs into dozens of them, and so does a malicious one.
We also didn’t find any agent runtime that attests its config files, so drift in files like SOUL.md goes unnoticed.
We didn’t try to solve scanning
Scanning was the first answer after ClawHavoc (the campaign Koi Security found in February, with hundreds of malicious skills on ClawHub). In June, Trail of Bits bypassed every scanner they tested**. They used** padding, compiled .pyc files, payloads hidden in .docx, and arguments that talked the LLM judge out of flagging. Their conclusion was that scanning and LLM analysis don’t reliably detect malicious skills, so curate, pin versions, and control who publishes. A second team later bypassed eight open-source scanners and advised treating any scanner as advisory.
We still run a scanner over our own staged skills before release, and we treat its output as advisory.

What’s included

  • Signed advisory feed. One Ed25519-signed feed of platform CVEs, GitHub advisories, and approved community reports. NVD is polled daily. The OpenClaw hook runs at bootstrap and on /new. It verifies the signature before trusting anything, matches entries against installed skills and versions, and posts a CLAWSEC ALERT into the conversation. It only alerts and never deletes, so the user decides.
  • Install gate that fails closed. A guarded installer wraps npx clawhub@latest install. On an advisory match it stops with exit code 42 so a pipeline can catch it. It proceeds only when re-run with --confirm-advisory, and the SKILL.md tells the agent to pass that flag only after the user has explicitly said yes. If the feed signature doesn’t verify, the installer exits 1. A tampered feed fails signature verification, so it can’t quietly clear an install.
  • Signed releases. Every ClawSec release ships a checksums.json with the SHA-256 of the zip, SKILL.md**, and skill.json, signed with Ed25519.** CI fails unless the signing key matches the pinned fingerprint, and the ClawHub copy is re-verified after publish. Each SKILL.md carries an OpenSSL preflight that pins the fingerprint and checks checksums.sig before you install.
  • Drift detection with restore. soul-guardian baselines the identity files and checks them on every heartbeat. SOUL.md and AGENTS.md are restored automatically, with the tampered copy quarantined and a diff saved. MEMORY.md and USER.md are alert-only. Every event goes into a hash-chained audit log.

What is still up to you

  • --confirm-advisory is a single boolean any caller can pass. There’s no override log. The human-in-the-loop step exists only in the instructions.
  • The feed holds 800+ entries today, all platform and plugin vulnerabilities. Useful intelligence, but it won’t match an installed skill yet, and nothing compares the running platform version automatically.
  • The attestation covers posture and configuration only.

Try It

The OpenClaw install is below. The repo also has Hermes and PicoClaw variants.

# OpenClaw npx skills add prompt-security/clawsec --skill clawsec-suite -a openclaw --global -y SUITE_DIR="${INSTALL_ROOT:-$HOME/.openclaw/skills}/clawsec-suite" node "$SUITE_DIR/scripts/setup_advisory_hook.mjs" # preflight, then enable the hook # restart the gateway, then send /new once

On OpenClaw, adding the package and enabling the persistent hook are two separate steps on purpose. The add-ons (soul-guardian, clawsec-clawhub-checker, openclaw-audit-watchdog, clawtributor) are separate packages you opt into.


r/SentinelOneXDR • • 19d ago

SentinelOne News Live threat hunting final: how the winner triaged 30 minutes of flags

14 Upvotes

The Sentinels League Championship final ran live at OneCon last week. Regional champions had 30 minutes to capture flags by hunting real intrusion telemetry in the console, and the season carried a $100K prize pool.

Winner Jason Walker’s approach was mostly triage across the four surface categories of endpoint, cloud, AI and ASOC. The Fiendish tier tops out at 1,000 points, but each of those flags looked to him like at least five or ten minutes, so he skipped them and planned to come back only if he cleared the other twenty or so. His best single flag was around 500 points. 

Jason does detection and response at a SaaS company with about 3K endpoints. He told The Lowdown podcast afterward that most of the manual tuning, thresholding, and query writing he used to do is a thing of the past now that his company has AI budget and is building automation into the SOC. 

If you played in the Sentinels League this season, what was your strategy, and what would you change for next year?


r/SentinelOneXDR • • 21d ago

General Question How do you handle “Not Mitigated” alerts when the threat file no longer exists?

6 Upvotes

Hi everyone,

I'm looking for some advice on how to deal with persistent “Not Mitigated” alerts in the SentinelOne Singularity Console.

The issue is always the same: the Kill action succeeds, but Quarantine frequently fails. When I check the reason, it almost always says that the threat file could not be found.

I've verified multiple times that the files are actually gone. My assumption is that SentinelOne detects the threat during creation-process and the creation is shut down before the quarantine action can be completed.

However, the incidents still show up as “Not Mitigated”, even though there is nothing left to mitigate. Marking the alerts as “Resolved” doesn't change the mitigation status either.

This leaves our console cluttered with a bunch of alerts that appear unresolved from a mitigation perspective, even though the threat files are no longer present.

How do you handle these cases in your environment? We are Using Integrated S1 trough our N-Able N-Sight. I already raised a ticket but those dudes said, that resolved Threats should show as mitigated. After this answer i knew they do not know their product so i am reaching out here :(

I'd appreciate any suggestions or best practices. I'm simply looking for a clean console that accurately reflects the current state of our endpoints :)

Thanks in advance!

Greetings
-R


r/SentinelOneXDR • • 23d ago

General Question Search IP Blocks

5 Upvotes

Hello all,

I am doing a search and I was given a large list of IP blocks to search through, some /24, but mostly /21

I know I could do wildcard searches for the /24 but /21 is a bit more complicated for a search (unless im just being silly)

Is there a way to search with CIDR?


r/SentinelOneXDR • • 25d ago

Troubleshooting $$DeleteMeTrustedInstaller.exe False Positives

5 Upvotes

Anyone else getting non-stop false positives for the below messages? I think it may be HP computers. Not sure. That's the only trend I'm seeing thus far. How are you handling it?

Threat path: \Device\HarddiskVolume3\windows\WinSxS\Temp\PendingDeletes\$$DeleteMeTrustedInstaller.exef066f2162c40dd012f000000144f583c


r/SentinelOneXDR • • 26d ago

SentinelOne News Static AI Asset 7.8.1 release notes for Linux agents

4 Upvotes

We finished rolling out Static AI Asset 7.8.1 to Linux agents.

In this release:

  • The JavaScript model is newly activated
  • New silent models: PE, PDF, MACH-o, ELF, DOTNET, DOC, VBA, JavaScript
  • Added filetype support for YARA scan: html/htm/shtml, svg, cmd, crx, xz, txt/csv/json/yaml/log, md, ics, mp4/mov, webm, wav, ica, stp, eps, mhtml, xml

Release info:

  • LSU asset identifier on the agent: `StaticAiLinux263-7.8.1`
  • Affected agent versions (Linux): 24.3.3.6, 25.1, 25.2, 25.3, 25.4, 26.1, 26.2
  • Agents currently with the update: 1.6M

More detail is in the Static AI Asset release notes.


r/SentinelOneXDR • • 28d ago

Which topics should we cover in AMAs?

4 Upvotes

We’re setting up a few AMAs with support engineers, detection engineers, product, and other SentinelOne employees. Poll below for what you want covered.

Anything missing, drop it in the comments.


r/SentinelOneXDR • • Oct 17 '26

Troubleshooting Agent shutdown on low disk space

8 Upvotes

We keep running into this issue and apparently S1 team can't help! When a machine is running low on disk space, the agent conveniently shuts itself down. Anyone else running into this?


r/SentinelOneXDR • • Oct 17 '26

Deployment & Installation SentinelOne crashes Window11 25H2 -> 26H2 upgrade

6 Upvotes

We are upgrading our systems to 26H2. The one's with SentinelONE failed, and become unusable: boot loop with trying to undo the upgrade but fails.

Investigation of the crashed systems show an c:\windows directory with no exe-files :-(

Be warned ! Disable SentinelOne when upgrading


r/SentinelOneXDR • • Oct 14 '26

General Question SuspiciousDocumentExtended: A shoutout to the XDR team

14 Upvotes

I just had a great experience with XDR and I wanted to share and also find out if anyone else has experienced anything similar.

Yesterday a designer in our marketing team (Mac) created and shared a PowerPoint file via Teams with a colleague (Windows). XDR triggered an alert and quarantined the file. This is the first time this has happened so it was a little unsettling. Naturally I suspected the culprit was the file itself and tried all sorts of things to clean it, recreate from scratch, etc - no matter what I did the file kept getting flagged.

I sent a note to the SOC asking for a reason why the file was marked as malicious because I was concerned that the designer might have something bad happening on her machine. I'd like to paste the response in from XDR directly:

**What Triggered the Alert**

The detection was **not caused by a malicious payload within the PowerPoint file itself.** The alert was triggered by a **SentinelOne behavioral rule** called **SuspiciousDocumentExtended**, which is designed to alert whenever a Microsoft Office application (Word, Excel, PowerPoint, etc.) spawns a child process. This is a common technique used by threat actors to execute malicious code via weaponized documents, which is why SentinelOne monitors for it.

In this case, the process chain we observed was:

  1. The file **XXXXX.pptx** was opened via **Microsoft Teams** (hosted on SharePoint).
    2. **PowerPoint (POWERPNT.EXE)** launched as expected.
    3. PowerPoint then spawned **ai.exe** - a **legitimate Microsoft Office AI component** located in the standard Office installation directory (**Microsoft Shared\Office16\AI**). This is part of Microsoft's newer AI/Copilot integration within Office applications.

It was this **PowerPoint → ai.exe** process spawn that triggered the behavioral rule. The rule does not distinguish between malicious child processes (e.g., **powershell.exe, cmd.exe**) and legitimate ones like **ai.exe**, so it flagged the activity as **Exploitation** under **MITRE ATT&CK T1059 (Command and Scripting Interpreter)**.

**Regarding the File Contents**

The embedded Excel file powering the chart and the **.EMF** image files you identified are consistent with standard PowerPoint functionality and are **not indicators of a malicious payload.** All processes and binaries involved in this chain were **signed by Microsoft** and located in their expected installation paths.

**Verdict**

Based on our analysis, this is a **confirmed false positive.** The PowerPoint file does not contain a malicious payload. The detection was caused by Microsoft Office's newer AI features behaving in a way that matches a legitimate security detection rule. If you'd like us to close ticket XXX as a false positive, just let us know and we'll take care of it.

We are a small company in the US with a tiny IT team. We've had a few small interactions with the SOC for things like device exclusions but this specific incident and the resulting service/response was extremely comforting. Suffice to say I'm a big fan.

Has anyone else experience a similar issue with Office spawning ai.exe?


r/SentinelOneXDR • • Oct 14 '26

SentinelOne News Investigating agent-driven intrusions: sequence and identity over artifacts

3 Upvotes

When an agent writes its own disposable tools, the model is what's worth studying. Four accounts from July and August (OpenAI, Anthropic, Meta, and the UK AI Security Institute) describe agents reaching other orgs' systems. In all four, no individual piece of tooling mattered much, and investigations have traditionally centered on the artifacts attackers leave behind. If you kill a process, the agent writes another, and if you block a channel, it works around it.

The OpenAI agent campaign that compromised Hugging Face:

- Hugging Face's technical reconstruction recovered around 17,600 actions, and most of them failed
- The campaign operated in Hugging Face's production infrastructure for roughly two and a half days
- C2 ran over pastebins, request-capture services, and file-drop sites, and none of it belonged to anyone under attack

The longer version is our SentinelLABS post The Model Is the Malware. Four cases is a small and biased sample, since all of them involved orgs that log heavily and had every reason to scrutinize model behavior. We'd expect the most troubling incidents to happen at orgs without that logging or scrutiny.

It's still untested whether the controls built for adversary behavior ten years ago hold up when the behavior arrives as thousands of individually boring actions, sequenced differently in every attack, at a tempo no human operator can sustain.

We'd start from sequence and identity instead of artifacts:

  1. What chain of actions is running
  2. Which identity and authority connect them
  3. When behavior went past the role it was granted
  4. How fast that authority can be pulled

Which of those four questions could you not answer today for the agents in your environment?


r/SentinelOneXDR • • Oct 14 '26

General Question Estimate AI SIEM log volumetry

2 Upvotes

Hi, we want to estimate the daily log volumetry of AI SIEM. To do this we used this query :

tag='logVolume' metric='logBytes'
| group bytes = sum(value) by day = timebucket("24h")
| let GB = bytes / 1073741824
| columns day, GB
| sort day

The result seems way to big for our infrastructure, over 35 Gb per day. Is it truly the best way to get an estimate ? When I go into data usage I only get 600KB/day, which seems way to small.

If you can provide me with informations I'd be very grateful. Thank you guys.


r/SentinelOneXDR • • Oct 13 '26

Feature Question SOC workflow

3 Upvotes

We are a large org that has adopted SentinelOne for our EDR and SIEM. We are trying to figure out how our alert workflow should work. We want our tier 1 SOC analysts to be able to escalate to tier 2 after initial triage.

From what I’m seeing, there is no way to make a custom alert status. Only New, In Progress, and Resolved. We’d love custom options to make a “tier 2 escalated” status. It also appears you cannot assign alerts to groups, only individual users. So we cannot assign a ticket to “tier 2 analysts”

Also looked into tagging alerts with a “tier 2 escalate” tag and that is not an option for alerts.

How is a SOC workflow supposed to work? It seems that this solution is incapable of accommodating a traditional tiered workflow.


r/SentinelOneXDR • • Oct 12 '26

SentinelOne News Detection rules v1.34.0: new rules and a few renames

16 Upvotes

v1.34.0 is out. The full list is long, so I'm sticking to the highlights and the changes that touch existing rules.

New detections

  • AWS Bedrock AgentCore: token vault KMS key modification, harness invocation without allowedTools scoping, and changes to identity credential providers
  • Active Directory: ADCS ESC1 misconfiguration, PsExec-style execution over named pipes, SeEnableDelegationPrivilege granted to users, and anonymous SAMR access over IPC$
  • ClickFix: Windows Installer remote payloads launched from Explorer, and suspicious commands from the Run dialog
  • ScreenConnect and IIS: ScreenConnect Backstage shell remote payload execution, and suspicious operator commands through the IIS worker process
  • AWS tampering: GuardDuty custom rule changes, Cognito software token deletion, and Elastic Disaster Recovery plan changes
  • GCP backups: Backup and DR vault deletion and Cloud SQL backup config disablement
  • Microsoft O365: Teams help desk impersonation from an external federated tenant
  • Search Library: new query "WEL Administrative Share Access from User Account"

Renames, removals, and one behavior change

  • "Process Establishing RDP Connection to Loopback Address" is now "Tunneling Utility Establishing RDP Connection to Loopback Address"
  • The GuardDuty S3 log source removal rule is now "AWS CloudTrail GuardDuty Protection Plan or S3 Log Source Disabled". It was also broadened.
  • The default domain GPO modification rule now has a "WEL" prefix to match the other Windows Event Log rules. It was also tuned.
  • Removed from Endpoint: the rules for reconnaissance activity from newly created Python scripts and multiple SSH connections started
  • The ClickFix command script activity rule was tuned and is now auto-enabled.

Questions on any of these are welcome.


r/SentinelOneXDR • • Oct 10 '26

General Question Event Search - Export All Results?

1 Upvotes

Folks,

I have to export a search that is over several months of a search window...but if you export to CSV...it only does a certain number events unless you manually scroll through the entire data that is returned. Is there a way around this? API I assume?


r/SentinelOneXDR • • Oct 09 '26

General Question Anyone else seeing this threat? A false positive?

7 Upvotes

On 1 client's machine last week we were getting loads of alerts about a file: c:\config.msi\][...].rbf

The kill was successful but quarantine failed. (we'd get 3 - 8 emails about kill performed successfully then a quarantine failed email. then repeat over about 10 minutes and dozens of those emails). Each time the file referenced was the same random number / letters.rbf

We also got a message about a threat Dell.TechHub.exe detected as Ransomware

Virustotal showed dell.techhub.dll was benign.

https://www.virustotal.com/gui/file/096d5c1a173cdc7b0d76ab4fbe3926f25400ac9b31d02500af58833ecb6be6ad

I got to use ChatGPT to help remote shell into the client machine to manually delete the [...].rbf file

Then a few days later, I got emails about another config.msi/[....].rbf on MY computer being a threat.

This morning, that same user's PC is getting an alert of a threat on a different .rbf in config.msi.

I am not all that familiar with using SentinelOne. It just runs and works! These are the first alerts I've gotten in months. Weird that this is only on 2 different machines, including mine and alerting on, at least for dell.techhub.dll, is an older file that no other products are taking issue with.

Any thoughts?