Security
The security review, answered up front
The questions a reviewer asks first—what listens on the network, what happens to secrets, what gets judged and what gets recorded—each has a short answer here, with the live status one click away.
Architecture
Small answers to the big questions
What listens on your network?
Nothing. Servers dial out to Alpacon over encrypted tunnels—no inbound ports, no bastion, no change to your network edge.
What happens to secrets in sessions?
Recognised credential formats are masked as the record is written—not cleaned up afterwards. Every read path serves the masked text.
What can a credential do?
Deny by default. A token's command, server and file allowlists start empty; a command not on the list does not run.
What is on the record?
Every command, file transfer and sudo grant lands on one filterable timeline per session, and terminal sessions replay.
Judgment
Checked before it runs, and checked again after
Commands are judged against the session's declared intent before they reach the host, not flagged after. Session analysis then maps what happened to MITRE ATT&CK—and the technique ids it names are checked back against the catalogue and dropped if they do not resolve. Even the emergency break-glass path lifts only IP and time bounds; the allowlists stay.
Status
Where the paperwork stands
- SOC 2 Type 2 in progress
- Independently penetration tested
Security
Bring your hardest reviewer
A 30-minute demo with the team. We'll walk through a session on your infrastructure and answer anything technical.