HCP System Management Help


Data integrity and security

HCP includes many features specifically designed to protect the integrity and ensure the security of stored data:

Write-once, read-many (WORM) storage — Once the data for an object is stored in the repository, HCP prevents that data from being modified or overwritten.

Node login prevention — HCP does not allow system-console logins on its nodes. This provides a basic level of protection not only for the stored data but also for the system software.

Secure Sockets Layer (SSL) — HCP can use SSL to ensure the privacy of HTTP and WebDAV access to namespaces. It always uses SSL to secure the Management and Search Consoles. Additionally, use of the HCP management API requires SSL.

For information on using SSL with HCP, see Managing domains and SSL server certificates.

Content verification service — Each object has a cryptographic hash value that’s calculated from the object data. The content verification service ensures the integrity of each object by periodically checking that its data still matches its hash value.

For more information on the content verification service, see Content verification service.

Scavenging service — The scavenging service protects namespaces from the loss of system metadata. If the service encounters an object with invalid metadata, it restores the correct metadata by using a copy from another location.

For more information on the scavenging service, see Scavenging service.

Retention policy — Each object has a retention setting that specifies how long the object must remain in the repository before it can be deleted; this duration is called the retention period. HCP ensures that objects are kept until their retention periods expire. The only exception to this behavior occurs in namespaces in enterprise mode. In these namespaces, users with explicit permission to do so can delete objects that are under retention. Such deletions are recorded in the tenant log.

For more information on enterprise mode, see the description of retention mode in Regulatory compliance. For more information on the retention policy, see Retention policy.

Shredding policy — Objects can be marked for shredding. When such an object is deleted, HCP overwrites its storage location in such a way as to completely remove any trace that the object was there.

For more information on the shredding policy, see Shredding policy.

Data access authentication — The HTTP, HS3, WebDAV, and CIFS protocols can be configured to require authentication for access to an HCP namespace. If these are the only protocols enabled for the namespace, users and applications must present valid credentials for access to the namespace content.

HCP supports both local and remote authentication methods. For remote authentication, HCP supports Windows Active Directory® and RADIUS.

For more information on configuring namespace access protocols to require authentication, see Managing a Tenant and Its Namespaces. For information on local and remote authentication, see User authentication.

Data access permission masks — Data access permission masks determine which operations are allowed in a namespace. These masks are set at the system, tenant, and namespace levels. The effective permissions for a namespace are the operations that are allowed by the masks at all three levels.

For more information on data access permission masks, see Setting the systemwide permission mask.

Data access permissions — Data access permissions determine which operations a user or application can perform on the objects in an HCP namespace. These permissions can be:

oAssociated with a tenant-level user or group account, in which case they apply to all objects in the namespace

oSpecified in the namespace configuration as the minimum permissions for authenticated or unauthenticated users, in which case they apply to all objects in the namespace

oSpecified in an ACL, in which case they apply to the individual object for which the ACL is defined

For more information on data access permissions that apply to all objects in a namespace, see Managing a Tenant and Its Namespaces. For more information on ACLs, see Using a Namespace.

Virtual networking — Virtual networking is a technology that enables you to define multiple logical networks over which clients can communicate with HCP. You can assign different networks to different tenants, thereby segregating network traffic to and from the namespaces owned by one tenant from network traffic to and from the namespaces owned by other tenants. This segregation enhances the privacy and security of data transmitted between clients and the HCP system.

For more information on virtual networking, see Network administration.

© 2017 Hitachi Vantara Corporation. All rights reserved.