ChipSec

Run ChipSec on the DUT. The DUT needs chipsec_main with the chipsec kernel driver, and sudo. See Test Images for the supported kernel versions.

Attribute	Type	Required	Default	Description
`cmd`	`const`	Yes	`chipsec`	Command Name
`name`	`string`	Yes		Name to uniquely identify the teststep. This name will show up in reports, logs and the WebUI
`transport`	`TransportObject`	No		Additional transport options
`options`	`OptionsObject`	No		Additional command options
`parameters`	`ChipSecOptions`	Yes		Options passed into ChipSec

ChipSec Options

Attribute	Type	Required	Description
`modules`	`[]string`	Yes	List of modules that get executed from the `ChipSec` test suite
`pch`	`string`	No	PCH parameter that gets passed into `ChipSec` as `--pch` parameter
`platform`	`string`	No	Platform parameter that gets passed into `ChipSec` as `--platform` parameter

ChipSec Example

cmd: chipsec
name: Run chipsec tests
transport:
  proto: ssh
  options:
    host: "[[attributes.Host]]"
    user: root
    password: root
parameters:
  modules:
    [
      common.bios_kbrd_buffer,
      common.bios_smi,
      common.bios_ts,
      common.bios_wp,
      common.ia32cfg,
      common.me_mfg_mode,
      common.memlock,
      common.rtclock,
      common.smm,
      common.smrr,
      common.spi_access,
      common.spi_desc,
      common.spi_fdopss,
      common.spi_lock,
      common.uefi.access_uefispec,
      common.memconfig,
      common.remap,
      common.smm_dma,
    ]