StorCycle Protect your data image header
Cyberattack, ransomware, natural disaster or simple human error – any of these can destroy an organization’s most valuable asset – its data — in an instant. StorCycle software protects data through end-to-end checksums; encrypting on all storage targets; and with the ability to store multiple copies on multiple storage mediums, enabling genetic diversity of storage mediums. StorCycle has the ability to store data on tape for offsite or vaulted storage, creating an impenetrable air gap that guarantees data security. StorCycle is fully ADFS compliant – file permission will remain intact regardless of where data is stored. StorCycle will even analyze the protection level of user-defined migration policies and assign a Perpetual Score* indicating the level of protection each migration policy creates.

*Perpetual Score available in a future release

Data Lifecycle management for protection square image

Active Directory Integration

StorCycle is installed on a Windows server and includes integration with Active Directory (AD). Active Directory integration provides for several benefits:

  • AD users can be granted various permissions for access to the StorCycle web management interface (see section above).
  • When files are migrated by StorCycle, their AD-based access permissions are recorded. When the files are restored, those access permissions are reapplied.
  • All AD users can optionally be given permission to be able to restore files migrated by StorCycle.

Data Integrity and Protection

Spectra StorCycle includes a number of features to ensure that migrated data is safe and secure, both when initially migrated and in the future.

File Checksum

When a file is read by StorCycle to be migrated, it creates the checksum of the entire file as it is written to the target storage. The checksum acts as a thumbprint of the file that can be reproduced to ensure that the file has not changed. StorCycle stores each file’s checksum in its database, and this value can be accessed and exported as part of a migration job’s manifest.

When StorCycle restores a file, it will again validate the checksum to ensure that the file has not changed. If StorCycle detects a change in checksum value, it will report an error. Files with reported errors can still be accessed and restored.

StorCycle uses the SHA-256 checksum method. This modern checksum method is commonly used, works well with Intel and AMD processors, and minimizes risks of collisions and attacks. A basic level of checksum verification is also included in the TCP/IP communication used by StorCycle. For StorCycle storage targets supporting HTTPS/SSL (BlackPearl, S3), the HTTPS protocol also includes basic checksum verification.

X