[vc_row css=”.vc_custom_1598393760680{padding-left: 5% !important;background-image: url(https:\/\/www.proya.com.tr\/wp-content\/uploads\/2020\/08\/limrad-proya-header.jpg?id=15166) !important;}”][vc_column css=”.vc_custom_1474490360423{padding-right: 9% !important;}”][vc_empty_space height=”60px”][vc_column_text]<\/p>\n
[\/vc_column_text][vc_empty_space height=”80px”][\/vc_column][\/vc_row][vc_row][vc_column css=”.vc_custom_1476278814474{padding-right: 10% !important;padding-left: 10% !important;}”][vc_empty_space height=”20px”][vc_single_image image=”12938″ img_size=”full” alignment=”center”][vc_empty_space height=”20px”][vc_column_text]LimRad Auth Platform Policy Manager By re-interpreting Radius server language according to industry standards without using the open source code, wired, wireless, VPN, APN, such as the standard, or icons developed by the hardware manufacturers to achieve high performance with low hardware resources can respond to a new generation Radius Server.<\/p>\n
Radius requests to the server can be interpreted faster by multithreading architecture and speed up validation time by answering low hardware resources.<\/p>\n
LimRAD Auht Platform Policy Manager network can work with CheckPoint, Fortinet, Forcepoint and Sophos with Network SSO support.<\/p>\n
Because it does not serve as a gateway in the system topology, it creates a bottleneck in the network.<\/p>\n
Thanks to the advanced interpreter, requests from the user equipment are transmitted to the LimRAD Auth Platform – Policy Manager module via the Radius language via the access device. \u201cRole\u201c,\u201dDownloadable- ACL\u201d ,\u201dVLAN\u201d and \/ or manufacturer-specific icons, depending on the type, which can be forwarded to the access device by verifying the transmitted packets from the integrated MS AD, LDAP, PostgreSQL, MySQL, MSSQL, Oracle, or internal local user identification databases Network Access Control (NAC) is provided by sending verification and rule packets.<\/p>\n
By disaggregating according to the packet types coming from user devices, corporate devices and users’ own devices (BYOD) can be separate from each other, and access to corporate resources can be made only from enterprise devices.<\/p>\n
In the MS, AD and LDAP structures that can be integrated easily, the Organizational Unit in the organizational data source can be taken the temporary memory on the system and the rules can be written according to this data. Does not require repeat identification.[\/vc_column_text][vc_empty_space height=”20px”][vc_single_image image=”15178″ img_size=”full” alignment=”center”][vc_empty_space height=”20px”][vc_column_text css=”.vc_custom_1598394459853{padding-top: 10px !important;padding-bottom: 10px !important;}”]<\/p>\n
[\/vc_column_text][vc_column_text]<\/p>\n