• Home
• App Integrations
• MFA Integrations
• Two-Factor Authentication (2FA) for Netskope Admin Console

Two-Factor Authentication (2FA) for Netskope Admin Console

---

Two Factor Authentication (2FA) or Multifactor Authentication is the process of the authentication in which you have to provide two factors to gain the access. First Factor is the one that you know username and password and Second factor is what you might have as unique like a phone (For OTP) or Fingerprint. This additional layer prevents the unauthorized person from accessing the resources even if they know your username and password. miniOrange provides 15+ authentication methods and solutions for various use cases.

Follow the Step-by-Step Guide given below for Netskope Admin Console Single Sign-On (SSO)

1. Configure Netskope Admin Console in miniOrange

• Login into miniOrange Admin Console.
• Go to Apps and click on Add Application button.



• In Choose Application, select SAML/WS-FED from the application type dropdown.



• Search for Netskope Admin Console in the list, if you don't find Netskope Admin Console in the list then, search for custom and you can set up your application in Custom SAML App.

Custom Application Name	Netskope Admin Console
SP Entity ID or Issuer	<identifier-value>
ACS URL	<domain-name>.goskope.com/saml/acs
Audience URI	mo
Single Logout Response URL	<domain-name>.goskope.com/saml/logoutResponse
Single Logout Request URL	<domain-name>.goskope.com/saml/logoutRequest
Sign Response	ON




• Click Next, now in the Attribute Mapping configure the following 3 attributes as shown in the image below



• Click on Save.
• Your application is saved successfully. Now click on the Select button against your newly created application. Go to Metadata.



• On the Metadata page -
  
  1. If you want to use miniOrange as User-Store i.e., your user identities will be stored in miniOrange then download the metadata file under the heading 'INFORMATION REQUIRED TO SET MINIORANGE AS IDP'.
  
  2. If you want to authenticate your users via any external Identity Provider like Active Directory, Okta, OneLogin, Google, Apple ID, etc then download the Metadata file under the heading 'INFORMATION REQUIRED TO AUTHENTICATE VIA EXTERNAL IDPS'.



• Then click on Download Metadata.

2. Configure SSO in Netskope Admin Console

• Login to Netskope Admin Console as an administrator. Click Settings in the bottom left corner.
• Navigate to Administration > SSO.
• Click on the EDIT SETTINGS under the SSO/SLO Settings section.



• On the Network Settings section, copy the ACS URL and SP Entity ID



• On the Settings popup window, Select Enable SSO.
• In the IDP URL text box, paste the Login URL value, which you will get from the miniOrange dashboard.
• In the IDP ENTITY ID text box, paste the miniOrange Identifier value, which you will get from the miniOrange dashboard.
• Open your downloaded Base64 encoded certificate in notepad, copy the content, and then paste it to the IDP CERTIFICATE text box.
• SelectEnable SSO.
• In the IDP SLO URL text box, paste the Logout URL value, which you have copied from the miniOrange dashboard.
• Click SUBMIT.

3. Configure 2FA for Netskope Admin Console

3.1: Configure 2FA for miniOrange Admin Dashboard.

• From your miniOrange Dashboard in the left navigation bar, select 2- Factor Authentication, click on Configure 2FA.




• Choose any 2FA method you want to configure.
• Let's say you want to configure OTP over SMS
• Click on OTP over SMS





• Now add your mobile number on which you want to receive the OTP.
• Then click on Save.





• Now as shown in the above image, OTP over SMS is your Active 2FA method.
• Enable Prompt for second factor during signin to your console.
• Then click on Save.



• To verify the configuration login again.
• You will be asked for Username and password then it is redirected to below page:
• Enter the OTP received on the phone and click on verify.



• If you are redirected to your dashboard, you have successfully configured OTP over SMS as your 2FA method.
• Similarly you can configure rest of the 2FA methods for miniOrange dashboard by following this guide.
• To configure 2FA methods for end-users, You can find the guide here.

3.2: Enable 2FA for Users of Netskope Admin Console application.

• To enable 2FA for Users of Netskope Admin Console application. Go to Policies >> App Authentication Policy
• Click on Edit against the configured application



• Enable the Enable 2-Factor Authentication (MFA) option.



• Click on Save.

4. Login with miniOrange

• Go to your Netskope Admin Console Domain. It will redirect you to miniOrange Single Sign-On Service console.



• Enter your miniOrange login credentials and click on Login.
• Since we have Two-factor authentication(2FA) enabled, you will be prompted to register for it. It's a one time process.
• Configure your basic details.



• Configure any authentication method of your choice.



• After successful registration, you will be logged in to your Netskope Admin Console account.
• Now we have Two-factor authentication enabled.
• To verify your Two-factor authentication(2FA) configuration, go to your Netskope Admin Console Domain. You will be redirected to miniOrange login console.



• Enter your login credentials, and click on login. It will prompt to verify yourself against the configured 2fa method.
  e.g. If you have configured OTP over SMS, after login into Netskope Admin Console it will prompt for OTP.



• Enter the OTP received in your phone, after successful 2fa verification, you will be redirected to the Netskope Admin Console dashboard.

5. Adaptive Authentication with Netskope Admin Console

A. Restricting access to Netskope Admin Console with IP Configuration

