[9.0] Integers should be type:integer (elastic#233253) (elastic#233596)

# Backport

This will backport the following commits from `main` to `9.0`:
- [Integers should be type:integer
(elastic#233253)](elastic#233253)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Toby
Brain","email":"[email protected]"},"sourceCommit":{"committedDate":"2025-09-01T06:38:16Z","message":"Integers
should be type:integer (elastic#233253)\n\n## Summary\n\nFrom
the\n[spec](https://swagger.io/docs/specification/v3_0/data-models/data-types/#numbers)\n`type:number`
defines floating point numbers optionally with `type:\nfloat32|float64`.
Integer fields should be `type:integer` where `format`\ncan be one of
`int32` or `int64` if required.\n\nRelated to
https://github.com/elastic/kibana/issues/228077\n\n###
Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers
should verify this PR satisfies this list as well.\n\n- [x] Any text
added follows [EUI's
writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\nsentence case text and includes
[i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n-
[x]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas
added for features that require explanation or tutorials\n- [x] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common scenarios\n- [x] If a plugin
configuration key changed, check if it needs to be\nallowlisted in the
cloud and added to the
[docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n-
[x] This was checked for breaking HTTP API changes, and any
breaking\nchanges have been approved by the breaking-change committee.
The\n`release_note:breaking` label should be applied in these
situations.\n- [x] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n- [x] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n-
[x] Review the
[backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand
apply applicable `backport:*` labels.\n\n---------\n\nCo-authored-by:
kibanamachine
<[email protected]>","sha":"c7ef6cfb87d3e591ff1c0c6ebab1af0f96926117","branchLabelMapping":{"^v9.2.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:all-open","v9.2.0"],"title":"Integers
should be
type:integer","number":233253,"url":"https://github.com/elastic/kibana/pull/233253","mergeCommit":{"message":"Integers
should be type:integer (elastic#233253)\n\n## Summary\n\nFrom
the\n[spec](https://swagger.io/docs/specification/v3_0/data-models/data-types/#numbers)\n`type:number`
defines floating point numbers optionally with `type:\nfloat32|float64`.
Integer fields should be `type:integer` where `format`\ncan be one of
`int32` or `int64` if required.\n\nRelated to
https://github.com/elastic/kibana/issues/228077\n\n###
Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers
should verify this PR satisfies this list as well.\n\n- [x] Any text
added follows [EUI's
writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\nsentence case text and includes
[i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n-
[x]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas
added for features that require explanation or tutorials\n- [x] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common scenarios\n- [x] If a plugin
configuration key changed, check if it needs to be\nallowlisted in the
cloud and added to the
[docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n-
[x] This was checked for breaking HTTP API changes, and any
breaking\nchanges have been approved by the breaking-change committee.
The\n`release_note:breaking` label should be applied in these
situations.\n- [x] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n- [x] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n-
[x] Review the
[backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand
apply applicable `backport:*` labels.\n\n---------\n\nCo-authored-by:
kibanamachine
<[email protected]>","sha":"c7ef6cfb87d3e591ff1c0c6ebab1af0f96926117"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.2.0","branchLabelMappingKey":"^v9.2.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/233253","number":233253,"mergeCommit":{"message":"Integers
should be type:integer (elastic#233253)\n\n## Summary\n\nFrom
the\n[spec](https://swagger.io/docs/specification/v3_0/data-models/data-types/#numbers)\n`type:number`
defines floating point numbers optionally with `type:\nfloat32|float64`.
Integer fields should be `type:integer` where `format`\ncan be one of
`int32` or `int64` if required.\n\nRelated to
https://github.com/elastic/kibana/issues/228077\n\n###
Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers
should verify this PR satisfies this list as well.\n\n- [x] Any text
added follows [EUI's
writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\nsentence case text and includes
[i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n-
[x]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas
added for features that require explanation or tutorials\n- [x] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common scenarios\n- [x] If a plugin
configuration key changed, check if it needs to be\nallowlisted in the
cloud and added to the
[docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n-
[x] This was checked for breaking HTTP API changes, and any
breaking\nchanges have been approved by the breaking-change committee.
The\n`release_note:breaking` label should be applied in these
situations.\n- [x] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n- [x] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n-
[x] Review the
[backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand
apply applicable `backport:*` labels.\n\n---------\n\nCo-authored-by:
kibanamachine
<[email protected]>","sha":"c7ef6cfb87d3e591ff1c0c6ebab1af0f96926117"}}]}]
BACKPORT-->

Co-authored-by: Toby Brain <[email protected]>

Author: kibanamachine

oas_docs/output/kibana.serverless.yaml

@@ -59116,15 +59116,13 @@ components:
           type: number
         category_1_count:
           description: The number of risk input documents that contributed to the Category 1 score (`category_1_score`).
-          format: integer
-          type: number
+          type: integer
         category_1_score:
           description: The contribution of Category 1 to the overall risk score (`calculated_score`). Category 1 contains Detection Engine Alerts.
           format: double
           type: number
         category_2_count:
-          format: integer
-          type: number
+          type: integer
         category_2_score:
           format: double
           type: number

oas_docs/output/kibana.yaml

@@ -66162,15 +66162,13 @@ components:
           type: number
         category_1_count:
           description: The number of risk input documents that contributed to the Category 1 score (`category_1_score`).
-          format: integer
-          type: number
+          type: integer
         category_1_score:
           description: The contribution of Category 1 to the overall risk score (`calculated_score`). Category 1 contains Detection Engine Alerts.
           format: double
           type: number
         category_2_count:
-          format: integer
-          type: number
+          type: integer
         category_2_score:
           format: double
           type: number

x-pack/solutions/security/plugins/security_solution/common/api/entity_analytics/common/common.gen.ts

@@ -151,13 +151,13 @@ export const EntityRiskScoreRecord = z.object({
   /**
    * The number of risk input documents that contributed to the Category 1 score (`category_1_score`).
    */
-  category_1_count: z.number(),
+  category_1_count: z.number().int(),
   /**
    * A list of the highest-risk documents contributing to this risk score. Useful for investigative purposes.
    */
   inputs: z.array(RiskScoreInput),
   category_2_score: z.number().optional(),
-  category_2_count: z.number().optional(),
+  category_2_count: z.number().int().optional(),
   notes: z.array(z.string()),
   criticality_modifier: z.number().optional(),
   criticality_level: AssetCriticalityLevel.optional(),

x-pack/solutions/security/plugins/security_solution/common/api/entity_analytics/common/common.schema.yaml

@@ -203,8 +203,7 @@ components:
           format: double
           description: The contribution of Category 1 to the overall risk score (`calculated_score`). Category 1 contains Detection Engine Alerts.
         category_1_count:
-          type: number
-          format: integer
+          type: integer
           description: The number of risk input documents that contributed to the Category 1 score (`category_1_score`).
         inputs:
           type: array
@@ -215,8 +214,7 @@ components:
           type: number
           format: double
         category_2_count:
-          type: number
-          format: integer
+          type: integer
         notes:
           type: array
           items:

x-pack/solutions/security/plugins/security_solution/docs/openapi/ess/security_solution_entity_analytics_api_2023_10_31.bundled.schema.yaml

@@ -1150,17 +1150,15 @@ components:
           description: >-
             The number of risk input documents that contributed to the Category
             1 score (`category_1_score`).
-          format: integer
-          type: number
+          type: integer
         category_1_score:
           description: >-
             The contribution of Category 1 to the overall risk score
             (`calculated_score`). Category 1 contains Detection Engine Alerts.
           format: double
           type: number
         category_2_count:
-          format: integer
-          type: number
+          type: integer
         category_2_score:
           format: double
           type: number

x-pack/solutions/security/plugins/security_solution/docs/openapi/serverless/security_solution_entity_analytics_api_2023_10_31.bundled.schema.yaml

@@ -1150,17 +1150,15 @@ components:
           description: >-
             The number of risk input documents that contributed to the Category
             1 score (`category_1_score`).
-          format: integer
-          type: number
+          type: integer
         category_1_score:
           description: >-
             The contribution of Category 1 to the overall risk score
             (`calculated_score`). Category 1 contains Detection Engine Alerts.
           format: double
           type: number
         category_2_count:
-          format: integer
-          type: number
+          type: integer
         category_2_score:
           format: double
           type: number