Kiln

Kiln is SOC 2 Type II compliant. On SOC2C this listing is Listed.

Kiln is SOC 2 Type II compliant. A Type II report covers how security controls operated over a period (typically 3 to 12 months), a stronger signal than a point-in-time Type I.

Yes. Kiln's SOC 2 status, frameworks, auditor, and renewal timing are on SOC2C for vendor risk and security reviews. Request the underlying report through SOC2C to complete your third-party risk file.

Kiln hasn't listed its penetration testing on SOC2C yet. SOC 2 Type II programs typically include periodic third-party penetration tests; the company can add who performed theirs.

Security isn't a single yes/no, but Kiln is SOC 2 Type II compliant. SOC2C verifies its compliance posture and shows how strongly each fact is proven.

Kiln employs a comprehensive multi-layered security infrastructure that includes SOC2 Type II attestation, multi-cloud deployment across providers like AWS, GCP, and OVH, with all sensitive information secured in Hashicorp Vault⁠ instances⁠. The infrastructure features strict access controls, network isolation per blockchain, and geographic distribution of validators for resilience⁠⁠. Security measures include automated GitOps workflows, continuous monitoring, and regular security audits⁠. The platform is protected by multiple layers of anti-slashing protection endorsed by the Ethereum Foundation, and is backed by insurance coverage from providers like Amtrust and MunichRe.

We have a business continuity and disaster recovery plan which we were certified for as part of our successful SOC 2 audit. We have architected our platform to be resilient to underlying failure. Our main infrastructure is spread on 3 availability zones. In case of the loss of an availability zone we have a procedure to move resources on the remaining two. In case of the loss of all of our AWS availability zone in our main region, we can still access our Vault from a backup cloud provider location (Scaleway or another AWS region) and rebuild our infrastructure there. All of Kiln infrastructure is infrastructure as code (IAC) and stored in version controlled system (Git) and therefore can be recovered quickly. We run services in two additional clouds (Scaleway and OVH) which we could spin up in fast. We routinely test the migration of validator servers to new infrastructure platforms.

By design Kiln collects a very small amount of data - only what is necessary to provide our service: customers' email addresses, organisation names, and public wallet addresses which customers are delegating from. All other data surfaced is public blockchain data or derived from it. Kiln encrypts data at rest and in transit for all of our resources. We use tools like Amazon Web Service’s Key Management System (KMS) to manage encryption keys using hardware security modules for maximum security in line with industry best practices. Customer login data and organisation names are stored in industry-leading SaaS platform Auth0 (by Okta). Some analytics information is held in Segment (Twilio) and Mixpanel. Public wallet addresses are stored in AWS database services.

No, by design Kiln never has access to your assets. You are only delegating the rights to validate the blockchain with your funds, but no other rights are transferred to Kiln. On all dPOS chains (all except ETH), the staker always can unilaterally unstake their assets. It is therefore fully non-custodial at the protocol level. If Kiln disappears, the customer can issue this unstaking transaction using their custodian, a frontend app from the relevant ecosystem, or manually using a script. On Ethereum, this is slightly complicated by the fact that validator exits are done by issuing a transaction that includes a message signed by the validator private key, which is held by Kiln. Kiln therefore enables customers to retrieve this pre-signed message such that they can exit unilaterally. - To fund a validator, the depositor issues a deposit transaction into the Beacon Chain deposit contract. This is the contract in which all the ETH staked sits - currently 34M ETH / $73B. It is not upgradeable. - The only address this ETH can go to upon exit of the validator is to the `withdrawal_credentials` address set by the depositor upon deposit - Kiln’s batch deposit contract is a thin layer on top of the Beacon Chain deposit contract, it ‘batches’ calls to this contract for gas optimisation and does not hold any assets - Kiln customers can exit validators unilaterally at any time by sending a pre-signed exit message which they can retrieve at any point from the Kiln API - specs Following the Pectra upgrade (May 2025) it will be possible to trigger exits from the withdrawal wallet (similar to all dPOS protocols), so presigned exit messages will no longer be required.

We have purpose built our Ethereum infrastructure to mitigate slashing risk as much as possible. Our anti-slashing practices are endorsed by the Ethereum Foundation, and we have written about them at length in this blog post.