fleet/schema/tables/firmware_eficheck_integrity_check.yml
Lucas Manuel Rodriguez 4784217b57
Add documentation for missing fleetd tables and regenerate JSON (#9960)
Updating documentation of Fleetd tables as part of the oncall duty.

Updating the json used by Fleet using the following command:
```sh
cd website
 ./node_modules/sails/bin/sails.js run generate-merged-schema
```

Samples:
![Screenshot 2023-02-20 at 17 20
55](https://user-images.githubusercontent.com/2073526/220192112-69a116e4-badb-4328-92d3-9a2a6f8657fe.png)
![Screenshot 2023-02-20 at 17 21
09](https://user-images.githubusercontent.com/2073526/220192117-dfa06c69-2166-47d4-99c3-e108911e2084.png)


@mikermcneil @eashaw: `generate-merged-schema` generates a different
output every time it's executed. Guess: It seems it should sort the
output lexicograhically?
2023-02-22 16:05:36 -03:00

20 lines
895 B
YAML

name: firmware_eficheck_integrity_check
platforms:
- darwin
description: Performs eficheck's integrity check on macOS Intel T1 chips (CIS 5.9).
columns:
- name: chip
type: text
required: false
description: |
Contains the chip type, values are "apple", "intel-t1" and "intel-t2".
If chip type is "apple" or "intel-t2" then no eficheck integrity check is executed.
- name: output
type: text
required: false
description: |
Output of the `/usr/libexec/firmwarecheckers/eficheck/eficheck --integrity-check` command.
This value is only valid when chip is "intel-t1".
notes: This table is not a core osquery table. It is included as part of [Fleetd](https://fleetdm.com/docs/using-fleet/orbit), the osquery manager from Fleet. Fleetd can be built with [fleetctl](https://fleetdm.com/docs/using-fleet/adding-hosts#osquery-installer).
evented: false