BigMemory Max 4.3.1 | Product Documentation | Big Memory Max Security Guide | Overview of BigMemory Max Security
 
Overview of BigMemory Max Security
Security can be applied to both authentication (such as login credentials) and authorization (the privileges of specific roles).
We recommend that you plan and implement a security strategy that encompasses all of the points of potential vulnerability in your environment, including, but not necessarily limited to, your application servers (Terracotta clients), Terracotta servers in the TSA, the Terracotta Management Console (TMC), and any BigMemory .NET or C++ clients.
Note: Terracotta does not encrypt the data on its servers, but applying your own data encryption is another possible security measure.
Securing the Terracotta Cluster and Components
*Terracotta Server Array (TSA) using SSL, LDAP, JMX. See:
*Introduction to Security .
*About Security in a Cluster.
*Setting Up Server Security.
*Setting Up a TSA to Use the Terracotta Management Server.
*Using LDAP or Active Directory for Authentication.
*Using Encrypted Keychains.
*Terracotta Client (your application). See:
*Enabling SSL on Terracotta Clients.
*Using Encrypted Keychains.
*Serialization: Securing Against Untrusted Clients
*Terracotta Management Console (TMC). See:
*The Terracotta Management Console User Guide.
*BigMemory Max monitoring without the TMC. See:
*Configure Securing Using JMX Authentication.
*BigMemory .NET and C++ clients. See:
*The Cross-Language Clients User Guide.
Copyright © 2010 - 2019 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.