DE01 Data Flow Sniffing vs DE02 Weak Credential Transit
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.2k
- Forks
- 229
- PR merge metrics
- No merged PRs in 30d
Description
DE02 is a more specific variant of DE01. Two questions come to mind:
- Is it necessary?
- Would a threat-relationship descriptor be useful, e.g. threat A follows from threat B (similar to CWE's model of relationships)?
Contributor guide
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 by comparing the existing DE01 Data Flow Sniffing and DE02 Weak Credential Transit threat definitions. Determine whether DE02 should remain separate and whether threat-relationship descriptors are needed; the issue is done only when one of those directions is decided and specified clearly enough to implement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100