-
Notifications
You must be signed in to change notification settings - Fork 1
3.3 Abuser Stories
Amos Wong edited this page Apr 17, 2017
·
8 revisions
Issues | Resolutions |
---|---|
As an abuser, I can inject malicious script into a markdown document | Input sanitization should be done on the markdown document before it get passed to the browser's markup processor (which also render the document). |
As an abuser, I can inject malicious SQL query to retrieve confidential information from the database | Input sanitization should be done on the user's input before any SQL command get executed. |
As an abuser, I can create a plugin to retrieve private information by accessing DOM element outside of my plugin. | Plugins code should be sand-boxed and encapsulated an iframe. |
Issues | Resolutions |
---|---|
As an abuser, I can view documents that are not meant for me by accessing a private URL. | The request for viewing a document should be authenticated before returning the document back to the user. |
As an abuser, I can run a brute-force attack on the login page to gain unauthorized access. | The login mechanism should impose a artificial delay before the user can re-enter the login detail again. CAPTCHA should used used after multiple invalid login attempts. |
by Sashimi 🐟
- Introduction
- Project Work Log
- Software Requirements 3.1 Functional Requirements
- Design 4.1 Architecture Diagram
- Developer Guide 5.1 Getting started
- Evaluation Report 6.1 Usability Evaluation
- Misc 7.1 Dog Fooding Process
3.2 Non functional Requirements
3.3 Abuser Stories
3.4 Glossary
4.2 Entity Relationship Diagram
4.3 UI Design
5.2 Resources
5.3 Testing tools
5.4 API Documents
6.2 Performance Evaluation
6.3 Security Evaluation