Conduit XYZ is entrusted by our users to keep their data safe. We operate under a shared responsibility model. Conduit XYZ is responsible for the secure delivery of the underlying infrastructure and our users are responsible for ensuring they leverage concepts like strong account management practices, enabling MFA on their accounts, anonymous private keys, and secure private key management. If you have any questions or concerns regarding Conduit XYZ security practices please get in touch with us.
ConduitXYZ leverages Stripe as our payment processor to handle all credit card and payment information. Stripe has been audited by an independent PCI Qualified Security Assessor and is certified as a PCI Service Provider level 1, which is the most stringent certification available in the payment industry.
Conduit does not collect or store user credit card information and does not have visibility into the payment transaction details to ensure the security of our users. To better understand how Stripe protects data please visit the Stripe Security page.
ConduitXYZ leverages Google Cloud Platform which undergoes regular independent audits for a range of compliance standards including but not limited to ISO 27001, FedRAMP, CSA STAR, SOC 2, and PCI DSS.
ConduitXYZ is hosted on Google Cloud Platform (GCP), which employs some of the best security practices in the industry. The practices in use are described in the Google security whitepaper and Google infrastructure security design overview, and includes:
All data centers have perimeter fencing, vehicle access barriers, 24x7 security guards, electronic access cards, alarms, metal detectors, biometrics, laser beam intrusion detection, interior and exterior cameras with tracking, access logs, and other security features. More details may be found on the [GCP Trust Center](https://cloud.google.com/trust-center).
GCP uses custom stripped-down, custom-built servers with only the necessary components and network equipment with Titan chips, a chip-based root of trust for verification, identification, and authentication, a secure boot stack with cryptographically signed BIOS, bootloader, kernel, and base operating system image, and automated patching of firmware and software vulnerabilities. Virtual machines are isolated from the host and each other via a specially hardened version of the open-source KVM virtualization stack.
GCP makes use of a private, global fiber-optic network extending to points-of-presence near the end user's local ISP. All internal connections establish automatic encryption of all internal WAN traffic using AES and elliptic-curve Diffie Hellman key exchange. GCP's private global network has a fully distributed firewall rule enforcement, IP spoofing protection, systematic anomaly detection, and uses Application Layer Transport Security to protect RPC Calls.
All data stored in GCP is encrypted at rest with the industry-standard AES cipher, using regularly rotated encryption keys that are integrated with cryptographically authenticated service identities and automatically deleted on service termination. Full disk encryption is in use and decommissioned hard drives are securely erased with two independent verification processes and physically destroyed and verified on-premise.
All Google employees undergo relevant background checks and security training and must sign confidentiality agreements. Only a small group of employees have access to customer data, on a least-privilege need-to-know basis, with all access monitored by dedicated audit teams. Less than one percent of employees have physical access to data centers. All employee access is authenticated, authorized, and encrypted using Google's BeyondCorp security model.
Access to GCP Data Centers is tightly controlled, only a limited number of Google Employees have access to the Data Center floor. ConduitXYZ employees do not have physical access to data centers, nor access to the underlying Google infrastructure.
Conduit.xyz Users can log in using their Google account via an OAuth 2 flow, or an email address and password with the optional to enable two-factor authentication, which is strongly recommended. The user's password is never transmitted to us, and we do not gain access to any external resources that belong to the account.
Access to Conduit.xyz services and resources by end users is encrypted in transit with transport layer security (TLS). ConduitXYZ does not support the older SSLv2, SSLv3, TLS 1.0 and TLS 1.1 protocols and are disabled, as are several older cipher suites, since these have known security vulnerabilities. Internally, data is encrypted in transit and at rest as described under the Infrastructure security section.
We only maintain records required to provide the service to customers. This data is retained to meet our legal obligations, once the data is no longer needed it is removed from active systems.
Data will still be retained in our snapshots for a limited time, as outlined in our service agreement, to allow for recovery in the case of accidental or malicious removal.
ConduitXYZ uses continuous delivery and integration to enable rapid and systematic development, testing, and deployment of our product. These services include automated error reporting and monitoring to alert us of problems. This ensures the ConduitXYZ team can quickly and effectively respond to potential bugs and security issues, and reduces the risk of error.
All data is encrypted in transit and at rest as outlined in the Infrastructure security section.
ConduitXYZ collects the minimum information required to open and establish an account. This data is used to meet our legal obligations and to collect payment. Please visit our Privacy Policy for additional information on data collection.
By default, ConduitXYZ provides anonymous private keys. These keys are not known or accessible to the user. They serve as a protection layer for ConduitXYZ users by removing the need to provide your private key and reducing the risks associated with storage of private keys in a cloud service.
Employees access corporate resources using two-factor authentication via Google Accounts, and utilize role-based access controls to ensure employees only have access to the systems required. All remote access is encrypted via HTTPS transport level security. Access to customer data is restricted to a limited number of roles.
Internal services are isolated from the Internet unless required to be public. Services only have access to the specific resources they need, with the minimum necessary privilege level, using a combination of service-specific cryptographically signed access tokens or passwords and network-level firewall rules. Access tokens are stored encrypted in our key management system, only available via authenticated and encrypted RPC calls from the ConduitXYZ systems, and provided to specific applications or services.
All data is removed shortly after service cancellation or deletion of roll-up(s). Because transaction data becomes public on the MainNet, data retention is not required. Conduit maintains backups of core critical systems to allow for recovery in the case of accidental or malicious removal. Users can also contact us to have their data removed. Storage devices are securely decommissioned after use as outlined in Infrastructure security.
Due to the nature of blockchain, once transactions have been posted to the MainNet all roll-up transactions are no longer required to be stored. When a user deletes a roll-up, closes or deletes their account with Conduit XYZ all data is removed as described in our Data Retention and Removal section.
Conduit XYZ performs internal audits to ensure systems are meeting internal requirements. Audits are performed by our engineering staff as needed and at least on an annual basis.
We perform patching on our infrastructure on a continuous basis. To ensure the reliability of systems, patches and updates are performed once they are identified and classified. Once updated and patches are classified they are applied following Conduit XYZ internal processes.
ConduitXYZ utilizes Stripe to process Credit cards and payments. ConduitXYZ never receives credit card information, or has access to payment information provided by customers. Additionally, payment data is removed from Stripe as soon as the customer updates their card information or closes their account.
All data provided to ConduitXYZ via the Web GUI or API is stored permanently within the continental US. However, during delivery to end users it may be stored transiently in locations outside of the continental US, through CDN caches, networking equipment, and browser caches. Data controlled by ConduitXYZ, like our user database and email processing, may be stored in the U.S. with third-party processors employed by us in order to deliver the service - see below for more information.
Data provided via our API is only stored in Google Cloud Platform, and never shared with any other third parties. Other customer data for which we are a controller, such as our user database, email processing, error reporting, and so on, may be sent to certain third-party processors which we employ to deliver our services, as detailed in our service agreement.
ConduitXYZ is built on cloud native technology using fully redundant and distributed systems that run across multiple zones in multiple data centers, and is able to withstand the loss of a single component or entire data center without significant service disruptions. Components leveraged by ConduitXYZ are regularly taken out of service during routine maintenance, without affecting availability, and with the assistance of Google Cloud Platform's live migration technology, we can transparently migrate virtual machines to other hosts prior to infrastructure maintenance.
The load balancers and WAF leveraged by ConduitXYZ can absorb many types of DDoS attacks (distributed denial of service) as well prevent other common application attacks. Due to the native cloud architecture, many of our backend systems will automatically scale to handle increased load when required.
Data centers utilized by ConduitXYZ have primary and alternate power sources, as well as backup generators, each can provide enough electrical power to run the data center at full capacity. Additionally, all Data centers in use by ConduitXYZ have automated fire detection and suppression equipment along with other safety features.
Conduit XYZ uses industry standard tools to monitor services provided to customers. Every service provided is monitored to ensure required uptime through our automated tooling providing an overview of usage, activity, problems and general status.
When issues are detected, or services reach a predefined threshold alerts are generated to the engineering team to address and prevent issues. Actions and security events are also logged allowing the team to detect security risks, understand user activity and access, and take any preventive or proactive actions to ensure stability of the services.
ConduitXYZ leverages cloud native architecture to ensure reliability and uptime. Critical systems required to ensure the uptime and availability of ConduitXYZ are continuously snapshotted every 10-15 min to ensure systems can be restored quickly when required. Snapshots include all redundant components. As previously described in our Data Retention and Removal section, once data is posted (approximately every hour) on the main blockchain, data becomes public and therefore backup of the data is purged and removed.
ConduitXYZ maintains snapshots of all critical systems. These snapshots are only accessible by employees whose roles require access to view, test, and restore a snapshot. Leveraging cloud native architecture, critical systems can be restored within 12-24 hours of a complete outage.
All employees are required to sign confidentiality agreements and are only given access to the systems they need for their role. ConduitXYZ issues employees a computer to perform work. Access to corporate resources and third-party services are always encrypted and protected with multi-factor authentication.
If a security issue or data leak is discovered, ConduitXYZ will notify the affected users and relevant authorities in line with current regulations. We will also publish timely reports of operational issues on our status page, which allows users to opt-in to email notifications if desired.
ConduitXYZ takes security seriously. If you have found a security issue or vulnerability and would like to disclose the finding to the team, please contact [email protected].
The team will verify the report and take corrective action as soon as possible, then notify all relevant parties.
