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

Why Driven Testing Important for every Software Tester

Context driven testing, Tester have to set their own path to complete their testing objectives, Test product, test documentation and test deliverable. The meaning of context-driven testing is project capture application of skill and opinion. Tester start testing with context driven testing it is very easy to understand and test application, therefore testing is a human activity that involves a great deal of skill to do well. The context-driven software testing methodological analysis indicates for continuous and creative valuation of testing opportunities. A tester always wants to do testing with context driven testing. It’s a very good practice to hands of explore and able to be proud of that work.   Why we need context driven testing- Context driven methodology like as agile process. Agile methodology generally depends on all-inclusive of unit tests. But in context driven testing, tester have to knowledge on unit testing as well testers will change, In context driven te...

Want to know about Mobile Application Testing? Came to right place

What is Mobile Application Testing ? Mobile Application Testing is a phenomenon of testing functionality, usability and consistency of application software designed for mobiles. It is done in two ways: Automated and Manually. When you buy a new mobile, various applications came pre-installed and some you install as per your need from mobile software distribution platforms such as Google Play, Nokia Store etc. In the recent years, mobile devices had shown a rapid growth rate .  Factors that give an open challenge to Mobile application Testing : 1. Mobile devices models : Different models have different hardware configurations, input methods (some are QWERTY, some are touch while others are normal). 2. Several different operating systems (OS) : Market  is full of availability of different operating  systems  (   Android , IOS, BREW, BREWMP, Symbian,   Windows Phone , and   BlackBerry   (RIM)).Each operating system is unique in ...

SELENIUM TESTING: SELENIUM IDE (& its installation)

In our previous post of selenium testing, we discussed selenium testing briefly. But it was just an introduction about that. And the selenium is much wider in its own. In today’s article, we are going to discuss the selenium, IDE Tool. What is Selenium IDE?? In selenium testing, selenium IDE (Selenium Integrated Development Environment) is a simple tool present in selenium suite Selenium IDE has an inbuilt record and playback functionality that allow us to create tests very quickly, easily and efficiently. Selenium IDE is very easy to install and use. As selenium IDE is a Firefox plugin, it aims to support Firefox browser only. Therefore, we can execute our created test scripts on Firefox only. Selenium IDE supports auto complete mode which allows the user to: * Enter commands more quickly *Restricts the user to enter invalid commands. The most impressive thing about the Selenium IDE in selenium testing that the user need not to have any prior knowledge of pr...