Key Clear (Clear sensitive data)

[ParishrutB]

Use Case

As an admin or SSR,  I need to clear the security keys so that:

• any sensitive data is not accessible on the system partitions anymore. 
• to install new keys when the old ones are lost or compromised.

This is useful in following scenarios:

• There are use cases where the customer wants to clear all sensitive data, for example when returning to manufacturer, resale, repair or changes in customer workloads. 
• On the other hand, there are use cases where the customer wants to clear only certain sensitive data, for example when a specific key has been compromised or lost.

This requires physical authentication at the server so that it is not misused.

Design Review Workflow

1. Each design iteration will have a comment section
2. The section will include:
   • A title with the iteration number
   • Any description or specific feedback the designer is requesting
   • Screenshots of the workflow
3. Based on community and user feedback, we create a comment for the new iteration and repeat these steps

[ParishrutB]

Iteration 1

Depending on the use case, the user can select which sensitive data needs to be cleared from the system. If the use case is to repurpose, resell, or return the entire system, then "Clear all" is used. If the use case is to reset specific keys, then other options are used.

[ParishrutB]

Feedback requested

1. Are there any terms here which you think are not generic for the community?
2. Should the title be "Clear sensitive data" or is "Key clear" understandable? (Key clear is the redfish term)

[joseph-reynolds]

For the Warning box shown above, consider using the term "data loss", as in performing this operation will result in data loss. then characterize what data will be lost: for example, will hypervisor partition data be lost? anything else?