Notifications
Clear all
Topic starter
08/07/2026 7:04 pm
TL;DR: Deep cloud and runtime telemetry are being used by agentic RADBots to investigate, prioritise, and triage security signals based on ground truth, according to RAD Security. The governance question is whether digital workers that can suggest and perform remediation steps are still being controlled as tools, or whether their runtime authority now needs identity and lifecycle treatment.
NHIMG editorial — based on content published by RAD Security: RAD Security Joins NVIDIA Inception
Questions worth separating out
Q: How should security teams govern AI systems that can both triage and remediate alerts?
A: Treat them as privileged non-human identities with explicit ownership, scoped permissions, and revocation paths.
Q: Why do agentic security tools change identity governance requirements?
A: Because the risk is no longer only whether the tool detects accurately.
Q: What breaks when digital workers are treated as ordinary automation?
A: You lose ownership, review, and offboarding discipline for a system that can affect production security state.
Practitioner guidance
- Define whether the security worker can execute or only recommend Separate advisory workflows from write-capable workflows before granting the system access to containment, ticketing, or remediation functions.
- Inventory every telemetry source that can justify action Record which cloud, workload, and runtime signals feed decisions and which sources are trusted enough to trigger remediation.
- Add lifecycle controls for digital workers Create onboarding, ownership, review, and offboarding steps for any AI system that can perform security operations.
What's in the full article
RAD Security's full blog post covers the operational detail this post intentionally leaves for the source:
- How RADBots are described as digital workers across investigation, prioritisation, and triage flows
- The company-specific product context behind its AI workflow design and go-to-market positioning
- The NVIDIA Inception benefits RAD Security says will support product development and technical work
- The exact wording RAD Security uses to describe its telemetry-driven security workflow
👉 Read RAD Security's announcement on joining NVIDIA Inception →
Agentic security operations in NVIDIA Inception: what changes now?
Explore further
08/07/2026 7:27 pm
Execution-capable security automation is a governance problem, not a tooling feature. Once a security system can do more than recommend remediation, it occupies a non-human identity role with real operational authority. That shifts the question from model quality to entitlement control, auditability, and revocation. The implication is that security operations teams must stop treating agent output as advisory by default when the system can actually act.
A few things that frame the scale:
- 67% of organisations still rely heavily on static credentials despite the risks they pose to agentic AI deployments, according to The 2026 Infrastructure Identity Survey.
- That same survey found that only 13% of organisations feel extremely prepared for the reality of agentic AI, which shows how quickly governance is lagging capability.
A question worth separating out:
Q: When should organisations restrict remediation authority in AI-driven security workflows?
A: Restrict it whenever the system can act on signals that are incomplete, noisy, or influenced by untrusted sources. If a workflow can change containment, create tickets, or modify access, those actions should be separated by approval, scope, or environment. The safest default is advisory first, execution second.
👉 Read our full editorial: RAD Security joins NVIDIA Inception for agentic security operations
