Skip to content
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

Security Risk Assessment (SRA) for Attestation API #132

Open
athoelke opened this issue Dec 14, 2023 · 0 comments
Open

Security Risk Assessment (SRA) for Attestation API #132

athoelke opened this issue Dec 14, 2023 · 0 comments
Labels
Attestation API Issue or PR related to the Attestation API clarification Something is confusing or missing in the documentation

Comments

@athoelke
Copy link
Contributor

Aligning with the other APIs, the Attestation API needs an SRA.

In this case, there is little to be said about the API itself, other than requiring implementations to be isolated, to sanitize input parameters, and consider limiting access to authorized callers.

Most of the threats to the Attestation process are transferred to the implementation (isolation & protection of cryptographic and claim assets), and/or the report format (covered by PSA Attestation Token and its dependencies) - so a detailed analysis of those threats is not required in this SRA.

@athoelke athoelke added clarification Something is confusing or missing in the documentation Attestation API Issue or PR related to the Attestation API labels Dec 14, 2023
@athoelke athoelke added this to the Attestation API 2.0.0 milestone Dec 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Attestation API Issue or PR related to the Attestation API clarification Something is confusing or missing in the documentation
Projects
Development

No branches or pull requests

1 participant