lowRISC / lowRISC/opentitan

[dv/sec_cm] Add assertions to check if local escalation can trigger fatal alerts

Open
#16,269 6 comments 0 reactions 0 assignees View on GitHub
Component:DV Component:RTL Earlgrey-PROD Candidate IP:csrng IP:edn IP:kmac IP:otbn IP:otp_ctrl Priority:P2 Subsystem:Entropy Triaging:MultipleBlocks
Dominant language
SystemVerilog
Stars
3.6k
Forks
1.1k
Avg merge
2d 22h
Merged PRs (30d)
141

Description

In EDN V2S review meeting, we identified a low risk coverage hole in terms of local escalation.

We need some assertion checks to ensure all local escalation will eventually trigger FSM fatal errors or alerts.

And we need to double check if all these assertions are written correctly.

> Estimate: 6

Contributor guide

Open the contributing guide

Research direction

Start with the EDN V2S local-escalation logic and trace its paths into FSM fatal errors or alerts. Review how each assertion should cover that guarantee; done means all local-escalation paths have correctly reviewed checks and the relevant verification suite passes.

Written by the indexing model from the issue text.

Assessment

Domain
security, testing-qa
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.