Metallic® is the BaaS (backup-as-a-service) division of Commvault®, a worldwide leader in intelligent data
management. Built leveraging Commvault IP, and with the best of Azure PaaS and native services, Metallic
delivers enterprise-grade backup with the simplicity of SaaS. With sophisticated protocols and a hardened,
multi-layered security approach, Metallic® SaaS Backup helps customers protect critical endpoints, SaaS
applications, and cloud and on-premises workloads now and in the future – as IT strategies continue
to shift and evolve. The following is a summary; for a full description of Metallic security, features and
functionality, and user terms and conditions, please see the associated user documentation.
Metallic is architected for scale and performance and separates the control plane and the data plane:
The control plane, provides features and functionality such as the user experience, job management
and user security. The control plane runs in Microsoft Azure and provides a web-based interface for user
access. Customer data itself does not flow through the control plane, minimizing network bandwidth
The data plane encompasses all features and functionality of data protection and management
operations. It ensures that backup data flows can be optimized to protect and manage production data
wherever it might reside – on-premises, public cloud or private cloud.
Metallic has several options for backup storage to help customers meet their RPO and RTO objectives:
- Metallic® Cloud Storage Service: Metallic offers a fully-managed cloud backup storage, built on Microsoft Azure. Customers can set policies to place their backup data in one or more Azure regions helping meet data residency requirements. Unlimited Metallic Cloud Storage is included in Metallic® backup solutions for Office 365, Dynamics 365, Salesforce, and Endpoints as part of the per user subscription costs.
- SaaS Plus: For hybrid-cloud workloads like Metallic® Database, Metallic® File & Object, and Metallic® VM & Kubernetes, Metallic offers unique storage target flexibility. Customers can leverage both cloud nativestorage and local backup copies in concert, for stronger data resiliency and recoverability, including:
- Bring Your Own Cloud Storage – customer cloud, such as Azure or AWS
- Metallic® Cloud Storage Service – cloud storage target that’s fully-managed by Metallic
- Bring Your Own On-Premises Storage – customer on-premises server via any disk or NAS device
- Hyperscale™ X – Commvault appliance, used for on-premises backup storage
Metallic® Cloud Storage Service (included with Metallic® Backup solutions for Office 365, Dynamics 365,
Salesforce, and Endpoints and offered as a standalone service), is a cloud backup storage target, built on
Microsoft Azure. To ensure durability and availability for disaster recovery, stored data is replicated six times
across two geographically separated regions. By default, Metallic will geo-locate the user and provision
storage in the nearest Metallic Azure data center. Customers also have full autonomy to choose one or more
Azure storage regions around the world and associate users to those regions, ensuring that their backup
data is stored in locations that meet data residency and compliance requirements. For more information
on data center regions currently supported with Metallic, please see our documentation here: https://docs.
Metallic leverages a hardened, multi-layered approach to data protection, providing robust controls that
prevent threats on backup data and ensure copies are highly recoverable from deletion or malicious attack.
Natively, we protect all backups at the storage level. Backup copies and operations live in a virtually airgapped location, in a separate security domain, decoupled from source environments. Retention locks are
applied to prevent unwarranted modifications to data retention policies. Multi-factor authentication, AES
256 bit at-rest/in-flight encryption, firewalls, and zero-trust access controls block internal and external
movement of data by unauthorized parties. All security protocols employed adhere to security best
practices and are based upon SOC2 type II and ISO27001:2013 compliance requirements.
Deduplication and Compression
Metallic’s compression and block-level deduplication improves network bandwidth utilization and reduces
storage footprint. Cloud native storage APIs are used to efficiently send and retrieve data to the cloud when
using cloud storage.
Networking and Communications
All network communications are managed via mutually authenticated SSL (MA-SSL) connections. Certificate
generation, revocation and renewal are automatically managed. Control connections from on-premises
components to the Metallic service control plane are outbound only over port 443, minimizing the network
access necessary to leverage Metallic. Connections to cloud storage also use HTTPS on port 443 outbound
only. Data is always encrypted at source and in transit.
Metallic employs a DevSecOps approach to enhance information and operational security. This includes
following industry best practices to isolate test, dev, staging and production environments. Testing and
review for security risks are performed regularly by both in-house and external third parties, including routine penetration testing, red team activities, anti-virus assessments and system and process audits.
Metallic service deployment uses layered security including firewalls, WAF and MFA to prevent any unauthorized and malicious access. Application Security assessments and vulnerability checks are regularly performed to maintain security hygiene and posture. Metallic also follows Open Web Application Security Project (OWASP) best practices to secure web services and APIs, and maintains SOC2 Type II and ISO.IEC 27001:2013 certifications.
Metallic.io Security Architecture
Separate Security Domain
Metallic leverages a 100% cloud-native architecture and maintains backup and restore operations outside of
customer environments – in a separate security domain. One-way, TLS-encrypted secure tunnels, are used to secure storage targets, without a physical network connection. Air-gapping controls within the solution include the ability to turn off connectivity to data stores when not needed, effectively severing the data path and reducing the risk of successful ransomware attacks in production environments impacting backup copies.
Metallic is a multi-tenant SaaS Platform with built in-segregation between tenants. Customer data is
completely isolated and stored in separate locations, with unique data encryption keys per tenant. Metallic also leverages zero-trust access controls, permitting only the data owners (customer) access through the Metallic Service.
Encryption is an integral part of Metallic. All backup data is compressed, deduplicated, and encrypted by
default from the source, on the network, and at rest using AES256. During transport, data is encrypted with
a tenant specific Data Encryption Key (DEK) before transferring the data across networks. Compression and
deduplication also obfuscate data, providing additional security. Metallic is FIPS 140-2 certified.
Customer data backed up within Metallic is encrypted and not accessible or readable by Commvault
employees. Access to data stored within Metallic is solely subject to Customer’s policies and authorized user permissions.
Data Owner Right to Delete Backup Data
Data that has been backed-up can be permanently deleted so that it is no longer available for browsing and
recovery. Data can only be deleted/purged by users with appropriate access and permission. Once data has
been securely deleted, it cannot be restored.
Key Management and Generation
Key management includes the ability to both generate random encryption keys for backup data and also
manage the secure storage of these keys. To create the keys, Metallic uses CTR_DRBG, which randomly and
dynamically generates keys via:
- Random 128-bit or 256-bit data encryption keys (DEK) for every client and storage policy copy combination, and initial vectors (IV) for CBC chaining during data encryption.
- Random 128-bit or 256-bit master key for the storage policy copy in absence of third-party key management server.
Metallic manages all encryption keys and follows best practices and procedures based on NIST Special
Publication 800-57 as follows:
- Metallic generates a master key for each storage policy copy
- Metallic generates a pair of 3072-bit KEK (key encryption keys) RSA public-private keys:
- Uses a master key to encrypt the private portion of KEK.
- Uses the default key to encrypt the public portion of KEK.
- Metallic encrypts both the master key and RSA public-private key pair, and stores them in a secure lockbox.
Metallic uses AES Key Wrap Specification to securely encrypt and secure all keys with CRC32 embedded.
Metallic also automatically rotates keys every 30-days, without user intervention.
Identity and Access Management
Access control is based on the Principle of Least Privilege and Zero Trust models in place designed to limit
elevated and unauthorized access to both data and service infrastructure. We employ industry standard
security best practices for all access to our services with tight audit-controls managed via best-in-class
security and DevSecOps tools, services, and processes.
User Application Access
Metallic supports SAML and MFA authentication, where customers can implement their own password
management controls and policies. Password complexity is enabled, requiring at least 12 characters, the use
of three unique characters, and cannot contain more than two characters from the username. Password
change frequency is 42 days, and at least three past password histories are logged. Metallic uses lockbox
and vaults to secure customer passwords and credentials.
Administrators can limit the number of times a user can attempt to logon to Metallic. After the limit is
reached, the user account is locked for the time period defined by the administrator. For more information,
see Limiting User Logon Attempts.
When Two-Factor Authentication is activated, users must enter a 6-digit PIN (Personal Identification Number) along with their passwords to access Metallic.
Metallic has built in Role Based Access Controls (RBACs) to restrict access to authorized users. A role
is a collection of permissions administrators assign to users and entities to create a three-way security
association. Roles can be assigned to grant appropriate access to any user or user group.
Integration with External Domains
Administrators can manage a single set of users through integration with external directory services like
Active Directory and Oracle Directory. Metallic roles and entities can be assigned directly to an external group or user.
Metallic supports SAML authentication. SAML can be used to create a single identity for each user for a
single sign-on logon for all applications. A SAML User Registration Workflow is available to create usernames.
Metallic prevents users and administrators who are not client owners from seeing the data on the client. This includes Metallic employees and personnel, who do not have access to customer data.
Metallic is a Software as a Service consuming Azure Cloud IaaS. Leveraging the cloud’s shared responsibility
model, Metallic helps ensure all data and access to the data is secured. Metallic leverages Microsoft Azure
for perimeter and physical access controls. For Azure data centers, see the link for an in-depth security
Governance and Risk Management
Metallic is ISO27001:2013 and SOC 2 type II compliant, maintaining and implementing industry standard security and privacy policies. Best-in-class cloud and SaaS service configuration management tools are employed to ensure any deviations from configurations detected are remediated automatically. All access is logged for audit and compliance reasons. Compliance with information security policies and procedures are strictly enforced and all Commvault’s employees receive training to ensure they remain aware of their role in maintaining the security, availability, and confidentiality of customer data among their other job responsibilities.
Metallic audit trails allow you to track user operations who have access to Metallic services and can help in
determining the root cause or source of operations performed within the environment. All changes are logged per Metallic SRE and DevSecOps requirements and follows SOC2 Type II and ISO27001:2013 compliances and standards.
Incident Response Plans
Metallic has an Incident Response Plan (IRP) program and it is tested annually by a certified third party as part of our normal ISO and SOC2 certification requirements. Daily scanning is performed and procedures are tested through internal and external audits.
Metallic Disaster Recovery (DR) procedures are based on the Commvault BCDR policies. The DR procedures
encompass all production services within Metallic, are well-established, reviewed every year, and continuously enhanced at scale to support our customers.
When providing services, Metallic ensures compliance with specific GDPR requirements for data processors.
When third parties are appointed to act as sub-processors, appropriate terms are in place to comply with the GDPR and safeguard customers’ data. Please see our GDPR Compliance page for more details.
Metallic Government Cloud, our portfolio of solutions for US government agencies and private businesses
handling federal data, is currently the ONLY data protection solution to meet FedRAMP High status. Metallic
Government Cloud is hosted exclusively on Azure Government Cloud, and incorporates 421 required security
controls to meet the most stringent confidentiality, integrity, and availability standards set forth by the US
government. For more information on Metallic Government Cloud, please visit the following page for more
Certifications and Compliance
For full list of certifications and standards met by Metallic, please visit the following webpage.