Difference between revisions of "OWASP Web Application Security Accessibility Project"

From OWASP
Jump to: navigation, search
 
(3 intermediate revisions by one user not shown)
Line 1: Line 1:
==== Main  ====
+
==== News ====
 +
- June 2013: [http://www.bbc.co.uk/news/technology-22754006 Blind Federation criticises Captcha security test] <br>
 +
- February 2013: New subproject [http://www.dobrykod.cz/ Dobry kod (Good Code)]
  
 
= OWASP Project Proposal  =
 
= OWASP Project Proposal  =
Line 36: Line 38:
 
=== SCENARIO 3  ===
 
=== SCENARIO 3  ===
  
José is able to communicate in Spanish only. He tips through an online casino. Someone tried to crack his authentication – the cracker introduced an incorrect pass code three times and the account got blocked. José received instruction via e-mail in English how to proceed for unblocking his account. However, José does not understand the English text and has no clue how to react.  
+
José is able to communicate in Spanish only. He bets through an online casino. Someone tried to crack his authentication – the cracker introduced an incorrect pass code three times and the account got blocked. José received instruction via e-mail in English how to proceed for unblocking his account. However, José does not understand the English text and has no clue how to react.  
  
 
=== SCENARIO 4  ===
 
=== SCENARIO 4  ===
  
Anna is dumb. She has arranged for an electronic health records (online). For security reasons, the access to her electronic health records was blocked. Web-based instructions redirect her to a telephone operator, who is supposed to help her out with unblocking the account. Helen is, though, unable to speak and is dependent on someone else´s help.  
+
Anna is mute. She has arranged for an electronic health records (online). For security reasons, the access to her electronic health records was blocked. Web-based instructions redirect her to a telephone operator, who is supposed to help her out with unblocking the account. Helen is, though, unable to speak and is dependent on someone else´s help.  
  
 
=== SCENARIO ...  ===
 
=== SCENARIO ...  ===

Latest revision as of 09:45, 4 June 2013

News

- June 2013: Blind Federation criticises Captcha security test 
- February 2013: New subproject Dobry kod (Good Code)

OWASP Project Proposal

OWASP project proposal of Web Application Security Accessibility (WASA) focuses on free accessibility to security of web applications.

What does security mean?

The origin of the word "security" refers to the Latin word securitas (sine cura + tutus); the word in English means also freedom from danger, safeguard, protection, certainty, doubtlessness.

  1. Objective security
  2. Subjective security

What does security of a web application mean?

From a web application user´s point of view, the security of web application is a complex of relations constituting the user´s interest protection; i.e. a factual status of how these relations are protected including the admissible amount of threats.

What is meant by accessibility?

Accessibility is a state under which an object of usage does not interpose any barriers to the user. Accessibility means without barriers.

What is the concept of web application security accessibility?

It is a state under which a complex of relations designed to protect user´s interests is maintained regardless of user´s disabilities, capabilities, knowledge, experience, visualisation capacities.

Examples of inaccessible security of web applications

SCENARIO 1

John is a blind user of online banking. He is transferring money to another account. He is about to transfer an amount of EUR 27 and introduces three zeros by mistake. A verification of data is processed before the final dispatch. In fact, EUR 27 000 is displayed (27 000 consists of a gap between 27 and 000). However, John´s screen reader identifies only EUR 27 because zeros are either ignored or read as zero – zero – zero. John is not aware of the fact that he is making a payment of EUR 27000 instead of 27.

SCENARIO 2

Helen is sightless. During the population census Helen is about to complete a web-based form and finds out that a code provided by the postman is required at the beginning. Yet she does not see the code. Therefore, she asks someone else to read it for her. A form is displayed in a format that screen readers are unable to read. Helen is completely dependent on the help of others.

SCENARIO 3

José is able to communicate in Spanish only. He bets through an online casino. Someone tried to crack his authentication – the cracker introduced an incorrect pass code three times and the account got blocked. José received instruction via e-mail in English how to proceed for unblocking his account. However, José does not understand the English text and has no clue how to react.

SCENARIO 4

Anna is mute. She has arranged for an electronic health records (online). For security reasons, the access to her electronic health records was blocked. Web-based instructions redirect her to a telephone operator, who is supposed to help her out with unblocking the account. Helen is, though, unable to speak and is dependent on someone else´s help.

SCENARIO ...

What are the project goals?

The practice points out to the fact that a seemingly secure web application does, in reality, protect interests of only a specific group of users. Interests of a great number of users are protected only partially or by no means. This is why I decided to focus extensively on the issue of web application security accessibility. This topic is conceded as a project within OWASP – a globally renowned organization and community, which I appreciate a lot for its high expertness, positive social respect and for successful free share of voice in the field of concepts regarding security of web applications.

During the project we will focus mainly on the following areas:

  1. Research and study of web application security accessibility (WASA)
  2. WASA situation monitoring
    - WASA user testing
    - WASA legal implementation
    - Discussion with providers of web application security
  3. Recommendations for providing an accessible security of web applications


Project About

PROJECT INFO
What does this OWASP project offer you?
RELEASE(S) INFO
What releases are available for this project?
what is this project?
Name: OWASP Web Application Security Accessibility Project (home page)
Purpose: The practice points out to the fact that a seemingly secure web application does, in reality, protect interests of only a specific group of users. Interests of a great number of users are protected only partially or by no means. This project will focus extensively on the issue of web application security accessibility.
License: Creative Commons Attribution Share Alike 3.0
who is working on this project?
Project Leader(s):
Project Contributor(s):
  • Jan Meszáros
  • Tomáš Bakos
  • Jakub Tomšej
  • TEREZA
how can you learn more?
Project Pamphlet: Not Yet Created
Project Presentation:
Mailing list: Mailing List Archives
Project Roadmap: View
Key Contacts
  • Contact the GPC to report a problem or concern about this project or to update information.
current release
Not Yet Published
last reviewed release
Not Yet Reviewed


other releases