{"blog": "https://blog.validationcloud.io/", "logo": {}, "name": "Validation Cloud", "country": "CH", "discord": "", "rssFeed": "https://rss.app/feeds/aQdV3DXl0oZPoSkL.xml", "twitter": "https://twitter.com/ValidationCloud", "website": "https://www.validationcloud.io/staking", "youtube": "https://www.youtube.com/@ValidationCloud", "linkedin": "https://www.linkedin.com/company/validationcloud/", "telegram": "", "stakeLink": "https://app.eigenlayer.xyz/operator/0x81a28c9f24fa19f3292178464427bd71c0dad411", "description": "

Validation Cloud has worked diligently to become SOC2 Type 2 compliant, showing its strong commitment to platform security and availability.

With respect to validators, we have a high availability Kubernetes cluster that is run as a stateful set. Each validator is accompanied by a remote signer, which is the only infrastructure that can access the key - based on the principle of least privilege. The validator keys are created in an ephemeral, secure environment that only has access to write the keys into AWS Secret manager and only the remote signers have access to read those keys.

For the remote signer, we utilize Web3Signer built by Consensys with a common postgres slashing database to prevent slashings.

With respect to monitoring and alerting, we utilize Datadog to evaluate logs and metrics from the various components of the tech stack 24/7/365. We have alerts for missed attestations, missed proposals, and slashing along with other common alerts tracking all components of the infrastructure.

", "supportChat": "https://app.validationcloud.io/"}