[otbn] Specify recommended software countermeasures
Open
Component:Doc
Component:Software
Earlgrey-PROD Triaged
IP:otbn
Priority:P3
Type:Enhancement
Type:FutureRelease
- Dominant language
- SystemVerilog
- Stars
- 3.6k
- Forks
- 1.1k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 141
Description
We currently have a list of threats and attacks in our design doc, as well as hardware countermeasures against them. However, this gives an incomplete picture of our countermeasures as long as we don't also list the recommended software countermeasures.
Add such countermeasures to the design doc and map them to attacks.
Related to #3314
Contributor guide
Research direction
Start with the OTBN design document and review its existing threat, attack, and hardware-countermeasure lists. Use related issue #3314 for context on the expected scope. Done means the design document lists the recommended software countermeasures and maps them to the relevant attacks.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100