Security

The agent cannot apply. Anything that mutates needs a human.

Fabric Projects is built so that the failure mode of a poorly-prompted agent is a closed PR, not a misconfigured cloud router. Our security model leans on Equinix's existing identity and approval surfaces — we just make them legible to the agent before it asks.

Plan-only by default

Every Terraform output ships with prevent_destroy and an apply guard. The default execution mode is dry-run.

control: F-001

Scoped MCP identities

Agents authenticate as network-agent-mcp@ users with project, metro, and resource scopes. Personal admin identities are never used for OAuth consent.

control: F-014

Account-aware preflight

Five blocking gates run before any mutating tool: ports/devices, observability permission, developer app, capacity confirmation, provider quote.

control: F-022

Pricing.md governance

The agent reads commercial estimates from a versioned pricing.md contract. Anything missing is reported as quote_required rather than fabricated.

control: F-031

Audit log per plan

Every plan run captures the prompt, the read tools, the blocked mutating tools, the timestamp, and the dedicated MCP user. Logs export as JSON or to a customer SIEM webhook.

control: F-040

Reviewer-grade Terraform

Output is shaped to be reviewable in a PR — modules, lifecycle blocks, apply guards, and explicit quote-status fields the reviewer can grep for before merging.

control: F-052
How we treat customer data

No customer data leaves your environment without consent.

The local workbench keeps everything on disk. The connected agent runs against your Equinix tenant with a read-only MCP scope by default. Nothing goes to a third-party inference provider unless you explicitly route through Equinix Fabric — at which point the path is private and observable.

Compliance roadmap

SOC 2 Type II in audit · Q3 2026
ISO 27001 scoped · 2027
HIPAA BAA on request
FedRAMP via Equinix Government Cloud
Subprocessors none for the local demo
Security review used to take weeks because everyone wanted to see what the network change would actually do. The plan-only output and audit log let us close that loop in a single afternoon.
Liam Doyle — Head of InfoSec, Pendle Federal