Merge with DASVS
Nobody has claimed this yet.
- Dominant language
- TeX
- Stars
- 30
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
The DASVS project has independently identified the same ASVS gap we did. They also took a practical approach by creating controls that are testable in real world scenarios.
Assuming their license is compatible, I propose we consider incorporating any missing items from their work into our project. We should ensure full attribution to their team and, ideally, collaborate with them by inviting a PR from their side into our repository.
This approach would allow us to integrate their contributions alongside our planned updates. We can then use this as a foundation for a broader overhaul next year to align with ASVS v5: https://github.com/OWASP/www-project-thick-client-application-security-verification-standard/issues/17
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
Review the linked DASVS v1.0.0 PDF and compare it with the current TCASVS content to identify missing, testable controls. Check the licensing and the discussion in issue 17 before proposing collaboration or integration. Done means an agreed, attributed scope for incorporation or a concrete PR from the DASVS team.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- tex
- Domain
- documentation, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100