Jump to content
Updated Privacy Statement

Ricardo José Garrido Reichelt

Internal Members
  • Posts

    2
  • Joined

  • Last visited

About Ricardo José Garrido Reichelt

  • Birthday December 31

Profile Information

  • User name display option
    Full name

Personal Information

  • I'd like to receive Citrix Community emails about upcoming events and webinars.
    No

Ricardo José Garrido Reichelt's Achievements

Newbie

Newbie (1/14)

  • One Year In
  • Conversation Starter Rare
  • Week One Done
  • One Month Later

Recent Badges

0

Reputation

  1. Within this article we want to proceed in showcasing some basic EPA (End Point Analysis) policies that we can implement within our organization to enhance security. Please do note that we will not necessarily get into the details on setting up pre or post authentication EPA policies, but more concentrate on the EPA policies itself. For reference here the short list and their setup that we will be describing in this blog entry: EPA for Operating System Patches (not the patch management)EPA for Operating System versionEPA device certificate verificationEPA Antivirus Check (Windows Defender as sample)EPA Registry check and CWA (Citrix Workspace Agent) verificationEPA Registry check and CWA (Citrix Workspace Agent) verification with the use of NetScaler expressions To be able to use EPA with Advanced Expressions we will look it up in the search box and click the search result (fastest operational approach). EPA for Operating System version With the following policy we do want to verify the Operating System version. For this purpose we either could use the "Windows" element, as it includes one configuration option, or even the "Common" option within the EPA Editor (first option). Note that for the purpose of this blog entry we have chosen the Windows menu as first configuration item. Windows >> Windows OS >> Select Operating System and edit desired minimum version Corresponding string: sys.client_expr("sys_0_WIN-OS_NAME_anyof_WIN-11_BUILD-NUM_==_22621[COMMENT: Windows OS]") Important: Be careful when creating the logic = , || , && , <= , etc. as this is a source of common mistake during policy setup. EPA Antivirus Check (Windows Defender as sample) One commonly demanded check is the verification of a security element as could be an Anti Virus solution. In this case and for this specific example we have chosen Windows Defender, but a variety of other security solutions are supported and available. Note that for the purpose of this example we only have used the main version for detection. sys.client_expr("app_0_ANTIVIR_90_362_VERSION_>=_4.20[COMMENT: Windows Defender]") EPA Registry check and CWA (Citrix Workspace Agent) verification with the use of NetScaler expressions As we have seen in the last example when using Registry Key EPA expressions it can get somehow complex from an expression point of view, especially if we wanted to make a more complex rule like V1 || V2 || V3, meaning the verification of different CWA (Citrix Workspace Application) versions. To make it easier form an operational point of view we can make usage of the "Expressions" functionality within NetScaler. You have to navigate to: App Expert >> Expressions >> Advanced Expressions It is highly recommended to make use of the Advanced and not the Classic expressions as those will be deprecated in upcoming versions. We will proceed in creating our EPA Policy with the corresponding Expressions that we have created.
  2. When publishing internal virtualized resources, it is common to use NetScaler as Load Balancer and security element (EPA , WAF , BOT , IP Reputation ) to protect the access to the virtualized company resources (Apps & Desktops; CVAD ). At some stage the organization might have the additional need to publish internal Web Applications to the business users. To be able to do so via NetScaler it would be required to change certain settings, so that NetScaler does publish the content to the user and not StoreFront. The settings that need to be changed for this purpose are: CVPN turned to ONICA Proxy turned to OffCVPN Setting change Expected Outcome: Virtualized Apps & Desktop and also published bookmarks are being shown. In this example the SharePoint Web is the shared Web resource. The described problem has to do with the Single Sign On policy. The IP for the Load Balancing VIP is being resolved as it is considered a public IP (remember the configuration), consequently the Single Sign On is turned off. It is required that the SSO is pushed by a Traffic Policy. This behavior has been put in place for security reasons in previous NetScaler versions. To fix this situation, it is required to create a traffic policy which is bound to the Gateway VIP as described in the following documentation reference: https://docs.netscaler.com/en-us/citrix-adc/current-release/aaa-tm/single-sign-on-types/enable-sso-for-auth-pol.html The same can be accomplished by making the required changes via the NetScaler User Interface as we can extract from the below image.
×
×
  • Create New...