Clarification: V2 Text Statement "High‑value"
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 3.6k
- Forks
- 831
- Avg merge
- 7h 55m
- Merged PRs (30d)
- 4
Description
High‑value business logic flows have considered abuse cases and malicious actors, and have
protections against spoofing, tampering, information disclosure, and elevation of privilege at‑
tacks.
"High-value business logic flows"
As far as I know the High-value is not the standard term is used in security, It should be "business-critical" or "critical business functions" or something else which are highly using in security.
"business logic flows have considered abuse cases and malicious actors, and have
protections against spoofing, tampering, information disclosure, and elevation of privilege at‑
tacks."
How business logic includes STRIDE?, I think, STRIDE is not the main purpose of business logic security.
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 with the raw ASVS 5.0 master .md source containing the quoted requirement, not the derived CSV, JSON, XLSX, PDF, or DOCX files. Review the meanings of “high-value business logic flows” and the cited STRIDE protections, then use the issue discussion to establish agreed terminology and wording before updating the source text.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100