Security by absence. Trust is the product.
The best way to avoid an agent incident is to keep the agent from ever being able to cause one. Powerloom is a control plane designed so that the blast radius of a rogue agent is scoped by your directory, your audit trail, and your approval gates — not by the agent's good behavior.
This page lists what we do today in plain language, what's underway, and what's aspirational. We don't claim certifications we haven't earned.
What Powerloom does today
Isolation
Every tenant gets its own VPC, its own KMS customer master key, and its own database. No shared compute between tenants. Deployed on AWS; infrastructure-as-code via Terraform.
Identity
SSO via OIDC with Google Workspace, Microsoft Entra ID, and GitHub. OUs mirror your directory — the RBAC model your admin team already operates. Agents run with workspace-scoped service identities, not human credentials.
RBAC with deny precedence
Role bindings allow or deny on OUs, agents, MCP servers, and tools. Deny wins every merge. Simulator runs before enforcement so you can see a policy's effect before it ships.
Append-only audit
Every policy decision, every tool call, every manifest apply is written to a hash-chained audit log. Each record hashes the previous, so silent edits are detectable. Log-ship to your SIEM is on the roadmap; export is available today.
Encryption
Data at rest is envelope-encrypted with per-tenant KMS keys. TLS 1.3 in transit on every hop. Secrets live in AWS Secrets Manager, not in environment variables or config files.
Approval gates
High-impact actions — create OU, deploy MCP, bind role to sensitive scope — require a second approver. The approval is itself a first-class audit event.
What is in progress
SOC 2 Type I
Audit engagement underway. We'll link the report here when it's issued. Not before.
SOC 2 Type II
Follows Type I with the required observation window.
HIPAA readiness
BAA availability is planned for enterprise tier once the control set is audited. Not available today.
ISO 27001
On the roadmap. No commitment date.
SIEM log-ship
Today: export audit log via API. Planned: push to Splunk, Datadog, and AWS Security Lake.
What we don't do (yet)
We don't have SAML support. We don't have SCIM user provisioning. We don't have a FedRAMP authorization. We don't host in regions outside US-East and EU-Central. If any of these are blocking for you, tell us — it helps us sequence the roadmap.
Report a vulnerability
Email security@powerloom.org. We respond within one business day. No bounty program yet; we acknowledge reporters on request.