Configure Versa Secure Access Objects
For supported software information, click here.
In secure access gateway or portal policy rules, you can use predefined or custom operating system (OS) or endpoint objects to secure end user connections.
Configure OS Objects
You can use predefined operating system (OS) objects or create custom OS objects and associate these objects with secure access gateway or portal policy rules. For more information, see Add a Secure Access Gateway Policy Rule and Add a Secure Access Portal Policy Rule.
View Predefined OS Objects
Versa Director provides predefined OS objects, including multiple versions of Android, MacOS, and Windows, that you can use as matches in secure access policy rules.
To view the predefined OS objects:
- In Director view:
- Select the Administration tab in the top menu bar.
- Select Appliances in the left menu bar.
- Select a device name in the main pane. The view changes to Appliance view.
- Select the Configuration tab in the top menu bar.
- Select Objects & Connectors > Objects > Predefined > Operating System in the left menu bar. The main pane displays the predefined OS objects.

- Click an OS object to view its name and identifier.

Add Custom OS Objects
You can create custom OS objects to use in secure access policy rules. You may want to do this when the OS running on an end-user device is not included in the predefined OS objects.
You can create OS objects as one of the following:
- Predefined OS object and OS version number
- Pattern entered as a regular expression (regex)
To add a custom OS object:
- In Director view:
- Select the Administration tab in the top menu bar.
- Select Appliances in the left menu bar.
- Select a device name in the main pane. The view changes to Appliance view.
- Select the Configuration tab in the top menu bar.
- Select Objects & Connectors > Objects > Custom Objects > Operating System in the left menu bar.

- Click the
Add icon to add a custom OS object. In the Add Operating System popup window, enter information for the following fields.

Field Description Name (Required) Enter a name for the OS object.
Description Enter a text description for the OS object. Pattern Click to enter a pattern to match the OS object, and then click the
Add icon to enter the pattern. Enter the pattern using the syntax /regex/regex-options. In this field, you can use the standard Perl-compatible regular expression (PCRE) pattern i, to indicate a case-insensitive match). You cannot use other PCRE patterns.For example, to match any Windows version, enter the pattern /windows/i, where i ignores the case. This pattern matches a query for Windows regardless of the case, matching, for example, windows, Windows, and WINDOWS.
If you enter a pattern, you cannot also select a value in the Predefined Operating Systems field.
Predefined Operating Systems Select a predefined OS object to match:
- Android
- Fedora
- MacOS
- MacOS X
- MacOS X Server
- RedHat Enterprise Linux
- Ubuntu
- Windows 7
- Windows 8
- Windows 8.1
- Windows 10
- Windows 10 Mobile
- Windows Server 2012
- Windows Server 2012 R2
- Windows Server 2016
- Windows Server 2019
- Windows Vista
- Windows XP
If you select a value in the Predefined Operating Systems field, you cannot also enter a pattern in the Pattern field.
Build Versions Enter a build version for the OS object. The version can be a single version, a range of versions, or a comma-separated list of versions. For syntax examples, see the description of the Versions field, below. Security Package Versions Enter the security package version of the OS object. The version can be a single version, a range of versions, or a comma-separated list of versions. For syntax examples, see the description of the Versions field, below. Versions Enter the version of the OS object that you selected in the Security Package Versions field. The version can be a single version, a range of versions, or a comma-separated list of versions, using the syntax in the following examples: - Example of a single-version
- 10.0
- Examples of ranges
- 10-15 (version 10 through 15)
- 10.2-15 (version 10.2 through 15)
- 10.2.2-15 (version 10.2.2 through 15)
- 10.2-15.2 (version 10.2 through 15.2)
- 10.2.2- (versions 10.2.2 and later)
- 10.2- (versions 10.2 and later)
- -10.2 (versions prior to 10.2)
- -10 (versions prior to 10)
- Examples of comma-separated lists
- 10, 11, 12, 13, 16
- 10.2, 10.3, 10.6
- 10.2, 10.3.5, 12.2-18, 20- (10.2,10.3.5, 12.2 through 18, and 20 and later)
- Click OK.
Configure Endpoint-Protection Objects
Endpoint protection ensures that the connection of endpoint devices such as laptops, tablets, mobile phones, internet-of-things (IoT) devices, and other wireless devices to an enterprise network is secure. In secure access gateway or portal policy rules, you can use predefined endpoint-protection objects or you can create custom endpoint-protection objects. An endpoint-protection object is the name of an endpoint protection provider, such as Avast, Kaspersky, and McAfee. For more information, see Add a Secure Access Gateway Policy Rule and Add a Secure Access Portal Policy Rule in Configure the Versa Secure Access Service.
View Predefined Endpoint-Protection Objects
Versa Director provides predefined endpoint-protection objects, such as Avast, Kaspersky, and McAfee, that you can use to match in secure access policy rules.
To view predefined endpoint-protection objects:
- In Director view:
- Select the Administration tab in the top menu bar.
- Select Appliances in the left menu bar.
- Select a device name in the main panel. The view changes to Appliance view.
- Select the Configuration tab in the top menu bar.
- Select Objects & Connectors > Objects > Predefined > Endpoint Protection in the left menu bar to view the list of predefined endpoint-protection objects.

