SOC 1 Type II
Readiness programTransaction, reconciliation, access, and change-management controls are being formalized for future auditor review.
Security at Ironclad
Protecting customer data should be built into the product, the infrastructure, and the way the company operates. Ironclad is building its trust program around the controls and evidence buyers expect from regulated retail software.
Public claims should track completed controls and real evidence. Formal reports and certifications are not yet published.
Transaction, reconciliation, access, and change-management controls are being formalized for future auditor review.
Security, availability, logging, environment separation, and incident response controls are being built toward an operating evidence window.
Administrative and technical safeguards are being mapped for healthcare-adjacent workflows, with encryption at rest treated as a mandatory internal standard.
Privacy notice, retention, rights handling, vendor review, and sensitive-data processes are being implemented for California readiness.
Architecture boundaries, access model, encryption posture, monitoring approach, and the operating assumptions behind the trust program.
A compliance-grade guide for standing up backend, worker, database, and future AI services on AWS with hardened network and key-management controls.
Access control, incident response, backup and restore, vendor review, retention, and subprocessor registers that back readiness claims with maintained artifacts.
Compute, storage, key management, secrets management, backups, and core production hosting.
Perimeter security, delivery optimization, and protective controls at the edge.
Infrastructure and application telemetry, alert routing, and compliance-relevant operational visibility.