Home
MATRIXX Security
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.
MATRIXX Gateway Proxy
MATRIXX includes Gateway Proxy that acts as a secure entry point for all network traffic that is not the result of subscriber usage. It sits between external applications and the Traffic Routing Agent (TRA).
Gateway Proxy Authentication
The Gateway Proxy provides the services that enable external applications to send data securely to MATRIXX Engine. It acts as an intermediary for clients making requests to MATRIXX Engine and for responses from MATRIXX Engine to external applications.

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.
  - MATRIXX Gateway Proxy
    MATRIXX includes Gateway Proxy that acts as a secure entry point for all network traffic that is not the result of subscriber usage. It sits between external applications and the Traffic Routing Agent (TRA).
    - Gateway Proxy Authentication
      The Gateway Proxy provides the services that enable external applications to send data securely to MATRIXX Engine. It acts as an intermediary for clients making requests to MATRIXX Engine and for responses from MATRIXX Engine to external applications.
  - RS Gateway Security
    RS Gateway uses Spring Security to authenticate clients using login ID and password credentials.
  - Business API Gateway Security
    The Business API Gateway is a development framework that includes the Business API SDK, Rest Services Gateway (RS Gateway), Gateway Proxy, and application tier. It allows custom mobile applications, Web clients, and other custom implementations to integrate with MATRIXX.
  - SBA Gateway Security
    SBA Gateway supports TLS Mutual Authentication.
  - TMF Gateway Security
    TMF Gateway supports HTTP authentication through a configurable authorization URL.
  - TRA Security
    This section describes the general security configuration requirements for Traffic Routing Agent (TRA). These security requirements apply when virtual servers are defined and specified as secured.
  - Self-Signed Certificate Detection and Handling
    While self-signed certificates can be used in controlled environments such as internal testing, because they are not verified by a trusted certificate authority (CA) they must not be used in production environments. If the use of a self-signed certificate is intentional, such as for testing purposes, the MDC Gateway and Traffic Routing Agent (TRA) components include ways to override default handling.
  - Network Security Checklist
    The following is a list of best practices for network design and configuration.
- Application Security
  Application security includes configuring web applications and gateways.
- 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

Gateway Proxy Authentication

The Gateway Proxy provides the services that enable external applications to send data securely to MATRIXX Engine. It acts as an intermediary for clients making requests to MATRIXX Engine and for responses from MATRIXX Engine to external applications.

The Gateway Proxy passes data to MATRIXX Engine without transforming it. This helps to avoid possible corruptions caused by external influences and security risks. If the connection to the engine is allowed, the MDC Gateway performs the business logic to convert the data to MATRIXX Data Container (MDC) format so it can be processed.

The Gateway Proxy listens on an authentication port and optionally on a non-authentication port.

Authentication Mode

By default, in authentication mode, the Gateway Proxy listens on a specific port that must be configured for the RS Gateway to communicate with the Gateway Proxy. For the specific port to use, see the discussion about MATRIXX Engine port configuration in MATRIXX Configuration.

In authentication mode, the MDC Gateway client must provide a login ID and password. A sample Java program, sample_java_client-5000.jar, demonstrates how to create a Java program that uses authentication mode. For more information about the sample Java programs, see the discussion about creating a Java client application in MATRIXX Subscriber Management API.

Non-Authentication Mode

In the optional non-authentication mode, the Gateway Proxy listens on port 4070. In non-authentication mode, accepts the connection without requiring login credentials. This mode is not recommended in a production environment.

For information about configuring the Gateway Proxy, see the discussion about configuring the Gateway Proxy in MATRIXX Installation and Upgrade.