search

dimmyvi / tigress-requirements

Other
0 stars 3 forks source link

Req-security is unclear #9

Closed bslassey closed 1 year ago

bslassey commented 1 year ago

(Req-Security) Solution SHOULD provide security of the provisioning data transferred (MITM, brute-force attacks on the content, DDOS attacks etc).

It is unclear to me what this requirement is trying to say. What are the threats we're trying to protect against?

dimmyvi commented 1 year ago

Protect content in transit on relay server - confidentiality (encrypt content stored on relay), integrity (impersonation attacks by storing malicious content - protect by device attestation at the time of creation) and availability - introduce measures against denial of service - protect the webapp on the network level.

dimmyvi commented 1 year ago

This may came a bit vague, if you could suggest a better wording, it would be very much appreciated!

bslassey commented 1 year ago

@dimmyvi do you have a threat model document that we can work off of here?

dimmyvi commented 1 year ago

Yes, we have a review tomorrow with security team and will publish it - probably in a day. Will add a link to it here. Do you feel it needs to be a separate document or shall it be appended to the requirement draft?

bslassey commented 1 year ago

Thanks, I look forward to reading it.

dimmyvi commented 1 year ago

We added a threat model draft, still adding content to it: https://github.com/dimmyvi/tigress-sample-implementation/blob/main/draft-tigress-sample-implementation.md

dimmyvi commented 1 year ago

Hi Brad, I finished updating the threat model document, planning to publish it tomorrow (5 November) on Datatracker. If you could review and provide feedback, I'd very much appreciate it

dimmyvi commented 1 year ago

Sample solution and threat modeling document has been published on Datatracker. link is here: https://datatracker.ietf.org/doc/draft-tigress-sample-implementation/01/ I f noone objects, we can close this issue..

bslassey commented 1 year ago

I don't think publishing the security model resolves this, but it is an important step in getting a shared understanding of the security requirements such that they can be described accurately in this doc.

Apologies for not being able to review the security model yet, it is on my to-do list.

dimmyvi commented 1 year ago

this was addressed in a new requirements document with sample implementations was published on 17 Feb. We can close the issue