Customer resolving lays the foundation for effective abuse management in Guardian Ops. It helps link abuse reports to the correct customers, contracts, and tenants, ensuring that the right actions can be taken accurately. This also helps identify the responsible parties and manage abuse cases efficiently.
  • Customers are individuals or companies; essentially, it’s an entity with an identifier.
  • Contracts are a customer’s specific resources (e.g., mobile vs. DSL, servers, domains, etc.).
  • Tenants can distinguish between subsidiaries that could have clashing customer identifiers
Each of the above entities can have additional metadata assigned to provide details and metadata that your agents can use to understand the specific nature of a customer or contract (e.g., resellers, external vs. internal, etc.). Guardian Ops offers two resolution methods: the Static and the API-based resolver. While we recommend API-based resolving, static resolving provides an alternative with a range of functionality. This lets you choose the best method for your network and customer management setup.
💡 If you need time to prepare your API for sophisticated API resolving, begin with the Static resolver for IP-based resolution and upgrade to the API resolver when ready.
Guardian Ops must resolve a customer identifier associated with the abuse report to process your data. This can be done in two ways:

​
Resolver Types

  1. IP-Based Resolution:
    Guardian Ops uses the IP address from the abuse report as customer IDs.
  2. Static Resolver:
    Guardian Ops maps values from any event attribute (IP addresses, domains, headers, etc.) to customer_id, tenant_id, and contract_id fields with automatic constraint handling and default value assignment.
  3. API Resolver:
    Guardian Ops can call your API with the IP address and event timestamp to retrieve the correct customer identifier and related information. This is ideal for dynamic IP assignments or when additional metadata is needed.
Please select the method that best fits your network and customer management setup, and follow the instructions below to set it up. Choose the method that best fits your network and customer management setup.
The IP Resolver sets the IP of the event as customer identifier.
💡 If you decide to use IPs as customer identifiers, use the IP Resolver node in your Inbound Processing flow. Step 3 of the getting started guide can help you with the configuration.