Home
MATRIXX Security
Application Security
Application security includes configuring web applications and gateways.

Welcome
MATRIXX Release Notes
MATRIXX Architecture
MATRIXX Installation and Upgrade
MATRIXX Configuration
MATRIXX Security
- About MATRIXX Security
- 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.
- Cloud Native Security
  The information here addresses cloud native security and includes recommendations for securing your cloud native implementation.
- Managing Certificates
  MATRIXX uses certificates signed by a trusted certificate authority, or validated by other means, to establish secure communications with another party with the corresponding private key.
- Enabling Transport Layer Security
  Transport Layer Security (TLS) provides secure internet connections by encrypting data sent between a browser, a website, and the website server to ensure that data is transmitted privately.
- Network Security
  Network zones are stacked with increasing proximity to the open internet or DMZ. Each zone is traversed by ingress and egress points through an application or server, with appropriate authentication and authorization for connecting system traffic.
- Application Security
  Application security includes configuring web applications and gateways.
  - Tracking Client Information
    For auditing and tracking purposes, Event Detail Records (EDRs) can include security information included in SubMan API requests or information can be derived from the client making the request.
  - Password Encoding
    MATRIXX applications support md5 and Spring Framework supported password encodings.
  - Configuring and Customizing My MATRIXX Security
    My MATRIXX leverages the Spring Security Framework. This section describes a sample Spring Security implementation that authenticates with the default My MATRIXX web app or with an LDAP directory.
  - Configuring MATRIXX Backoffice Customer Tool Security
    MATRIXX Backoffice Customer Tool leverages the Spring Security Framework.
  - Configuring Active Directory LDAP Authentication
    MATRIXX supports Active Directory LDAP authentication using the Active Directory-specific ActiveDirectoryLdapAuthenticationProvider in Spring security.
  - Application Security Checklist
    The following is a list of best practices for application deployment.
  - SNMP User-Based Security Model V3
    In the configuration file for the component for which you are gathering statistics, configure the parameters listed in security/c_snmp_security.html#concept_fd3_sbr_3qb__table_l1d_3cr_3qb.
- Database Security
  Depending on your MATRIXX environment, you can use multiple external databases.
- OAuth 2.0 Identity and Access Management
  MATRIXX supports third-party identity and access management application integration.
MATRIXX Integration
MATRIXX Diameter Integration
MATRIXX Call Control Framework Integration
MATRIXX TM Forum Integration
MATRIXX 5G Integration
MATRIXX 5G Event Streaming
MATRIXX Event Streaming
MATRIXX Administration
MATRIXX Web App Administration
MATRIXX Monitoring and Logging
MATRIXX Policy
MATRIXX Kafka CDR Consumer
MATRIXX Pricing and Rating
MATRIXX Pay Now
MATRIXX Subscriber Management
MATRIXX Subscriber Management API
MATRIXX Business API SDK
My MATRIXX Help
MATRIXX Backoffice Customer Tool Help
MATRIXX Third-Party Licenses
Glossary

Application Security

Application security includes configuring web applications and gateways.

Application security includes Zones 2 and 3 in Figure 1.

Multiple zones (DMX, web Services, Application Services, Network Systems) separated by firewalls. — Figure 1. Security Zones

MATRIXX Engine must be deployed within a secure area of your network. Think of MATRIXX Engine as a black box server with limited access points for event processing, business support systems, maintenance, and monitoring.

The Gateway Proxy restricts which applications, services, and IP addresses can communicate with MATRIXX Engine. It is located between provisioning and self-care systems and MATRIXX Engine and uses Linux firewall rules to enforce access restrictions. This prevents unauthorized services from communicating with the engine.

The Business API Gateway should be in Zone 4 so that it is separate from MATRIXX Engine and not directly exposed to the internet like the web services in Zone 3.

My MATRIXX

In cloud native environments, you install My MATRIXX as a separate pod with its own Docker image. You can deploy it on the same nodes as the Gateway Proxy pods or on remote nodes that communicate through the Gateway Proxy to MATRIXX Engine. MATRIXX Support recommends that you deploy My MATRIXX separately from the Business API Gateway pods, because the tool is a design-time environment for creating configuration files to deploy to the runtime MATRIXX Engine. This ensures the separation of responsibilities between design-time and runtime systems. For example, the nodes can be located within Zone 1 as the service provider internal network, along with other non-network IT systems.

For information about user authentication, see the discussion about configuring and customizing My MATRIXX authentication. For information about enabling OAuth 2.0, see the discussion about OAuth 2.0 identity and access management.