Forum

Forums
Non-Claw Alternativ...
Code-First Agent Fr...
SuperAGI Security
 
Notifications
Clear all

SuperAGI Security

Security of SuperAGI's self-hosted deployment — its web UI exposure, marketplace plugin risk, agent memory backends, and what the default install leaves open that you need to lock down.
RSS
Page 3 / 4

Thoughts on the new SuperAGI 1.0 release notes - did they fix the .env file exposure issue?

Last post by Tom Eriksen, 3 months ago

Posts: 1
Views: 25


What's the best way to monitor agent memory (Redis/Postgres) for unexpected data exfiltration?

Last post by Oliver Dunn, 3 months ago

Posts: 1
Views: 30


Showcase: I built a policy engine that intercepts and approves/denies agent tool execution.

Last post by Mark O'Brien, 3 months ago

Posts: 14
Views: 23


Step-by-step: Isolating SuperAGI's network traffic with VLANs and a dedicated firewall.

Last post by Raymond Cho, 3 months ago

Posts: 16
Views: 138


Am I the only one who thinks the default SQLite DB for agent memory is fine for small, trusted setups?

Last post by Sam HomeLab, 3 months ago

Posts: 14
Views: 17


My results after 30 days of running SuperAGI: A log of every unexpected behavior I had to contain.

Last post by Ari W., 3 months ago

Posts: 1
Views: 32


Comparison: SuperAGI's internal memory vs using an external, audited database like PostgreSQL with RLS.

Last post by Tomislav Horvat, 3 months ago

Posts: 7
Views: 37


Showcase: My 'lint' script that validates SuperAGI config files against a security baseline.

Last post by Ray Tanaka, 3 months ago

Posts: 16
Views: 51


What's the real risk of running SuperAGI on a developer's laptop vs a dedicated server?

Last post by Maria S., 3 months ago

Posts: 15
Views: 22


ELI5: How can a malicious plugin steal my API keys in SuperAGI?

Last post by Bob Chen, 3 months ago

Posts: 1
Views: 16


Page 3 / 4
Share:
Share
Tweet
Share