Ruby Logo

Security & resilience

A transparent operating model for critical blockchain infrastructure

This page summarizes our operating principles. Engagement-specific controls, responsibilities and evidence are reviewed during technical due diligence and documented in the service agreement.

Secure by default

Every deployment starts from a consistent, security-focused baseline, reducing human error and keeping protection uniform as infrastructure grows.

Controlled access

Access is limited to authorized people and only the services each deployment needs, helping protect systems from unwanted activity.

Dedicated environments

Workloads can run in isolated environments with access and infrastructure boundaries tailored to your organization.

Always-on monitoring

Production systems are monitored around the clock, with alerts and agreed escalation paths when something needs attention.

Built for availability

Redundancy and failover options help services remain available when individual components or locations experience disruption.

You retain asset control

Ruby Nodes does not take custody of delegated assets. Asset control and signing responsibilities are agreed clearly for each service.

Clear accountability

Ownership, support expectations and incident responsibilities are documented before production, so every party knows its role.

Privacy considered

Personal data is handled under our privacy policy and applicable GDPR requirements, with relevant data flows reviewed during scoping.

Engagement-specific controls

What we define before production

Blockchain protocols and deployment models create different operational boundaries. We document the applicable control ownership rather than presenting one generic model as suitable for every service.

  • ✓ Infrastructure boundary and hosting locations
  • ✓ Asset custody and signing-key responsibilities
  • ✓ Network exposure and access requirements
  • ✓ Monitoring, support and incident escalation
  • ✓ Availability measurement and service commitments
  • ✓ Relevant data flows and residency requirements

Operational transparency

Public service health is available through our infrastructure dashboard. Detailed reporting and SLA measurement depend on the contracted service.

View system status →

Security and due-diligence enquiries

Contact us to review the proposed architecture, responsibility model and control evidence available for the scope of your engagement.

Contact Peter →