Trust & Security
We operate inside client infrastructure. We access financials, email, project data, and business-critical systems. That level of access requires a security and compliance posture that matches what enterprise clients expect, regardless of firm size. Here is exactly what we've built, what we're actively working on, and what's coming next.
Compliance Status
SOC 2 Type II
In progress — report expected Q3 2026
NIST AI RMF
Aligned
GDPR DPA
Production-ready, available on request
HIPAA BAA
Production-ready, available on request
SOC 2 Timeline
We're pursuing SOC 2 Type II directly, skipping Type I. The observation window runs three months, followed by auditor fieldwork and the final report. Here's where we are in that process.
April 2026
Current14 security policies finalized. Vanta configuration and AWS integration (CloudTrail, Config, GuardDuty). Insurance binding. Background checks. Observation window begins.
May 2026
Third-party penetration test commissioned. AI Governance Framework formalized. Trust page published. SBOM generated. Agentic MSA attorney review.
June – July 2026
Pen test remediation and retest. SOC 2 auditor engagement. Observation window continues with continuous monitoring via Vanta. Q2 quarterly access review.
August – September 2026
Auditor fieldwork. SOC 2 Type II report issued with three-month observation window and clean audit.
14 Security Policies
We have written 14 formal security policies that describe how we actually operate. These are not template documents purchased from a compliance vendor. Each one was written specifically for our infrastructure, our agent architecture, and our client delivery model.
• Information Security Policy
• Access Control Policy
• Acceptable Use Policy
• Encryption Policy
• Change Management Policy
• Data Classification Policy
• Data Retention & Disposal Policy
• Monitoring & Logging Policy
• Password & Authentication Policy
• Vendor Management Policy
• Incident Response Plan
• Business Continuity & Disaster Recovery
• Vulnerability Management Policy
• Personnel Security Policy
All policies effective 2026-03-31. Annual review cycle. Enforced through technical controls where possible.
Evidence & Testing
Compliance is only credible if it's backed by evidence. We maintain 13 evidence artifacts that are continuously updated and available for auditor review.
Disaster recovery restoration test completed. Full system restored in 55 seconds against a 4-hour SLA target.
Vulnerability scan completed. Findings identified and tracked through remediation. GitHub Dependabot and CI pipeline scanning active.
Q1 2026 quarterly access review completed. SSH keys, Tailscale devices, GitHub membership, Mission Control accounts, and integration tokens all reviewed. 8 remediation actions taken.
Third-party penetration test scheduled for Q2 2026. Scope: external network, web application, and API. Annual cadence thereafter.
Risk Assessment
We maintain a comprehensive risk register with over 25 identified risks across infrastructure, application, agent operations, and business continuity categories. Each risk is rated by likelihood and impact, mapped to specific controls, and tracked through remediation. A separate red-team exercise identified 56 attack vectors across the agent architecture, consolidated into a priority matrix with P0 through P3 ratings.
Critical and high-severity items have been addressed. The risk register is reviewed quarterly and updated when the architecture changes.
How We Protect Your Data
Client Isolation
Every client runs on dedicated infrastructure with five isolated Linux user tiers: admin, application runtime, agent service, per-client workers, and per-client MCP integration processes. Each tier has its own credentials, file permissions, and network egress rules. Your data physically cannot be accessed by another client's processes. This is an architectural constraint enforced by the operating system, not a policy that relies on software to enforce it.
Encryption
TLS 1.3 for all data in transit, with a minimum floor of TLS 1.2. AES-256 for all data at rest including EBS volumes, AWS Secrets Manager entries, and credential vaults. Encrypted backups with offsite storage and tested restoration procedures. Automatic certificate renewal via Caddy with HSTS enforcement.
Access Control
Role-based access with least-privilege enforcement across every layer. MFA required for all administrative access. Per-user iptables egress filtering controls what each process can reach on the network. SSH key-pair authentication only, no password-based SSH. AWS root account protected with hardware MFA and never used for routine operations. Quarterly access reviews covering all credentials, devices, and memberships.
Credential Management
Three-tier credential vault architecture. Tier 1: root-owned CLI vaults with sudo wrapper pattern, so worker processes never see credential files directly. Tier 2: MCP integration credentials stored under dedicated UID-isolated users, inaccessible to agent processes via /proc. Tier 3: AWS Secrets Manager for tokens requiring rotation, synced every six hours. Agent processes have zero direct credential access at any tier.
AI Agent Security
Every AI agent operates in a sandboxed environment with restricted network access. API blocklists use three-layer enforcement across 11 categories — backend middleware, CLI wrappers, and RBAC roles — to prevent unauthorized operations. All DELETE endpoints, financial approvals, user management, and sensitive write operations are blocked by default. Agent instructions are immutable and cannot be modified at runtime by user input or prompt injection. All agent actions are audited and logged with full traceability, and all output is scrubbed for credential exposure before delivery.
AI Governance
We maintain a formal AI Governance Framework aligned with NIST AI RMF and ISO 42001. This framework governs how we build, deploy, monitor, and retire AI agents that have access to client systems. It is the operating manual for responsible agent deployment.
- • Agent inventory and classification — every agent in production is cataloged with defined scope, access permissions, and risk classification
- • Three-tier human oversight model — human-in-the-loop for high-risk actions (financial approvals, external communications), human-on-the-loop for moderate-risk (report generation, data analysis), full automation only for well-bounded routine tasks (email triage, status monitoring)
- • Incident classification for agentic AI — five severity levels covering hallucination, unauthorized action, data leakage, instruction drift, and prompt injection attempts
- • Model management — evaluation procedures, version tracking, rollback capabilities, and training data opt-out for all deployed models
- • Transparency and disclosure — clients are informed of what AI does, what it cannot do, where human judgment is applied, and what data flows through third-party model providers
Legal Readiness
Our legal documentation is production-ready. MSA, DPA, HIPAA BAA, and SOW templates can be executed immediately. An Agentic MSA with AI-specific liability provisions is in development with attorney review.
- • Master Services Agreement (MSA) — includes AI disclosure clause, tiered pricing structure, SLA exhibit with 99.5% uptime commitment, and standard liability provisions
- • Data Processing Agreement (DPA) — GDPR-aligned, covers all personal data processing with defined retention periods, deletion procedures, subprocessor list, and data subject rights
- • HIPAA Business Associate Agreement (BAA) — 45 CFR 164.504 compliant, 9 mandatory provisions, AI-specific language for PHI access, subcontractor BAA flow-down
- • Statement of Work (SOW) templates — standardized engagement scoping with deliverables, milestones, acceptance criteria, and payment terms
- • Agentic MSA — in development, covers AI-specific liability allocation, autonomy tier definitions, insurance requirements, and incident response provisions specific to autonomous agent systems
Insurance
We carry cyber liability and errors & omissions (E&O) insurance with affirmative AI coverage. Our carrier was selected specifically because their policies do not contain AI exclusions, which means claims arising from AI agent operations, model failures, and autonomous actions are explicitly covered. This is a deliberate choice — many carriers in the market are adding AI exclusion clauses, and we chose one that does the opposite.
- • Cyber + E&O with affirmative AI coverage (no AI exclusions)
- • General liability (Business Owner's Policy)
- • Certificate of Insurance available on request
- • Additional Insured endorsement available for enterprise clients
Vendor Questionnaire Turnaround
We maintain pre-filled responses for SIG Lite and CAIQ v4 questionnaires with evidence references mapped to each control. For enterprise procurement teams, we can typically return a completed vendor questionnaire within 24–48 hours instead of the 2–3 weeks that is standard in the industry.
If you have a custom security questionnaire, send it to security@1404.io and we will turn it around on the same timeline.
Infrastructure
Client environments are hosted on AWS (us-east-1 and us-east-2) with automatic TLS via Caddy reverse proxy. Administrative access runs through a Tailscale WireGuard mesh VPN — no management ports are exposed to the public internet.
The architecture follows defense-in-depth with five isolated Linux user tiers (admin, application, agent-service, per-client workers, per-client MCP processes), per-client iptables egress rules, three-tier credential vaults, secret scrubbing on all agent output, and immutable agent instruction files. No single compromised layer provides access to client data.
Backups run on a three-layer strategy: local daily (30-day retention), remote daily (30-day retention), and S3 Glacier weekly (52-week retention). Recovery targets are 1 hour RTO and 24 hours RPO for cloud infrastructure, verified through quarterly restoration tests.
Incident Response
Our incident response plan defines four severity levels with escalating response and resolution targets. All incidents are documented with full timelines, root cause analysis, remediation steps, and lessons learned.
| Severity | Response | Resolution Target | Client Notification |
|---|---|---|---|
| Critical | 15 minutes | 4 hours | Within 24 hours |
| High | 1 hour | 8 hours | Within 48 hours |
| Medium | 4 hours | 24 hours | Within 72 hours |
| Low | 24 hours | 5 business days | As applicable |
Documents Available
Under NDA
- • SOC 2 Type II Report (available Q3 2026)
- • Penetration Test Report (available Q2 2026)
- • AI Governance Framework
- • Risk Assessment & Red Team Report
On Request
- • Data Processing Agreement (DPA)
- • HIPAA Business Associate Agreement (BAA)
- • Certificate of Insurance (COI)
- • Vendor Questionnaire Responses (SIG Lite, CAIQ v4)
- • Master Services Agreement (MSA) with SLA exhibit
Public
Subprocessor List
Last updated March 2026
| Provider | Service | Data Processed | Location |
|---|---|---|---|
| AWS | Infrastructure hosting | All client data | US (us-east-1, us-east-2) |
| Anthropic | AI model API (Claude) | Prompts & responses (30-day retention, training opt-out) | US |
| Microsoft | M365 integration | Email, files, calendar (per client) | US |
| Google Workspace integration | Email, files, calendar (per client) | US | |
| GitHub | Source code hosting | Application code | US |
| Intuit | QuickBooks integration | Financial data (per client) | US |
| Smartsheet | Project management integration | Project data (per client) | US |
| Tailscale | Admin VPN | No client data transits | US |
Monitoring
System status and incident history are published at status.1404.io. Audit logs are retained for a minimum of 12 months. Agent transcripts, API call logs, and knowledge store activity are all logged with timestamps and full traceability.
Security Contact
For security inquiries, vulnerability reports, document requests, or vendor questionnaires:
We acknowledge all security reports within 24 hours and aim to resolve confirmed vulnerabilities within 72 hours.