You can use adaptive authentication with Netskope Admin Console Single Sign-On (SSO) to improve the security and functionality of Single Sign-On. You can allow a IP Address in certain range for SSO or you can deny it based your requirements and you can also challenge the user to verify his authenticity. Adaptive authentication manages the user authentication bases on different factors such as Device ID, Location, Time of Access, IP Address and many more.

You can configure Adaptive Authentication with IP Blocking in following way :

• Login to Self Service Console >> Adaptive Authentication >> Add Policy.



• Add a Policy Name for your Adative Authentication Policy.
• Select Action for Behavior Change, click the Edit link, and then choose the appropriate Action and Challenge Type for the user from that section.





Action for behavior Change Options :




Attribute	Description
Allow	Allow users to authenticate and use services if Adaptive authentication condition is true.
Deny	Deny user authentications and access to services if Adaptive authentication condition is true.
Challenge	Challenge users with one of the three methods mentioned below for verifying user authenticity.




Challenge Type Options :




Attribute	Description
User second Factor	The User needs to authenticate using the second factor he has opted or assigned for such as OTP over SMS PUSH Notification OTP over Email and, many more.
KBA (Knowledge-based authentication)	The System will ask the user for 2 of 3 questions he has configured in his Self-Service Console. Only after the right answer to both questions is the user allowed to proceed further.
OTP over Alternate Email	User will receive an OTP on the alternate email they have configured through the Self Service Console. Once the user provides the correct OTP, they are allowed to proceed further.



• Now click Edit option from the IP Configuration section to configure custom IP range.
• Select Add IP if the User's IP Address is not in the configured list.
• Specify the IP Address that you want to whitelist. For the IP Range other than the whitelisted one, you can select the above setting to reflect.
• Choose either allow or deny by selecting the corresponding option from the dropdown.
• If a user tries to login with the whitelisted IP address, they will always be allowed access.
• We support IP address range in three formats i.e., IPv4, IPv4 CIDR, and IPv6 CIDR. You can choose whichever is suitable for you from the dropdown menu.
• You can add multiple IPs or IP ranges by clicking the + Add IP button.



• Once the changes are made, scroll down to the end and click on Save.

B. Adaptive Authentication with Limiting number of devices

Using Adaptive Authentication you can also restrict the number of devices the end user can access the Services on. You can allow end users to access services on a fixed no. of devices. The end users will be able to access services provided by us on this fixed no. of devices.

You can configure Adaptive Authentication with Device Restriction in following way


• Login to Self Service Console >> Adaptive Authentication >> Add Policy.
• Add a Policy Name for your Adaptive Authentication Policy.
• Select your Action for behavior Change and Challenge Type for user from the Action for behavior Change Section.



• On the Add Policy tab, go to the Device Configuration section and click the Edit button.
• Enter the Number of Device Registrations Allowed as per your requirement. (2-3 devices are recommended.)
• Choose Action if number of devices exceeded (This will override your setting for Action for behavior Change.)
• Challenge: The user needs to verify himself using any of the three methods mentioned in table in step 5.1
• Deny : Deny users access to the system
• Enable Mobile Device Restriction to block logins from mobile devices. This ensures all login attempts from mobile devices will be declined.
• Enable MAC Address Based Restriction if you want to restrict access based on device MAC address.



• Scroll down to the bottom of the page and click on Save.

C. Add Adaptive Authentication policy to Netskope Admin Console

• Login to Self Service Console >> Policies >> Add Login Policy.
• Click on Edit icon option for predefined app policy.



• Set your policy in the Policy Name and select Password as First Factor.
• Enable Adaptive Authentication on Edit Login Policy page and select the required restriction method as an option.
• From Select Login Policy dropdown select the policy we created in last step and click on Submit.

D. Notification and Alert Message.

This section handles the notifications and alerts related to Adaptive Authentication. It provides the following options :

• Get email alerts if users login from unknown devices or locations: Admins need to enable this option to enable receiving alerts for different alert options.
  
  
  

Option	Description
Users login from unknown IP addresses, devices or locations	Enabling this option allows you to login from unknown IP addresses or devices and even locations.
Number of Device registrations exceeded allowed count	This option will allow you to register more devices than the devices you have numbered.
Challenge Completed and Device Registered	Enabling this option allows you to send an email alert when an end-user completes a challenge and registers a device.
Challenge Completed but Device Not Registered	Enabling this option allows you to send an email alert when an end-user completes a challenge but do not registers the device.
Challenge Failed	Enabling this option allows you to send an email alert when an end-user fails to complete the challenge.




• Next subsection is Send email alerts which allows us to enable or disable alerts for admin and end-users. To enable alerts for admins, you can enable the Administrators checkbox.



• In case you want multiple admin accounts to receive alerts, then you can enable the option for admin and then enter the admin emails separated by a ‘,’ in the input field next to Administrator’s email to receive alerts label. To enable alerts for the end users, you can enable the End User checkbox.
• In case you want to customize the deny message that the end user receives in case his authentication is denied due to adaptive policy, you can do this by entering the message inside Deny Message text box.

How to add a trusted Device

• When End-user log in to the self service console after the policy for device restriction is on, he is provided the option to add the current device as a trusted device.

External References

• Guide For Single Sign-On (SSO)
• Netskope Admin Console SAML Single Sign-On