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 review issue 1: denial of service against vendor MASA service #81

Closed
mcr opened this issue Sep 30, 2018 · 4 comments
Closed

security review issue 1: denial of service against vendor MASA service #81

mcr opened this issue Sep 30, 2018 · 4 comments
Assignees

Comments

@mcr
Copy link
Member

mcr commented Sep 30, 2018

  1. Denial of service against the vendor MASA service. Adversaries could mount an
    attack against the service at a critical time, preventing real-time issuance of
    nonced vouchers. This could for example prevent the deployment of autonomic networks
    during emergencies.
@mcr mcr changed the title security review issue 1 security review issue 1: denail of service against vendor MASA service Sep 30, 2018
@mcr mcr changed the title security review issue 1: denail of service against vendor MASA service security review issue 1: denial of service against vendor MASA service Sep 30, 2018
@pritikin
Copy link
Collaborator

pritikin commented Oct 2, 2018

shrug... true. the following attempts have been made to mitigate this:

  • the protocol allows for nonce-less vouchers
  • proximity detection

@mcr
Copy link
Member Author

mcr commented Oct 10, 2018

what mechanism exist to mitigate:

  • nonceless vouchers
  • proximity assertion prevents prevents DoS against the audit log, but not against the TCP port.
  • supply-chain integration (know your customers) prevents at the TLS level.

Structure Security Considerations to deal with this section. (9.0, 9.1, 9.2), move DoS to new section 9.3.

@pritikin
Copy link
Collaborator

pritikin commented Nov 2, 2018

since much of the text already existed in 9.0 and to avoid changing the flow I added the DoS section as 9.1 which changed the existing 9.1 & 9.2 section numbers. I think this is a cleaner fix.

@pritikin
Copy link
Collaborator

pritikin commented Nov 2, 2018

b482a02

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants