Global score
The global score computes an overall score from the partner technologies. You configure the weightings in Risk Management. The API also returns the scores for the individual technology partner.
When the global score from Thales is used to make a decision, the result of its analysis is included in decisionDetails under an element named globalScore.
Important elements
The table below highlights the important elements to understand when using the global score from Thales to analyze risks.
In this table, the JSON path column(#json-relative-paths) represents a relative path inside the Risk Management response. Click here for the full path.
| Direction | Name | JSON path | Type | Description | Mandatory | Example |
|---|---|---|---|---|---|---|
| Output | name | name | String | Score name Compliant with the following RegEx: ^[^"%&'*,/;<>{}]{1,64}$ |
"Score with TMX and IAT" | |
| Output | intervals | intervals | array | Intervals resulting from the score composition calculation. minItems=2, maxItems=2, items=Integer | [5,22] | |
| Output | partner_details | partner_details | JSON | A JSON object gathering the details from the partner called in the global score computation. | {"threametrix": {…}} |
|
| Output | threatmetrix | partner_details.threatmetrix | JSON | A JSON object gathering the Threatmetrix elements | false | "policy": "gto_atpLogin","eventType": "LOGIN","useDefaultScore": true,"score": -50} |
| Output | policy | partner_details.threatmetrix.policy | String | The name of the used policy | false | "gto_atpLogin" |
| Output | eventType | partner_details.threatmetrix.eventType | enum | The type of event | false | "LOGIN" |
| Output | useDefaultScore | partner_details.threatmetrix.useDefaultScore | Boolean | The usage of DefaultScore entity | false | 1 |
| Output | score | partner_details.threatmetrix.score | Integer | The Threatmetrix resulting score | false | -50.0 |
| Output | result | result | Number | Resultant global score that was calculated based on partnerScores and their weight. | "result": 20 | |
| Output | rating | rating | String | The resulting rating taken in {"LOW RISK", "MEDIUM RISK", "HIGH RISK"} |
"HIGH RISK" |
When several scores are used to make the decision, the global score contains the information from each of them between curly brackets and separated by a comma.
Multi-score example
{
"id": "5b54d59f-a747-4913-ae03-c4ba54b79bde",
"name": "Evaluate_Risk",
"status": "Finished",
"state": {
"result": {
"code": "0",
"message": "Risk operation completed",
"type": "Risk_Response",
"object": {
"risk": {
"status": "SUCCESS",
"decision": {
"access": "allowed",
"auth": [
{
"type": "password"
}
]
},
"decisionDetails": {
"threatmetrix": [
{
"policyName": "gto_atpLogin",
"result": {
"TMX details ...."
}
}
],
"globalScore": [
{
"name": "Score with TMX",
"intervals": [
45,
70
],
"partner_details": {
"threatmetrix": {
"eventType": "LOGIN",
"policy": "default",
"score": 90,
"useDefaultScore": false
}
},
"rating": "LOW RISK",
"result": 73
}
],
},
"policy": {
"id": "348d6906-56f4-4a41-efcd-4109aacd2bb1",
"name": "Example Scores",
"scenario": {
"id": "e088d416-5401-3ca8-7faa-30f0c0389118",
"name": "Aggregated_score"
}
}
}
}
}
}
}
Generic example
globalScore: [
{ global score 1 details} ,
{ global score 2 details} ,
{…}
]
JSON relative paths
In the tables on this page, the JSON path column contains relative JSON paths.
For easier readability, we removed the beginning of the JSON path since it is common to all paths. This part is shown below.
You can also check the example section to see a complete response.
{
"state": {
"result": {
"object": {
"risk": {
"decisionDetails": {
"globalScore": "JSON RELATIVE PATH"
}
}
}
}
}
}
Global score computation
The scores from the different partner technologies are not the same, so each one is converted into a score in the 0-100 range, where 100 is the lowest risk. The following table summarizes the score for each partner technology.
| Partner technology score | Original scoring | Transformation |
|---|---|---|
| ThreatMetrix | -100 to 100 (lowest risk) | Scores outside this range are given the values -100 or +100, as appropriate. Then the scores are transformed to the 0-100 range (so -100 becomes 0, 0 becomes +50, and 100 remains as 100). |
When the score from each partner technology is capped, so that it falls within the original score range, it is transformed using the formula below. The priority for each technology that was configured in Risk Management is taken into account by the formula.
Global score formula
In the formula:
- P: Partner
- G: Global
- PR: Priority
P.x is the original partner score before transformation.
P.min is the minimum possible value in the partner score range.
P.max is the maximum possible value in the partner score range.
G.min is the minimum possible value in the global score range (always 0).
G.max is the maximum possible value in the global score range (always 100).
P.PR is the priority given to the partner technology.
F.P is the transformed score for the partner technology, taking into account the priority.
F.P = (P.x - P.min) * ((G.max - G.min) / (P.max - P.min)) * P.PR
Example for a ThreatMetrix score of -50 priority 1
F.P = (-50 - -100) * ((100 - 0)/(100 - -100)) * 1
F.P = +50 * (100/200)
F.P = 25.
For the global score:
F.Px is the transformed score for partner x, taking into account the priority.
Px.PR is the priority used for partner X.
GS = ( F.P1 + F.P2 + FPn + ... ) / ( P1.PR + P2.P + Pn.PR + ... )
