Predictika · Network security

An AI sales agent's Forescout Platform license order, checked before it goes out

An AI sales agent prepares a Forescout Platform license order for a customer: eyeSight with eyeControl, eyeRecover, eyeExtend, eyeSegment, REM, XDR, Assist or eyeInspect, the endpoint counts, the Forescout version, term-based or perpetual licenses, Flexx or per-appliance licensing, and the appliance or virtual platform. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the licensing rules Forescout publishes and returns a verdict and every reason.

Scope: Forescout Platform licensing (eyeSight, eyeControl, eyeRecover, eyeExtend, eyeSegment, REM, XDR, Assist, eyeInspect): dependencies, endpoint counts, versions, Flexx and per-appliance rules. See everything this validator covers

This validator models the licensing rules of the Forescout Platform as published in the public Forescout Product License Guide and Platform Sizing Guide, for any order that involves the products below, not just the scenarios shown on this page.

  • Dependencies and counts — eyeSight is required for eyeControl, eyeRecover, eyeExtend Connect, eyeExtend Ecosystem, eyeSegment and REM; the endpoint counts of eyeControl, eyeRecover, eyeExtend Connect, eyeExtend Ecosystem and eyeSegment must match eyeSight; an eyeExtend Module count cannot exceed eyeSight; Assist requires an XDR entitlement.
  • License types and versions — term-based licenses need Forescout 8.1 or later; eyeSegment, REM, XDR and Assist are subscriptions that need 8.1 or later; eyeExtend Connect and Ecosystem are term-based only.
  • Flexx, per-appliance and appliances — per-appliance licensing is for CT series appliances and the VCT and VCEM virtual appliances; CT and CEM series do not use Flexx; the 5110 does not support 8.2.0 (a limited appliance option exists from 8.2.1, which goes to a person); the 4100 series uses Flexx from 8.2.2 or eyeInspect; the 2130 is an eyeInspect appliance.
  • Subscoping and eyeInspect — subscoping is not available for eyeSight, eyeControl, eyeRecover, eyeSegment, eyeExtend Connect, eyeExtend Ecosystem, Assist, REM or XDR; eyeInspect needs a base license with the endpoint option, the 2130 appliance needs an eyeInspect license, and eyeInspect virtual appliances run on VMware, AWS and Azure.

Not checked: which physical appliances can run eyeInspect beyond the 2130 and 4130 rules, and subscoping of the eyeExtend Module under per-appliance licensing (the guide names an exception it does not spell out). Not covered: prices (none are modeled), per-appliance endpoint capacity and virtual appliance sizing (not found in the public pages read), the full SKU list, regional variants, and any product or version the guides do not describe.

The AI sales agentBuilds the license order from the conversation and says it is ready.
Predictika validatorChecks every rule at once and returns the verdict, each finding, and the computed figures.

6 scenarios in 3 groups · each group runs from the agent’s first attempt to the outcome · click one to switch

What the agent proposes

The AI sales agent says

Illustrative agent statement. The validator receives the structured request below.

Proposing agent: AI sales agent (scripted)

Before sending, the agent must call Recorded run

Predictika validator


      
Waiting for the call.

Where rules-based CPQ gets it wrong

Click to expand

Our assessment of what a typical rules-based CPQ (product rules, price rules and validation rules, as in Salesforce CPQ) does with the same cases. It is a judgment about effort and reliability, not a claim that nothing can be built.

