-
Notifications
You must be signed in to change notification settings - Fork 8
Reviewed and Updated the Threat Modeling #70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Reviewed and Updated the Threat Modeling #70
Conversation
|
|
…me used in the table
| # Threat Model | ||
|
|
||
| ## Assets | ||
| ## Assets and Desired Security Properties |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought it would be better to organize this as table so that we could have assets listed in the first column.
| - Integrity and authenticity of OpenPRoT policies | ||
| | Asset | Security Property | Description | | ||
| |----------------------------------------|---------------------------|-------------| | ||
| | OpenPRoT Firmware | Integrity, Authenticity, Non-Repudiation | Ensure firmware is unmodified, from a trusted source, and the origin cannot de denied.| |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why non-repudiation?
I think we have to consider the supply chain security where a trusted source on top of signing has to provide a proof that it has done its security due diligence on their side which could be a signed audit trail.
| |----------------------------------------|---------------------------|-------------| | ||
| | OpenPRoT Firmware | Integrity, Authenticity, Non-Repudiation | Ensure firmware is unmodified, from a trusted source, and the origin cannot de denied.| | ||
| | Cryptographic Operations | Integrity, Authorization | Ensure operations are performed as intended, only by authorized entities. | | ||
| | Cryptographic Configuration | Integrity, Authorization, Auditability | Ensure cryptographic configurations (key size, algorithms, key lifetime, POST) are secure, unaltered, auditable, and only modifiable by authorized entities. | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cryptographic Configuration is a critical security parameter as it dictates the key size, algorithm choice, and mode of operation. Plus, it dictates the crypto agility of the firmware and hardware.
| | Anti-Rollback Counters | Integrity | Prevent manipulation of monotonic counter to protect against rollback/replay attacks. | | ||
| | Symmetric Keys managed by OpenPRoT | Integrity, Confidentiality| Protect key material from unauthorized modification or disclosure. | | ||
| | Private Asymmetric Keys | Integrity, Confidentiality| Prevent unauthorized modification or exposure to unauthorized parties. | | ||
| | Keys Lifecycle | Integrity, Availability | Ensure that authorized users and processes can perform generation, storage, distribution/provisioning, rotation, and destruction. | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Another CSP is the key lifecycle management process or service.
| class JTAGP,JTAG,OTP dev; | ||
| ``` | ||
|
|
||
| #### Example Threat Modeling Table as Per this Specification |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not a complete list but an illustration. Which debug port or IO is used for programming depends from vendor to vendor.
|
@cfrantz @moidx @attzonko @timothytrippel I would love to get your thoughts on this proposal. |
Summary of changes