Introduction to MATRIXX Cloud Native Security

The information in MATRIXX Security is best-practice information and identifies MATRIXX-specific security considerations and implementations. For container-specific and Kubernetes security information, see the third-party documentation.

MATRIXX has multiple security layers:
  • Operating System Security
    Important: MATRIXX leverages the security concepts and functionality provided by Kubernetes for cloud native security. For information about securing your environment, see the discussions about Kubernetes security concepts in the Kubernetes documentation. For information about role-based access control for MATRIXX components, see the discussion about role-based access control in MATRIXX Configuration.
  • MATRIXX Engine Security
  • Network Security
  • Application Security
  • Database Security

Network and application node security mitigates the risk from external threats such as Dedicated Denial of Service (DDoS) attacks, breaches to obtain user details and credit card information, and so forth. Network configuration and the outer gate-keeping web and application servers provides the front line against these threats.

Security policies should account for internal threats, auditing processes, and accountability. The configuration of database security, the configuration of operating systems, and overall security practices mitigate external threats and ensure adequate internal processes that address employee protection and regulatory compliance. External threat assessments are usually well-defined; however, internal threats require a much more balanced approach to risk assessment.

Servers should have limited access points for event processing, business support systems, maintenance and monitoring, and local access.