What the validator caughtTypical rules-based CPQPredictika
Endpoint counts that must match eyeSight, and a Module count that must not exceed itOnly with care
Each product has its own count, and the rule differs by product (equal for some, at most for others). A rules-based CPQ needs a validation rule per product, kept in step with the guide.
Every count is compared with the eyeSight count on every call, whatever order the choices arrive in.
Version-dependent license types (term-based, subscriptions)Only with workarounds
Which product needs which version, and which license types each product allows, are separate tables that all depend on the version chosen earlier.
Version, license type and products are compared together on every call.
Appliance and licensing model combinations (Flexx or per-appliance; 5110, 4130, 2130, CT series)Only with workarounds
Each appliance family has its own licensing model and version conditions, so one rule per family and per version has to be written and maintained.
The appliance, licensing model, version and eyeInspect option are checked together.
Subscoping that is allowed for one product and not for the othersOnly with care
A long list of exclusions has to be repeated in a rule and updated whenever the guide changes.
The excluded products and the one that qualifies are checked on every call, with a person asked to confirm the exception.
Every problem returned in one answerOnly with workarounds
Rules tend to fire as the order is saved or a step is completed, so a person often fixes one error and meets the next.
All findings come back together, whatever order the choices arrived in.

What this validator catches: findings from its test cases

Click to expand

Every rule is checked on every call, in any order the choices arrive; one problem never hides another. Blocking findings stop the quote; approval findings need a person to sign off; everything else is computed.

1EyeSight is required for eyeControl, eyeRecover, eyeExtend Connect, eyeExtend Ecosystem, eyeSegment and REM; the quote has no eyeSight endpoints.
2The eyeControl endpoint count of 9999 must match the eyeSight endpoint count of 10000.
3The eyeRecover endpoint count of 10,001 must match the eyeSight endpoint count of 10000.
4The eyeExtend Connect endpoint count of 5000 must match the eyeSight endpoint count of 10000.
5The eyeExtend Ecosystem endpoint count of 2000 must match the eyeSight endpoint count of 10000.
6The eyeSegment endpoint count of 8000 must match the eyeSight endpoint count of 10000.
7The eyeExtend Module endpoint count of 10,001 cannot exceed the eyeSight endpoint count of 10000.
8EyeExtend Connect and eyeExtend Ecosystem are available only as term-based licenses.
9Term-based licenses need Forescout 8.1 or later; the quote is for version 8.0.
10EyeSegment, REM, XDR and Assist are subscriptions that need Forescout 8.1 or later; the quote is for version 8.0.
11Forescout Assist requires an XDR entitlement; the quote has none.
12Subscoping is not available for eyeSight, eyeControl, eyeRecover, eyeSegment, eyeExtend Connect, eyeExtend Ecosystem, Assist, REM or XDR.
13Subscoping needs Forescout 8.1 or later; the quote is for version 8.0.
14Per-appliance licensing is available only on CT series appliances and the VCT and VCEM virtual appliances; the other hardware uses Flexx.
15The CT and CEM series use per-appliance licensing, not Flexx.
16The 5110 does not support Forescout 8.2.0.
17The 5110 has a limited appliance option from Forescout 8.2.1; a person should confirm the limits.
18The 4100 series uses Flexx from Forescout 8.2.2 or eyeInspect 4.0; the quote is for version 8.2.1 without eyeInspect.
19The 2130 is an eyeInspect appliance; the quote has no eyeInspect license.
20The eyeInspect endpoint option needs a base license alongside the endpoint license.
21EyeInspect virtual appliances run on VMware, AWS and Azure only.
22The eyeControl endpoint count of 8000 must match the eyeSight endpoint count of 10000.

Scenarios and results

Click to expand

The recorded result of the validator for each scenario on this page: the request the AI agent sent, the verdict, and every finding, in the order they appear above.

1. Version and license type: A hospital group orders eyeSight, eyeControl and eyeSegment on Forescout 8.0

The agent's request. Please quote eyeSight for 25,000 endpoints, eyeControl for 25,000 endpoints and eyeSegment for 25,000 endpoints, with term-based licenses on Forescout 8.0, for 5160 appliances under Flexx licensing. It is ready to send.

Verdict: Blocked.

  • Term-based licenses need Forescout 8.1. Term-based licenses need Forescout 8.1 or later; the quote is for version 8.0.
  • Subscription products need Forescout 8.1. EyeSegment, REM, XDR and Assist are subscriptions that need Forescout 8.1 or later; the quote is for version 8.0.

2. Version and license type: The agent resubmits after fixing the errors

The agent's request. Please quote eyeSight for 25,000 endpoints, eyeControl for 25,000 endpoints and eyeSegment for 25,000 endpoints, with term-based licenses on Forescout 8.1, for 5160 appliances under Flexx licensing. It is ready to send.

Verdict: Allowed.

  • Order summary. 3 licensed product lines on 25,000 eyeSight endpoints.

3. Counts and dependencies: A retail chain orders eyeSight, eyeControl and Assist

The agent's request. Please quote eyeSight for 25,000 endpoints, eyeControl for 20,000 endpoints and Forescout Assist, with term-based licenses on Forescout 8.2.2, for 5160 appliances under Flexx licensing. It is ready to send.

Verdict: Blocked.

  • eyeControl count must match eyeSight. The eyeControl endpoint count of 20,000 must match the eyeSight endpoint count of 25000.
  • Assist needs an XDR entitlement. Forescout Assist requires an XDR entitlement; the quote has none.

4. Counts and dependencies: The agent resubmits after fixing the errors

The agent's request. Please quote eyeSight for 25,000 endpoints, eyeControl for 25,000 endpoints, XDR and Forescout Assist, with term-based licenses on Forescout 8.2.2, for 5160 appliances under Flexx licensing. It is ready to send.

Verdict: Allowed.

  • Order summary. 4 licensed product lines on 25,000 eyeSight endpoints.

5. Licensing model and subscoping: A manufacturer orders per-appliance licenses for 5160 appliances with a subscoped eyeExtend Module

The agent's request. Please quote eyeSight for 25,000 endpoints and an eyeExtend Module for 5,000 endpoints, with term-based licenses on Forescout 8.2.2, for 5160 appliances under per-appliance licensing. License the eyeExtend Module for only part of the endpoints (subscoping). It is ready to send.

Verdict: Blocked.

  • Per-appliance licensing is for CT appliances. Per-appliance licensing is available only on CT series appliances and the VCT and VCEM virtual appliances; the other hardware uses Flexx.

6. Licensing model and subscoping: The agent resubmits after fixing the errors

The agent's request. Please quote eyeSight for 25,000 endpoints and an eyeExtend Module for 5,000 endpoints, with term-based licenses on Forescout 8.2.2, for CT series appliances under per-appliance licensing. License the eyeExtend Module for only part of the endpoints (subscoping). It is ready to send.

Verdict: Allowed.

  • Order summary. 2 licensed product lines on 25,000 eyeSight endpoints.

Narration transcript

Click to expand

The text of the narrated walkthrough, step by step.

  1. Welcome to a demo of Predictika's Validator. An AI sales agent prepares a Forescout Platform license order for a customer: eyeSight with eyeControl, eyeRecover, eyeExtend, and more. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the licensing rules Forescout publishes and returns a verdict and every reason.
  2. I will start with the first request by the agent.
  3. The agent says. Please quote eyeSight for 25,000 endpoints, eyeControl for 25,000 endpoints and eyeSegment for 25,000 endpoints, with term-based licenses on Forescout 8.0, for 5160 appliances under Flexx licensing. It is ready to send.
  4. Before it goes out, the agent calls the validator.
  5. Blocked, with two findings, all in one answer. Term-based licenses need Forescout 8.1 or later; the quote is for version 8.0. EyeSegment, REM, XDR and Assist are subscriptions that need Forescout 8.1 or later; the quote is for version 8.0.
  6. The validator returned two blocking findings in one answer. A check that reads one field at a time would pass most of this; it shows only when the choices in the quote are checked against each other.
  7. What this shows: for version-dependent license types (term-based, subscriptions), a rules-based CPQ can do this only with workarounds.
  8. Now the agent resubmits.
  9. The corrected request. It changes the forescout version to 8.1.
  10. It calls the validator again.
  11. This time the validator clears it.
  12. Both earlier findings are cleared.
  13. Two problems caught in one call, fixed in one pass, and a clean quote. That is the value of Predictika's validator: catching mistakes before they reach the customer. Now you can try the other scenarios yourself.