How we built security into Computer

Perplexity Computer is an autonomous agent that can write and execute code, browse the web, and access external services, built on Perplexity’s SOC 2 Type II-attested infrastructure and enterprise security features. To manage the added risks of executing code and interacting with live services, it uses Firecracker microVMs with dedicated kernels, isolated filesystems and networks, short-lived credentials, encrypted communications, and separation between storage and execution environments. Connector access is controlled by administrators and authenticated by users, with minimal-data transmission, encryption for file data, and a policy that enterprise task data and attachments are not used for model training, while attachments are deleted after seven days. Its prompt-injection defenses combine the BrowseSafe detection model, external-content classifiers, tool-specific guardrails, untrusted-content labeling, and safe stops for suspicious material, with ongoing updates informed by audits, red-team testing, and bug reports. Enterprise administrators can further govern access, connectors, models, billing, and monitoring through audit logs that integrate with SIEM platforms such as Splunk, Azure Sentinel, and Datadog.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.