KhronosGroup / KhronosGroup/KSCAF_DocGuidelines
Preventing Denial-of-Service (DoS) attacks
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 2
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
For both a safety hazard mitigation and cyber-attack point of view DoS should be identified and the risk reduced. DoS could occur via two attack vectors:
- Data handling overloading
- Calculating for results
The SC API should be accommodate parameters, size or time, or return status results accordingly. A Watchdog system may also be necessary to identify and mitigate DoS attacks.
Related to this issue are the following: #12, #15, #16 and Requirements issue No undefined behavior #7
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with this issue and the related issues #12, #15, #16, and requirements issue #7 to understand the intended SC API scope. Define the requirements for limiting data handling and calculation work, returning status results, and assessing whether a watchdog is needed; the issue is complete when those requirements and mitigations are agreed.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100