- Click an endpoint-protection object to view its name and identifier.

Add Custom Endpoint-Protection Objects
You can create custom endpoint-protection objects to use in secure access policy rules. You may want to do this when the endpoints or entry points of end-user devices you are using are not included in the list of predefined endpoint-protection objects.
You can create endpoint-protection objects as one of the following:
- Predefined endpoint-protection object and endpoint object version number
- Pattern entered as regular expression (regex)
- Predefined endpoint protection with software version number and virus definition number; for example, McAfee software version 8.0.0 and virus definition 4558.
To add a custom endpoint-protection object:
- In Director view:
- Select the Administration tab in the top menu bar.
- Select Appliances in the left menu bar.
- Select a device name in the main panel. The view changes to Appliance view.
- Select the Configuration tab in the top menu bar.
- Select Objects & Connectors > Objects > Custom Objects > Endpoint Protection in the left menu bar.

- Click the + Add icon to add a custom endpoint-protection object. In the Add Endpoint Protection window, enter information for the following fields.

Field Description Name (Required) Enter a name for the endpoint-protection object.
Description Enter a text description for the endpoint-protection object. Predefined Endpoint Protection Select a predefined endpoint-protection object:
- Avast
- Bitdefender
- ESET
- F-secure
- Kaspersky
- McAfee
- Panda
- Symantec
- Trend Micro
- Webroot
- Windows Defender
If you select a value in the Predefined Endpoint Protection field, you cannot also enter a pattern in the Pattern field.
Update Versions Enter the virus update version of the endpoint-protection object. For example, if you selected McAfee, the update version can be 4558. The version can be a single version, a range of versions, or a comma-separated list of versions. For syntax examples, see the description of the Versions field, below. Versions Enter the version of the endpoint-protection object that you selected in the Update Versions field. The version can be a single value, a range of values, or a comma-separated list of values, using the syntax in the following examples:
- Example of a single version
- 10.0
- Examples of ranges
- 10-15 (version 10 through 15)
- 10.2-15 (version 10.2 through 15)
- 10.2.2-15 (version 10.2.2 through 15)
- 10.2-15.2 (version 10.2 through 15.2)
- 10.2.2- (versions 10.2.2 and later)
- 10.2- (versions 10.2 and later)
- -10.2 (versions prior to 10.2)
- -10 (versions prior to 10)
- Examples of comma-separated lists
- 0, 11, 12, 13, 16
- 10.2, 10.3, 10.6
- 10.2, 10.3.5, 12.2-18, 20- (10.2,10.3.5, 12.2 through 18, and 20 and later)
Pattern Click to enter a pattern to match the endpoint-protection object, and then click the
Add icon to enter the pattern. Enter the pattern using the syntax /regex/regex-options. In this field, you can use the standard PCRE pattern i, to indicate a case-insensitive match). You cannot use other PCRE patterns.For example, to match any webroot version, enter the pattern /webroot/i, where i ignores the case. This pattern matches a query for webroot regardless of the case, matching, for example, webroot, Webroot, and WEBROOT.
If you enter a pattern, you cannot also select a value in the Predefined Endpoint Protection field.
- Click OK.
Supported Software Information
Releases 21.2.1 and later support all content described in this article.
Additional Information
Configure the Versa Secure Access Service
Configure Versa SASE Clients
