Clarification 1.1.2: How requirement apply to Single Page Applications (SPA) architectures
Open
Nobody has claimed this yet.
V1 (prev V5)
Will be closed if no response/opposite arguments
- Dominant language
- HTML
- Stars
- 3.6k
- Forks
- 831
- Avg merge
- 7h 55m
- Merged PRs (30d)
- 4
Description
Rule: 1.1.2 - Verify that the application performs output encoding and escaping either as a final step before being used by the interpreter for which it is intended or by the interpreter itself.
SPAs have complex data flows ( from state management to components to APIs), and ensuring that encoding happens as the “final step” can be challenging.
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 Rule 1.1.2 in the ASVS 5.0 master text and examine how its final-step encoding requirement applies to SPA data flows. Done means documenting a clear interpretation of the requirement for SPA architectures.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, security, web-dev
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100