Skip to main content

Security Testing Types

Security testing is type of testing, where we test the application and try to find all loop holes and try to prevent form unauthorized access of application.
Now security testing is not only  necessity for website and web application. Now hacker are try to hack you mobile, your online data, your digital locker. Now security is one of manor challenge of all software to prevent unauthorized access.
We know, you cannot trust any application and you do not want to register in any website where security is not good.
These are some security testing type; we can test security of application according to nature of application.

No.
Type of security testing
1.1
Information Gathering
1.2.
Conduct Search Engine Discovery and Reconnaissance for Information Leakage
1.3
Fingerprint Web Server
1.4
Review Webserver Metafiles for Information Leakage
1.5
Enumerate Applications on Webserver
1.6
Review Webpage Comments and Metadata for Information Leakage
1.7
Identify application entry points
1.8
Map execution paths through application
1.9
Fingerprint Web Application Framework
1.10
Fingerprint Web Application
1.11
Map Network and Application Architecture
2.1
Configuration and Deploy Management Testing
2.2
Test Network/Infrastructure Configuration
2.3.
Test Application Platform Configuration
2.4.
Test File Extensions Handling for Sensitive Information
2.5.
Backup and Unreferenced Files for Sensitive Information
2.6.
Enumerate Infrastructure and Application Admin Interfaces
2.7.
Test HTTP Methods
2.8.
Test HTTP Strict Transport Security
2.9
Test RIA cross domain policy
3.
Identity Management Testing
3.1
Test Role Definitions
3.2
Test User Registration Process
3.4
Test Account Provisioning Process
3.5
Testing for Account Enumeration and Guessable User Account
3.6
Testing for Weak or unenforced username policy
3.7
Test Permissions of Guest/Training Accounts
3.8
Test Account Suspension/Resumption Process
4.
Authentication Testing
4.1
Testing for Credentials Transported over an Encrypted Channel
4.2
Testing for default credentials
4.3
Testing for Weak lock out mechanism
4.4
Testing for bypassing authentication schema
4.5
Test remember password functionality
4.6
Testing for Browser cache weakness
4.7
Testing for Weak password policy
4.8
Testing for Weak security question/answer
4.9
Testing for weak password change or reset functionalities
4.10
Testing for Weaker authentication in alternative channel
5
Authorization Testing
5.1
Testing Directory traversal/file include
5.2
Testing for bypassing authorization schema
5.3
Testing for Privilege Escalation
5.4
Testing for Insecure Direct Object References
6
Session Management Testing
6.1
Testing for Bypassing Session Management Schema
6.2
Testing for Cookies attributes
6.3
Testing for Session Fixation
6.4
Testing for Exposed Session Variables
6.5
Testing for Cross Site Request Forgery
6.6
Testing for logout functionality
6.7
Test Session Timeout
6.8
Testing for Session puzzling
7
Data Validation Testing
7.1
Testing for Reflected Cross Site Scripting
7.2
Testing for Stored Cross Site Scripting
7.3
Testing for HTTP Verb Tampering
7.4
Testing for HTTP Parameter pollution
7.5
Testing for SQL Injection
7.6
Oracle Testing
7.8
MySQL Testing
7.9
SQL Server Testing
7.10
Testing PostgreSQL
7.11
MS Access Testing
7.12
Testing for NoSQL injection
7.13
Testing for LDAP Injection
7.14
Testing for ORM Injection
7.15
Testing for XML Injection
7.16
Testing for SSI Injection
7.17
Testing for XPath Injection
7.18
IMAP/SMTP Injection
7.19
Testing for Code Injection
7.20
Testing for Local File Inclusion
7.21
Testing for Remote File Inclusion
7.22
Testing for Command Injection
7.23
Testing for Buffer overflow
7.24
Testing for Heap overflow
7.25
Testing for Stack overflow
7.26
Testing for Format string
7.27
Testing for incubated vulnerabilities
7.28
Testing for HTTP Splitting/Smuggling
8
Error Handling
8.1
Analysis of Error Codes
8.2
Analysis of Stack Traces
9
Cryptography
9.1
Testing for Weak SSL/TSL Ciphers, Insufficient Transport Layer Protection
9.2
Testing for Padding Oracle
9.3
Testing for Sensitive information sent via unencrypted channels
10
Logging
10.1
Test time synchronization
10.2
Test user-viewable log of authentication events
11
Business Logic Testing
11.1
Test Business Logic Data Validation
11.2
Test Ability to Forge Requests
11.3
Test Integrity Checks
11.4
Test for Process Timing
11.5
Test Number of Times a Function Can be Used Limits
11.6
Testing for the Circumvention of Work Flows
11.7
Test Defenses Against Application Mis-use
11.8
Test Upload of Unexpected File Types
11.9
Test Upload of Malicious Files
12
Client Side Testing
12.1
Testing for DOM based Cross Site Scripting
12.2
Testing for JavaScript Execution
12.3
Testing for HTML Injection
12.4
Testing for Client Side URL Redirect
12.5
Testing for CSS Injection
12.6
Testing for Client Side Resource Manipulation
12.7
Test Cross Origin Resource Sharing
12.8
Testing for Cross Site Flashing
12.9
Testing for Clickjacking
12.10
Testing WebSockets
12.11
Test Web Messaging
12.12
Test Local Storage


