Clarification: 2.4.2 "realistic human timing"
Open
Nobody has claimed this yet.
V2 (prev V11)
- Dominant language
- HTML
- Stars
- 3.6k
- Forks
- 831
- Avg merge
- 7h 55m
- Merged PRs (30d)
- 4
Description
Verify that business logic flows require realistic human timing, preventing
excessively rapid transaction submissions.
I have few questions:
- Is realistic human timing is defined anywhere?
- How this is testable?
- How application react when the tests(E2E, etc) are runs through CI/CD automation?
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
Read the quoted 2.4.2 requirement and the raw Markdown files in the ASVS 5.0 tree, using the referenced requirement links as the documentation entry point. Clarify what “realistic human timing” means, how it can be tested, and how CI/CD automation should be handled; done means the requirement and testing guidance are unambiguous.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- markdown
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100