Testing Points for WEB Security Testing

Testing Points for WEB Security Testing
Test points to be considered for Security Testing

1,
Problem: no input verified
Test method:

Data Type (string, integer, real number, etc)
Supported character sets

Minimum and maximum length
Whether empty input is allowed
Whether the parameter is required
Repeat allowed?
Value Range
Specific value (Enumeration type)
Specific mode (regular expression)

2,
Problem: Problematic access control

Test method:

It is mainly used for pages that require user identity verification and permission verification. Copy the url address of the page, close the page, and check whether the copied address can be directly accessed.
For example, you can see the URL address in the gap from one page chain to another.
Enter this address directly to view the page information that you do not have permission,

3. Incorrect authentication and session management

For example, the input boxes of the Grid, Label, and Tree view classes are not verified. The input content is parsed according to the html syntax.

4. Buffer Overflow

No key data encryption

For example, view-source: http address. You can view the source code.

Enter the password on the page. The page displays *****. Right-click the source file to view the password you just entered,

5. Dos

Analysis: attackers can generate enough traffic from a host to exhaust many applications, and ultimately paralyze the program. Server Load balancer is required.

6. Insecure Configuration Management

Analysis: the link strings, user information, emails, and data storage Information in Config must be protected.

What programmers should do: configure all security mechanisms, disable all unused services, set role permission accounts, and use logs and alarms.

Analysis: the user uses buffer overflow to destroy the web Application Stack. By sending specially written code to the web program, attackers can allow the web application to execute arbitrary code.

7. Injection Vulnerability.
For example, a user login verification page,

If the SQL statement used is:

Select * from table A where username = ''+ username +'' and pass word .....

Enter 'or 1 = 1' in the SQL statement to launch attacks without entering any password.

8. Improper Exception Handling

Analysis: When an exception is thrown, the program provides detailed internal error information, exposing execution details that should not be displayed, and the website has potential vulnerabilities,

 

9. insecure storage

Analysis: account list: the system should not allow users to browse all the accounts on the website. If a user list is required, it is recommended to use some form of Kana (screen name) to point to the actual account.

Browser cache: authentication and session data should not be sent as part of GET. POST should be used,

10 problem: XSS)

Analysis: attackers use cross-site scripting to send malicious code to undiscovered users and steal arbitrary information on their machines.

Test method:

• HTML Tag: <... </…>

• Escape characters: & (&); <(<);> (>); (Space );

• Scripting language:

<Script language = 'javascript '>

... Alert ('')

</Script>

• Special characters: ''<>/

• Minimum and Maximum length

• Whether empty input is allowed