List of protocols and ports

  1. Built-in protocols — updated along with the SSG software version. Installing a new version requires a DPI reboot, which causes traffic interruption.
    If needed, they can be supplemented with up-to-date attributes from the VAS Cloud. This is only necessary for complex protocols, but the option is available for all.
  2. Cloud protocols created by VAS Experts — are periodically updated from the VAS Cloud. This ensures that popular applications remain up-to-date as their behavior changes.
  3. Custom (user-defined) protocols — protocols created by users via the GUI using VAS Cloud tools. These have higher priority than those loaded from the VAS Cloud, and within them, IP:PORT takes precedence over IP and CIDR. It is possible to add a protocol based on IP, SNI, or AS. Guide.

Поиск:

ProtocolIDDPI versionProtocol groupProtocol typeUpdateDescription
d2dconfig938712.2UnknownBuilt-inAs neededd2dconfig operates on port 9387 and supports D2D Config for device-to-device configuration management.
d2ddatatrans938812.2UnknownBuilt-inAs neededd2ddatatrans operates on port 9388 and is used by D2D Data Transfer for device-to-device data exchange.
adws938912.2UnknownBuilt-inAs neededadws operates on port 9389 and provides Active Directory Web Services for managing directory objects via web protocols.
otp939012.2UnknownBuilt-inAs neededotp operates on port 9390 and supports one-time password authentication in secure login environments.
fjinvmgr939612.2UnknownBuilt-inAs neededfjinvmgr operates on port 9396 and supports inventory tracking or device communication in Fujitsu environments.
mpidcagt939712.2UnknownBuilt-inAs neededmpidcagt operates on port 9397 and enables agent-level communication in MPIDC environments for monitoring and control.
sec-t4net-srv940012.2UnknownBuilt-inAs neededsec-t4net-srv operates on port 9400 and is used by Secure T4 Network Server for secure terminal server operations.
sec-t4net-clt940112.2UnknownBuilt-inAs neededsec-t4net-clt operates on port 9401 and supports Secure T4 Network Client for secure terminal client communication.
sec-pc2fax-srv940212.2UnknownBuilt-inAs neededsec-pc2fax-srv operates on port 9402 and facilitates Secure PC-to-Fax Server for encrypted fax transmission.
git941812.2UnknownBuilt-inAs neededgit operates on port 9418 and enables Git version control operations over TCP, including fetch and clone commands.
tungsten-https944312.2Web browsingBuilt-inAs neededTungsten software performing HTTPS requests
wso2esb-console944412.2UnknownBuilt-inAs neededwso2esb-console operates on port 9444 and provides web access to the WSO2 Enterprise Service Bus management console.
mindarray-ca944512.2UnknownBuilt-inAs neededmindarray-ca operates on port 9445 and supports centralized analytics and control in MindArray monitoring platforms.
sntlkeyssrvr945012.2UnknownBuilt-inAs neededsntlkeyssrvr operates on port 9450 and is used by SafeNet Sentinel for managing software license keys and secure authentication.
ismserver950012.2UnknownBuilt-inAs neededismserver operates on port 9500 and enables communication with ISM (Infrastructure Service Management) servers.
sma-spw952212.2UnknownBuilt-inAs neededsma-spw operates on port 9522 and facilitates SMA SPW for SMA Solar Power Web communication.
mngsuite953512.2UnknownBuilt-inAs neededmngsuite operates on port 9535 and provides communication and control services for MNGSuite network management or monitoring tools.
laes-bf953612.2UnknownBuilt-inAs neededlaes-bf operates on port 9536 and supports lawful interception buffering functionality in compliant telecom systems.
trispen-sra955512.2UnknownBuilt-inAs neededtrispen-sra operates on port 9555 and manages authentication or authorization services in Trispen Secure Remote Access environments.
ldgateway959212.2UnknownBuilt-inAs neededldgateway operates on port 9592 and is used by LD Gateway for linking distributed systems or services.
←1…270271272273274…318→

Описание