search

lowRISC / opentitan

OpenTitan: Open source silicon root of trust
https://www.opentitan.org
Apache License 2.0
2.54k stars 757 forks source link

[sw] Document software guidance on logging of alerts and events #6547

Open moidx opened 3 years ago

moidx commented 3 years ago

Document guidance on how to remember alerts and its impact on different use cases, including recommendations for non-volatile storage.

msfschaffner commented 2 years ago

What is the status of this issue? Do we need to group it with one of our upcoming milestones / assign a priority?

CC @tjaychen

tjaychen commented 2 years ago

@johannheyszl @jadephilipoom

Johann do you guys want to take a stab at this? I think the basic idea here is that we want to give "memory" to alerts in certain scenarios. Our alert system is effectively non-volatile at the moment, ie once you reset the effect is gone. (the fact that an alert was there is recorded in reset manager however).

One of the labs we talked to proposed that perhaps we should consider making the behavior more sticky in some way.

johannheyszl commented 2 years ago

sure

cindychip commented 1 year ago

@johannheyszl do you have any update on this? From triaging, I think it belongs to M3 category. But just want to check-in with you in case you had already working on it?

moidx commented 1 year ago

Marked as P2 and moved to M2.5 for triaging follow up.

moidx commented 4 months ago

This is related to #7974. Moving to ROM_EXT as we want to avoid performing flash operations in the ROM. ROM_EXT is the first chance we get to make persistent attacks easier to remember.

johannheyszl commented 4 months ago

Additional considerations for this and #7974 can be found here.