docs/designs/redfish-resource-supplement-for-pfr.md

7 Created: 2019-09-12
13 NIST SP 800-193 provides technical guidelines and recommendations supporting
18 to represent the PFR provisioned and locked states.
21 represent the PFR provisioning status such as platform firmware is provisioned
27 Platform Firmware Resilience technology in NIST SP 800-93 provide common
35 - [NIST.SP.180-193](https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-193.pdf)
36 - [Redfish schema supplement](https://www.dmtf.org/sites/default/files/standards/documents/DSP0268_…
37 - [Redfish Logging in bmcweb](https://github.com/openbmc/docs/blob/master/architecture/redfish-logg…
43 - BMC shall provide the way to represent Platform Firmware Resilience
46 - Event logs should be logged to redfish for Platform Firmware Resilience.
51 Resilience by using guidelines provided by NIST SP 800-193. Some of the
70 - ProvisiongStatus: The value of this property indicates the provisioning status
72   1. NotProvisioned: Indicates platform firmware is not provisioned. This is an
76      provisioned but not locked. So re-provisioning is allowed in this state.
78   3. ProvisionedAndLocked: Indicates that the platform firmware is provisioned
79      and locked. So re-provisioning is not allowed in this state.
81 PFR enabled platforms can provision or re-provision the platform resilience
84 it can not be re-provisioned.
93 [Redfish logging in bmcweb](https://github.com/openbmc/docs/blob/master/redfish-logging-in-bmcweb.m…
103    - BIOSFirmwareResiliencyError
104    - BMCFirmwareResiliencyError
105    - CPLDFirmwareResiliencyError
106    - MEFirmwareResiliencyError
107    - FirmwareResiliencyError Severity: Critical
111    - Boot failure
112    - Update Failure
118    - BIOSFirmwarePanicReason
119    - BMCFirmwarePanicReason
120    - CPLDFirmwarePanicReason
121    - MEFirmwarePanicReason Severity: Warning
124    - Boot time watchdog expired
125    - Firmware authentication failure
131    - BIOSFirmwareRecoveryReason
132    - BMCFirmwareRecoveryReason
133    - CPLDFirmwareRecoveryReason
134    - MEFirmwareRecoveryReason Severity: Warning
137    - Launch failures
138    - Update failures
139    - Authentication failures
191 - User can provision the PFR in OEM specific way and test using below URI and
221 - User can induce security attack and validate the panic event logs as well as