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

Implementation specific answers to the security attestation (CON-1118) #898

Closed
PhLuReh opened this issue Apr 10, 2024 · 2 comments
Closed

Comments

@PhLuReh
Copy link

PhLuReh commented Apr 10, 2024

For certification approval a manufacturer has to answer security relevant questions in the CSA_Matter_Security_Attestation_Approved.docx document. Some of them are implementation specific and should be pre-answered by espressif.

13.6.1.e Device shall use non-repeating initialization vectors for given session key.

what is the specific implementation? or is it a connectedhomeip specific thing?

13.6.3.a

is there a CVE report for the esp-matter implementation?

@github-actions github-actions bot changed the title Implementation specific answers to the security attestation Implementation specific answers to the security attestation (CON-1118) Apr 10, 2024
@chshu
Copy link
Collaborator

chshu commented May 10, 2024

@PhLuReh Here is a recommended response to 13.6.1e (if you are using esp-matter SDK without any change to the SDK source code):

13.6.1.e: Yes, the hardware RNG module is used for random number generation, which is true random, so it's non-repeating initialization vector.

Regarding 13.6.3.a: Yes, esp-matter SDK is built on top of connectedhomeip, we support the public vulnerability reporting flow.

is there a CVE report for the esp-matter implementation?

We can't provide a public report for esp-matter implementation, since it's a product specific report, but not SDK specific. If you have any particular questions on the report, feel free to contact us via technical-inquiries, we can assist you on it.

@shubhamdp
Copy link
Contributor

@PhLuReh Can you please close the issue if the questions are answered.

@PhLuReh PhLuReh closed this as completed Jun 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants