---
sourceDocument: Brazil Platform security
sourceDocumentLink: https://www.servicenow.com/docs/r/platform-security

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# Inspect the client request

# Inspect the client request {#ariaid-title1}

Release version: Brazil  
Updated November 5, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Before creating a custom encryption rule, you must determine the format of the client
request entering the Edge Encryption proxy
server.

## Before you begin

Role required: admin

## About this task

Because encryption rules iterate over client requests and determine what, if anything, needs
to be encrypted, you must understand the type of request you are creating a rule for. The format
of the client request determines the structure of your encryption rule and the APIs available
for use in the rule.

## Procedure

1. Inspect the client request.  
   Depending on the source of the request, the following tools are available to inspect the
   request and determine the format.  
   {#request-type__table_umt_q5y_rz__entry__2}

   | Source of request | Available tools |
   |-|-|
   | Client browser | Use the developer console in your browser to inspect the client request. Useful tools include: * [Firefox Network Monitor](https://developer.mozilla.org/en-US/docs/Tools/Network_Monitor) * [Chrome Network Panel](https://developers.google.com/web/tools/chrome-devtools/network-performance/resource-loading) {#request-type__ul_oh4_y5y_rz} |
   | Third-party/external source | Use an HTTP protocol analyzer to inspect the request. Useful tools include: * [Wireshark](https://www.wireshark.org/) * HTTP Scoop {#request-type__ul_bbw_2vy_rz} Alternatively, you can often use documentation for the external source to determine the format of the request. |
   [ ]

   {#request-type__table_umt_q5y_rz}
2. From the client request, inspect the packet and determine:  
   * The client request method
   * The URL path of the request
   * The URL parameters
   * The POST parameters, if any
   * The format of the request body, if included
   {#request-type__ul_evj_k1z_rz}  
{#request-type__steps_ifj_cxy_rz}

## Result

Inspecting the request provides an understanding of the fields you need to filter for and
iterate over in your encryption rule. To understand the fields in the request
object, see [request](https://www.servicenow.com/docs/rBKFoNW6MnnYKLdBlLA3eg#c_requestAPI "The request object is a global object available in Edge Encryption rule action and condition scripts.").