Comments

  1. Its like a book
    You covered all the topics of testing
    Thanks for sharing
    Project Management Tool

    ReplyDelete

Post a Comment

Popular posts from this blog

Steps To Hunt the Bugs Successfully

The testers should catch the bugs in software that they’re testing. Testers should try to catch as several vital bugs as soon as possible. Catching the crucial bug earlier on Product-Life-Cycle can save the Projects from financial losses & mitigate the risks as compared for catching the same at a later stage in SDLC. Steps to hunt the bugs: Sometimes it’s useful to break the rules: The following test cases, which were predefined a tester can miss the bugs so it makes it impossible’s to provide the product i.e. 100 percent bug free. If you-follow pre-determined test cases you risks becoming blind to outside the bugs. A first secret is to check the functionality under the test. It’ll be an effective channel to discover the more bugs, because functionality is not generally covered by the test cases. Examine the patterns: You might have noticed that the bugs can be often met in the groups, one can call them-gregarious. The testing a new but the similar functionality...

Cross browser testing Tools

Cross Browser testing It is a process to test the web apps across multiple browsers. It involves the checking compatibility of the app across multiple web browsers & ensures that your web app’s works correctly across different web browsers. Tools for Cross Browser Testing Browser shots: The browser shots might be most exhaustive cross browser-testing tool that exists. Browser Shots includes all of most popular-browsers, like Firefox, Chrome, & Safari, along with the tons of another browser’s that might sound unfamiliar, like Sea Monkey, Flock, & Iceape. You can adjust the resolution, color-settings, & even Flash and JavaScript settings. Cross Browser Testing: It allows users to test their websites with over the hundred resolution or browser and Operating System combinations. This also has support to mobile web-browsers, which is crucial because the web traffic is making shift from the primarily desktop computer users to primarily mobile ...

Mobile Application Testing: Strategy for Development

There are a huge number of demands and lots of competitions in the mobile application industries. In that demands and competitions, the mobile application testing has become more important. The testing phase of the mobile application testing looks like evil between the creative process and excitement of new products in the market. According to the survey, “In US, on an average 2-3 hours per day people spends their time on smartphones and tablets. On that time, they spent 80% on mobile application and remaining 20% on web applications.” Few list of key factors for successful mobile application testing strategies are: Selection of Device for Testing : Before introducing the mobile application test activities, first select the devices for testing the application. Selection decision is very important because only devices can help to targets maximum numbers of the customers for accessing the application. There are two parts for device selection: §   Device Model ...