Customer Managed Devices (On-Premises) Deployment
“Configuration of Juniper Secure Edge Deployments” and “Add Directory Services” are mandatory for customers using both On-Premises and Secure Edge deployments.
JIMS Server
The JIMS Server is configured by default for localhost connection. Once it is configured, you can only edit the JIMS Server port and Max Data Rate for the server.
A new JIMS server can also be configured. To add a new JIMS Server, follow the below steps:
- Click Add to add a new JIMS Server.
- Enter the IP address or the fully qualified domain name (FQDN) of the server.
- Give a description.
- Enter the Username and Password for authentication purposes.
- Select the JIMS Server Type from the drop-down menu.
- Deselect TLS only if you perform troubleshooting.
- The identity JIMS Server Port and Max Data Rate are automatically configured by JIMS. You can either change to a certificate signed by your organization or use the default certificate provided by JIMS.
Directory Services
You must configure at least one directory server for JIMS Collector to collect users, devices, and group memberships. Currently, only Active Directory is supported.
If you plan to use multiple Directory Server with the same credentials, you could create a template to reduce the input for each directory server.
To add a new Directory Server:
- Click Add to add a new Directory Server.
- Optionally use an already created template to pre-configure the credentials.
- The source is selected by default.
- Provide a Description.
- Enter the Server Hostname or IP Address of the server.
- Enter the Login ID) and Password for authentication purposes.
- Select TLS Connection if you like to encrypt communication between JIMS and the Directory Server.
Identity Producers
You can configure Identity Producers to gather user and device status events. JIMS uses this information to provide IP address-to-username mappings. JIMS also provides device names with domain names to the enforcement points (SRX Series Firewalls).
The identity producers have 3 tabs/options. Select the appropriate option for your deployment based on the information provided in this section.
Add Event Source
To add a new event source:
Add PC Probe
To add a new PC probe:
- Click Add to add a new PC Probes.
- Enter the Login ID and Password. This is the newly created service account with limited privileges.
- Provide an optional description.
- After you provide the details, you can move the order of usernames in the sequence you want them executed.
Add Syslog Source
To add a new syslog source:
- Click Add to add a new Syslog Source.
- Optionally, select a pre-existing Base Configuration to inherit predefined settings.
- Enter the IP address or Fully Qualified Domain Name (FQDN) of the Syslog client (server sending the logs).
- Provide an optional description.
- Click Add to define your matching regular expressions.
- Navigate to the Regular Expression Sequences section. On the right-hand side, you will see Add, Edit, and Delete buttons.
- Click Add to define a new Regular Expression Sequence. A pop-up window titled Add Regular Expression Builder will appear.
-
In the pop-up window, fill in the following details:
- After completing the fields, click Add to save the sequence.
- Click OK to populate the Regular Expression Sequences table with your newly defined sequence(s). Once configured, the Regular Expression Sequences will be associated with the selected Syslog Source and used for matching incoming log messages accordingly.
Filters
The JIMS server allows you to filter by:
-
IP Filters—Allows you to include or exclude traffic from the specified IP ranges in reports. The Include IP filters will only include those IP ranges while sending updates to SRX, similarly Exclude IP filters will exclude the IP ranges from its update to SRX. Requires input for IP Range Start and IP Range End.
-
User/Device Filters—Designed to exclude specific users or devices from reports. You can specify usernames or device identifiers to filter out unwanted data. Helps in refining the visibility of events by omitting irrelevant or known sources.
-
Group Filters—Acts as Include Filters, applied to all SRX Series Firewalls across your network. For improved matching, a Domain can also be added alongside the group specification.
-
DN Filters—Used to exclude entries based on Distinguished Names (DN). Ideal for filtering out specific organizational units or user paths from directories.
Note: Supports the use of regular expressions for more accurate and flexible matching for User/Device Filters, Group Filters and DN Filters.
Settings
The Settings menu consists of two tabs:
Logging
In the Logging section, enter the following details:
General
In the General section, enter the following details:
Enforcement Points
Add Enforcement Points in JIMS UI
You must configure the Enforcement Points (SRX/NFX devices), otherwise, it cannot pull user, device, and group information to enforce identity-aware policies (user Firewall).
If you have many Enforcement Points with the same client id and client secret, you can create a template to reduce the input for each of them.
To add a new Enforcement Point:
- Click Add.
- Optionally use an already created template to pre-configure the credentials.
- Enter the SRX IP Address.
- If you have several Enforcement Points within a subnet, you can enter a matching Subnet that covers all of them.
- Provide an optional description.
- Enable the IPv6 reporting as IPv6 as it is used in your organization. This adds duplicated records in the auth table on the Enforcement Point.
- Enter the Client ID and Client Secret used for this device.
- The Token Lifetime is enforced. This lifetime can be changed/adjusted.
Configure JIMS in Junos
- Configuration of JIMS with SRX Series Firewall
- Configuration of the Device Identity Authentication Source (End-User-Profile)
- Configuration of the Firewall Policy to Match the Source Identity.
Configuration of JIMS with SRX Series Firewall
Use the following steps to configure JIMS with SRX Series Firewall:
-
Configure the FQDN/IP address of the primary/secondary JIMS server.
[edit services user-identification] user@host# set identity-management connection primary address [fqdn/ip-address] user@host# set identity-management connection secondary address [fqdn/ip-address]
-
Configure the client ID and client secret that the SRX Series device provides to the JIMS primary/secondary server as part of its authentication.
[edit services user-identification] user@host# set identity-management connection primary client-id [client-id] user@host# set identity-management connection primary client-secret [client-secret] user@host# set identity-management connection secondary client-id [client-id] user@host# set identity-management connection secondary client-secret [client-secret]
-
Optionally, configure the source-ip or routing instance that should be used to reach JIMS servers.
[edit services user-identification] user@host# set identity-management connection primary source [ip-address] user@host# set identity-management connection primary routing-instance [routing-instance-name]
Note:You can also configure the enforcement point to validate the certificate of the JIMS server, to do so, see advanced section.
-
Configure the maximum number of user identity items that the device accepts in one batch in response to the query.
[edit services user-identification] user@host# set identity-management batch-query items-per-batch [number-of-items-per-batch]
-
Configure the interval in seconds after which the device issues a query request for newly generated user identities.
[edit services user-identification] user@host# set identity-management batch-query query-interval [query-interval]
-
Configure active directory domains of interest to the SRX Series Firewall. You can specify up to twenty domain names for the filter.
[edit services user-identification] user@host# set identity-management filter domain [domain-name]
-
Configure the address book name to include the IP filter.
[edit services user-identification] user@host# set identity-management filter include-ip address-book [address-book-name]
-
To configure the referenced address set, trace option file name, trace file size, level of debugging output, and the trace identity management for all modules, use the below commands appropriately:
[edit services user-identification] user@host# set identity-management filter include-ip address-set [address-set] user@host# set identity-management traceoptions file [file-name] user@host# set identity-management traceoptions file [file-size] user@host# set identity-management traceoptions level all user@host# set identity-management traceoptions flag all
Configuration of the Device Identity Authentication Source (End-User-Profile)
Specify the device identity authentication source and the security policy. The device obtains the device identity information for authenticated devices from the authentication source. The device searches the device identity authentication table for a device match when traffic issuing from a user’s device arrives at the device. If it finds a match, the device searches for a matching security policy. If it finds a matching security policy, the security policy’s action is applied to the traffic.
Use the following steps to configure device identity authentication source:
-
Specify the device identity authentication source.
[edit services user-identification] user@host# set device-information authentication-source network-access-controller
-
Configure the device identity profile and domain name to which the device belongs.
[edit services user-identification] user@host# set device-information end-user-profile profile-name [profile-name] domain-name [domain-name]
-
Configure the profile name attribute device identity string.
[edit services user-identification] user@host# set device-information end-user-profile profile-name [profile-name] attribute device-identity string [string-value]
Configuration of the Firewall Policy to Match the Source Identity.
Use the following steps to configure one or more firewall policies that control access based on identity.
-
Create a source or destination address for a security policy and configure the application/service to match the policy.
[edit security] user@host# set policies from-zone untrust to-zone trust policy name match source-address any user@host# set policies from-zone untrust to-zone trust policy name match destination-address any user@host# set policies from-zone untrust to-zone trust policy name match application any
-
Define a username or a role (group) name that the JIMS sends to the device. For Example: "jims-dom1.local\user1".
[edit security] user@host# set policies from-zone untrust to-zone trust policy name match source-identity username or group
-
Permit the packet if the policy matches.
[edit security] user@host# set policies from-zone untrust to-zone trust policy name then permit
-
To configure the session initiation time and session close time use the below commands:
[edit security] user@host# set policies from-zone untrust to-zone trust policy name then log session-init user@host# set policies from-zone untrust to-zone trust policy name then log session-close
[edit security policies from-zone LAN to-zone FINANCE policy FinanceAUTH] user@host# set match source-address any user@host# set match destination-address Payroll user@host# set match application any user@host# set match source-identity unauthenticated-user user@host# set match source-identity unknown-user user@host# set then permit firewall-authentication user-firewall web-redirect user@host# set then permit firewall-authentication user-firewall web-redirect-to-https user@host# set then log session-init user@host# set then log session-close