Configuring Inline Encryption

If you do not intend to perform inline encryption and only encrypt via API calls you can skip this section.

1. You need to learn the fields and map the linked form. Under Linked Forms click green plus icon.
   
   
   
2. Provide a name for this form setup. Again this name is arbitrary but should be something to help you identify what it is for. Leave the Request URI blank for now as you will discover it shortly. Click Edit Sample Request and you now need to find the Request Body in the application to discover the fields that we will be making changes to.
   
   
   
   1. To figure out the Request Body, you will need to do a network capture inside the app itself attempting to upload or post to a field on the page you wish to make changes to.

      For this example, we will be looking at Incidents in Servicenow. While sitting on an Incident page open up the browsers Inspect function. Go to the Network tab at the top and clear out any traffic to start clean. Fill out whichever field you wish to control and click submit.

      
      
      

      
      
      
   2. In the Network tab, search for the post. In this case it is incident.do. This will also be the Request URI, enter that inside of the Forcepoint ONE SSE portal. Select incident.do scroll down to Form Data and select view source.
      
      
      

      Then copy the contents (make sure to scroll to the bottom and show more to get the entire content) and paste it into the Sample Request in Forcepoint ONE SSE.

      

3. Now with the Name and Request URI fields filled out and the sample request uploaded you should now see an additional section at the bottom for field mapping. This will allow you to select the available fields that we saw within that form based on the Sample Request uploaded.
   
   
   
4. Now you can add fields to encrypt. Select the field key that Forcepoint ONE SSE discovered (here we are choosing short description). Select the Object and Field that you had created back in step 2 of this encryption setup. Remember you can have multiple objects/fields that you created each with different levels of encryption/tokenization. Here we only created one.
   
   
   

   Now this means I will have encrypted the Short Description field with a level of 20 based on my configuration above.

5. Once done you can now check to make sure that data that is entered into that field through the proxy is tokenized or encrypted based on your security level. This means users going direct or without the proper security level will not see the data in a decrypted state.
   Note: When configuring contextual policies to decrypt data and using custom locations, if you have the same IP address in multiple custom location objects it is possible that one of those locations is configured for a policy where users are not allowed to view data. In this case the user will not see data in a decrypted state coming from that IP regardless of policy. Forcepoint ONE SSE recommends avoiding duplicate IP addresses or ranges across multiple custom location objects. To learn more about custom location objects, refer to Adding custom locations.