## Platform

### New RiskOS™ IP addresses

As part of ongoing infrastructure updates, we are adding new IP addresses to RiskOS™. After **August 31, 2026**, RiskOS™ may begin serving traffic from these addresses.

If your organization restricts traffic by IP, add the six addresses listed here to your allowlists and firewall rules before that date. If you don't allowlist them, requests can be blocked and you may experience service disruption.

These additions are additive. Keep every Socure IP you already allowlist and add the six new ones.

**New production IPs**

- `54.209.34.129`  
- `100.24.247.109`  
- `44.195.229.53`

**New sandbox IPs**

- `3.218.138.162`  
- `13.217.134.98`  
- `54.85.52.249`

#### What you need to do

1. Add these six IP addresses to your allowlists and firewall rules.  
2. Notify [support@socure.com](mailto:support@socure.com) to confirm you have completed the update so we can mark your account as ready.

If you do not restrict traffic by IP, notify [support@socure.com](mailto:support@socure.com) so we can mark your account as ready.

For help during the update, contact [support@socure.com](mailto:support@socure.com) or your account team.

* * *

## Platform

### MCP server authentication updates

Starting July 21, 2026, username and password authentication for the MCP Server will be deprecated and replaced by **MCP Server Keys**.

If you currently connect to the MCP Server using username and password authentication, you must generate an MCP Server Key and update your MCP client configuration to use token-based authentication before the deprecation date.

#### SSO-enabled organizations will be able to use the MCP Server

Previously, organizations using Single Sign-On (SSO) could not access the MCP Server because authentication required local RiskOS™ username and password credentials.

With the introduction of MCP Server Keys, organizations configured for SSO can now authenticate to the MCP Server using token-based authentication. This eliminates the need for local RiskOS™ credentials and enables MCP Server access for SSO-enabled users.

* * *

## Phone Risk

### Carrier line type override

In July 2026, we are introducing an improvement to phone line type classification for certain carrier-routed numbers.

For affected carriers, the line type will be overridden to **Non-fixed VOIP**.

This update improves the accuracy of line type signals. As a result, customers may observe a **0.5%–1.3% increase** in Non-fixed VOIP classification rates.