factor_scores

Queries

Factor scores driving the organization's overall risk score for a given date. Accepts Unix epoch milliseconds. The date must be within the last 365 days.

Response

Returns FactorScoresResponse

Arguments

Name	Description
scoring_date - Long!	The evaluation date in Unix epoch milliseconds. The timestamp must correspond to 00:00:00 UTC (the beginning of the day) for the requested date.

QUERY

query RISK_SCORE {
RISK_SCORE {
  factor_scores(scoring_date: "123456789") {
    factor_groups {
      grp_name
      factor_name
      score
      peer_risk_score
      category
      weight
      licensed
      recommended_actions
    }
    scoring_date
  }
}
}

RESPONSE

{
"data": {
  "RISK_SCORE": {
    "factor_scores": {
      "factor_groups": [
        {
          "grp_name": "Device Posture Not Used in Access Policy Rules",
          "factor_name": "Device Posture Not Used in Access Policy Rules",
          "score": 3.759,
          "peer_risk_score": 2.628,
          "category": "Lateral Propagation",
          "weight": 3.759,
          "licensed": false,
          "recommended_actions": "[Implement device posture checks for 5 application segments. ]",
          "include": true,
          "notes": "-",
          "factors": [
            {
              "grp_name": "Device Posture Not Used in Access Policy Rules",
              "factor_name": "Device Posture Not Used in Access Policy Rules",
              "score": 3.759,
              "peer_risk_score": 2.628,
              "category": "Lateral Propagation",
              "weight": 3.759,
              "licensed": false,
              "recommended_actions": "[Implement device posture checks for 5 application segments. ]",
              "include": true,
              "notes": "-"
            }
          ]
        },
        {
          "grp_name": "DNS Security",
          "factor_name": "DNS Security",
          "score": 1.967,
          "peer_risk_score": 2.187,
          "category": "Compromise",
          "weight": 3.799,
          "licensed": true,
          "recommended_actions": "[Investigate risks identified in DNS control policies configured and perform the corresponding remediations.]",
          "include": true,
          "notes": "-",
          "factors": [
            {
              "grp_name": "DNS Security",
              "factor_name": "Blocking Unknown DNS Traffic",
              "score": 0.844,
              "peer_risk_score": 0.611,
              "category": "Compromise",
              "weight": 0.844,
              "licensed": true,
              "recommended_actions": "[Transition to a 'Block' posture for unauthorized or high-risk DNS traffic categories.]",
              "include": true,
              "notes": "-"
            },
            {
              "grp_name": "DNS Security",
              "factor_name": "Blocking High Risk DNS Domain Category",
              "score": 0.422,
              "peer_risk_score": 0.254,
              "category": "Compromise",
              "weight": 0.422,
              "licensed": true,
              "recommended_actions": "[Enable the block rule for high risk DNS domain categories.]",
              "include": true,
              "notes": "-"
            },
            {
              "grp_name": "DNS Security",
              "factor_name": "Blocking Critical DNS Domain Category",
              "score": 0.392,
              "peer_risk_score": 0.456,
              "category": "Compromise",
              "weight": 0.844,
              "licensed": true,
              "recommended_actions": "[Enable the block rule for critical DNS domain categories.]",
              "include": true,
              "notes": "-"
            }
          ]
        },
        {
          "grp_name": "Risky SaaS Application Usage",
          "factor_name": "Risky SaaS Application Usage",
          "score": 2.857,
          "peer_risk_score": 2.971,
          "category": "Data Loss",
          "weight": 2.857,
          "licensed": true,
          "recommended_actions": "[Investigate the business use case for access to risky SaaS applications and add Security Awareness training to the internal process.]",
          "include": true,
          "notes": "-",
          "factors": [
            {
              "grp_name": "Risky SaaS Application Usage",
              "factor_name": "Risky SaaS Application Usage",
              "score": 2.857,
              "peer_risk_score": 2.971,
              "category": "Data Loss",
              "weight": 2.857,
              "licensed": true,
              "recommended_actions": "[Investigate the business use case for access to risky SaaS applications and add Security Awareness training to the internal process.]",
              "include": true,
              "notes": "-"
            }
          ]
        }
      ],
      "scoring_date": 1787898873
    }
  }
}
}